andar wrote:darude wrote:hey guys,
its me again, the guy who is testing every new release and guess who's still in, the thing with the silent daemon interrupt. now it's in the advanced form of silently dying daemon.
it happens mostly when i start the daemon with the webui and resume about 5 torrents at the same time.Code: Select all
[DEBUG ] 22:34:19 torrentmanager:749 on_alert_save_resume_data
[DEBUG ] 22:34:19 torrent:770 Deleting fastresume file: /home/deluge/.config/deluge/state/e5f431ea43448124665de14df6052f24336b935e.fastresume
[DEBUG ] 22:34:19 torrent:756 Saving fastresume file: /home/deluge/.config/deluge/state/e5f431ea43448124665de14df6052f24336b935e.fastresume
[DEBUG ] 22:34:19 torrentmanager:749 on_alert_save_resume_data
[DEBUG ] 22:34:19 torrent:770 Deleting fastresume file: /home/deluge/.config/deluge/state/f809535d9b7367db1d117e0e5d2fb05914c6d967.fastresume
[DEBUG ] 22:34:19 torrent:756 Saving fastresume file: /home/deluge/.config/deluge/state/f809535d9b7367db1d117e0e5d2fb05914c6d967.fastresume
[DEBUG ] 22:34:19 torrentmanager:717 on_alert_tracker_error
[DEBUG ] 22:34:19 torrentmanager:717 on_alert_tracker_error
[DEBUG ] 22:34:19 torrentmanager:717 on_alert_tracker_error
that were the last lines when the daemon stopped or disappeared, nothing special if u ask me...
i'm going crazy with this **** :/
bye, darude-
Run it in gdb and do a backtrace when it dies.
Hi andar,
sorry for my late reply.
In my very low knowledge of gdb is was unable to launch the daemon in this debugger to backtrace when it stucks.
At last, the client daemon completely stucked when started, but removing the state directory solved that problem.
This behaviour just appeared after stopping and starting the daemon, strange... maybe just killing the process via sigterm is not a really good idea, since it makes some state files corrupt?
bye darude