Deluged start freeze, NO error on LOG

[olygraph]

Since couple of week, deluged start but looks like it freeze on start.

I can't connect to my daemon until I delete fastresume.
After a couple hours / day, same problem come back.

Deleted all my config (~/.config/deluge), started fresh and still have the problem today.

deluged: 1.3.6
libtorrent: 0.16.13.0

No error in the debug log.
last line of my debug log:

Code: Select all

[DEBUG] 17:21:53 torrent:305 setting 87fbc3c898127658f5c46a9bc09c131287d6d795's file priorities: [1]

Using kodibuntu.
Never had problem before using it.

[olygraph]

Just figured out I was way out of date.

I updated to:
deluged: 1.3.13
libtorrent: 1.0.11.0

Looks like it works now.

[olygraph]

No still crashed with corrupted state config folder.

[shamael]

Only when you restart the daemon/server or randomly? Nothing in system logs?
The storage is clean? how is it mounted?

[olygraph]

yes only daemon.

might just have found why.
If I delete the state folder. start fresh and add a torrent I get this error:

Code: Select all

[ERROR   ] 08:57:48 torrentmanager:734 Unable to backup /home/*user*/.config/deluge/state/torrents.state to /home/olygraph/.config/deluge/state/torrents.state.bak: [Errno 2] No such file or directory
[ERROR   ] 08:57:48 torrentmanager:823 Unable to backup /home/*user*/.config/deluge/state/torrents.fastresume to /home/olygraph/.config/deluge/state/torrents.fastresume.bak: [Errno 2] No such file or directory

I guess it was not backup up and on crash those files were corrupted.

It usually happen after a day of use and when it crash I believe or I kill it. But yeah pretty random

I created the .bak files, and now it doesn't throw the error anymore. Might just be why.

It is mounted on / with ext4 in fstab
I have 90% free space

[olygraph]

Well I just killed it and restart it and freeze again. Bak file is present and loaded
. Tried with and without bak file.
last line of debug:

Code: Select all

[DEBUG   ] 10:04:24 torrentmanager:486 handle id: 2d8c15586b626d932ae4e3757f44c810d2e7cca2
[DEBUG   ] 10:04:24 torrent:113 Creating torrent object 2d8c15586b626d932ae4e3757f44c810d2e7cca2
[DEBUG   ] 10:04:24 configmanager:111 Getting config 'core.conf'
[DEBUG   ] 10:04:24 configmanager:111 Getting config 'core.conf'
[DEBUG   ] 10:04:24 torrent:358 Setting trackers for 2d8c15586b626d932ae4e3757f44c810d2e7cca2: [{'send_stats': True, 'fails': 0, 'verified': False, 'url': 'trackeX"', 'fail_limit': 0, 'complete_sent': False, 'source': 1, 'start_sent': False, 'tier': 0, 'updating': False}]
[DEBUG   ] 10:04:24 torrent:321 setting 2d8c15586b626d932ae4e3757f44c810d2e7cca2's file priorities: [1]

then nothing happen

I cant use it anymore

[olygraph]

ok I restore an old lubuntu back up (january when deluged was not freezing).

1. Re-update / upgrade everything including deluged

Code: Select all

apt-get upgrade, dist-upgrade

2. Restore State Folder backup (I have one I know was stable)

3. It was working until I kill deluged a couple of times.
Deluged freeze on launch(deluged -L debug) just stop randomly without any error and hang there forever without going further.


Then, on a side note, I figured out my network-manager was not starting automatically and I was playing with it.

I discovered by chance if I do these steps:

Code: Select all

sudo stop network-manager
deluged -L debug
sudo start network-manager

Means I start deluged when network manager is closed, it works, then re-start network, and voila deluged just start.

Kill deluged, relaucch deluged -L debug, freezes again. Stop network, launch deluge, works!

Using a static IP with google DNS 8.8.8.8

Internet works fine.

Any ideas?

Kinda of an annoying workaround for now.

[shamael]

I faced issue with fastresume and the previous mount described in the wiki, changed now in the documentation http://forum.deluge-torrent.org/viewtop ... 03#p225403 . Each time my daemon restart I faced an issue with a recheck needed for all the torrents, simply linked by the way the service link the USB disk. But it's different for you it seems....

I'm not using the network-manager package but it seems you can bypass it with a fixed config https://wiki.debian.org/NetworkManager in "Wired Networks are Unmanaged" section. If you're in the case all is managed by the package it worth the test to manually define it /etc/network/interfaces and see the behavior

Ps: I suppose the service account of the daemon has all the accesses needed for the location mentioned in the error