Opened 15 years ago
Closed 15 years ago
#1163 closed bug (Invalid)
config:405 Unable to open config file
Reported by: | simonbcn | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.3 |
Component: | Core | Version: | 1.2.1 |
Keywords: | Cc: |
Description
deluged in server with init script.
When it starts the init script, in log file appears this warning several times:
[WARNING ] config:405 Unable to open config file: /xxx/.config/deluge/label.conf
But that config file exist.
And, sometimes, when I stop the deluged (with init script), it shows, in log file:
[WARNING ] config:405 Unable to open config file: /xxx/.config/deluge/core.conf
But that config file exist too.
All these are only warnings, incorrect, but only warnings. Deluged starts. But the real problem is that today, I rebooted the machine but deluged didn't start, I saw the log file:
[ERROR ] config:405 Unable to open config file: /xxx/.config/deluge/core.conf
I didn't change anything and I executed:
sudo /etc/init.d/deluge-daemon start
And deluged started well this time!
Well, I think it's necessary to review the code, don't you think?
(Sorry for my bad english. I'm spanish)
Change History (3)
comment:1 by , 15 years ago
Status: | new → pending |
---|
comment:2 by , 15 years ago
Status: | pending → new |
---|
No, that is not the problem.
Today I have restarted the daemon and this the output:
[WARNING ] config:405 Unable to open config file: /xxx/.config/deluge/label.conf
The daemon is started with my user and the permissions are 644.
comment:3 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
I don't see how this would prevent your process from starting.. These are simply warnings that shouldn't have any real impact and they can happen when new files need to be created.
It sounds like whatever user you were attempting to run Deluge as did not have read permissions to where the config file is stored. Could you check that?