[[Support] binhex - DelugeVPN]

Yeah, I removed the entire sessions key and its all sub-records. Not sure if the file would be recreated automatically correctly if you deleted it, I'd guess not as it contains the the password hash.

 

And yes the file was something like 1.2 millions lines, all but 23 of which were session records. Which now I think about it is far too many to just be orphaned sessions, even for an image that had been running (with irregular updates) since early 2019.

 

I suspect that any session records could be cleaned up safely on startup, worse case any active sessions would have to re-authenticate? I don't know for sure that there's nothing that depends on them though.

[[Support] binhex - DelugeVPN]

On 5/7/2022 at 7:09 PM, Earendur said:

 

It appears I'm having this exact same issue.  Hangs at the same point and the WebUI doesn't load.

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

Sometimes, after leaving it for a few hours, it seems to move to the next step:

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 14:06:11,257 DEBG 'watchdog-script' stdout output:
[warn] Deluge config file /config/web.conf does not contain valid data, exiting Python script config_deluge.py...

2022-05-07 14:06:11,592 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-05-07 14:06:11,802 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started

However, the WebUI is not responsive and won't load.

I've made no changes to my configuration and it was working for many months before yesterday when this issue popped up.

 

Edit:  I was planning to follow the steps listed here today, but it seems to have started on it's own over night and is running fine now.  I'll update if that changes.

 

 

I've just seen exactly this behaviour (takes many minutes to progess from "[info] Writing changes to Deluge config file '/config/core.conf'...", WebUI nonresponsive, and deluge-web pinning one cpu core at 100%), and have found what was causing it for me.

 

'\appdata\binhex-delugevpn\web.conf' had grown to over 40MB causing both the config-parser script and deluge-web to choke trying to parse it. Looking at the file this was because there were thousands of 'session' entries; I'm guessing that it caches active sessions to the webui in the web.conf, but for some reason never clears them, causing the file to grow out of control.

 

Stopping the image, deleting all of these entries (bringing the file down to a much more reasonable 620bytes), and restarting the image made everything start up quickly with the webui working as normal.

 

Hopefully that's helpful to someone!