Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#3183 closed bug (Fixed)

Closing Daemon causes core.conf to revert to default settings

Reported by: hawkeye Owned by: Cas
Priority: critical Milestone: 2.0.0
Component: Core Version: develop
Keywords: Cc:

Description

Really loving 2.0x but having a pretty significant issue here when using a daemon with thin clients on linux.

Closing out the daemon cleanly via the ui or systemd will cause a few settings in core.conf to revert to null from settings made from any ui or manual text editor.

"listen_interface" set to ip address in ui or text editor on daemon close reverts to null "listen_random_port" set to false in ui or text editor on daemon close reverts to null

Attachments (1)

deluge.PNG (15.3 KB) - added by hawkeye 2 years ago.
core.conf relevant settings

Download all attachments as: .zip

Change History (9)

Changed 2 years ago by hawkeye

core.conf relevant settings

comment:1 Changed 2 years ago by Cas

  • Milestone changed from needs verified to 2.0
  • Owner set to Cas
  • Status changed from new to assigned

comment:2 Changed 2 years ago by Cas

  • Milestone changed from 2.0 to 2.0.0

Milestone renamed

comment:3 Changed 2 years ago by Cas

You cannot manually modify core.conf while deluged is running, it will be overwritten on every new config setting and shutdown.

I can see no issue with setting changes to listen_interface, however, there appears to be a bug in listen_random_port.

Which UI were you using?

Edit: I don't see any issue with listen_random_port is random_port set to True as that would set listen_random_port to None?

Last edited 2 years ago by Cas (previous) (diff)

comment:4 Changed 2 years ago by Cas

  • Milestone changed from 2.0.0 to needs verified

comment:5 Changed 2 years ago by hawkeye

here is how it occurs:

Set listen ip address in thin client connected to daemon to 192.168.2.10 hit apply. listen_interface in core.conf reflects the ip address.

If I shutdown the daemon via systemd OR the thin client that IP address will revert to null. I am not changing it while the daemon is running except via the thin client.

I can go in and set the listen address manually and then start the daemon and now the ip address in the thin client network configuration is what it should be (192.168.2.10). But once I stop the daemon it reverts to null.

i updated to 2.0.0.dev7223 and the problem occurs. This issue does not occur on the current 1.3.15 version. I have not tested it on the windows version.

Last edited 2 years ago by hawkeye (previous) (diff)

comment:6 Changed 2 years ago by Cas

  • Milestone changed from needs verified to 2.0.0

Ok I now see the issue now! This is an odd one but I think it might be a text/bytes issue.

Actually found the issue, a mistake in core shutdown code...

Last edited 2 years ago by Cas (previous) (diff)

comment:7 Changed 2 years ago by Cas

  • Resolution set to Fixed
  • Status changed from assigned to closed

Thanks for feedback, fixed is develop: [67d9c2efb4ba9]

comment:8 Changed 2 years ago by hawkeye

I concur issue is fixed!

Note: See TracTickets for help on using tickets.