Info:
All are Debian Wheezy packages
python-libtorrent: Version: 0.15.10-1+b1
libtorrent-rasterbar6: Version: 0.15.10-1+b1
deluged Version: Version: 1.3.3-2+nmu1
Steps to reproduce (I guess):
Have those versions of software running on Debian Wheezy. Those versions
are fresh at the time of writing this.
Have 8 torrents finished downloading
Have 1 torrent seeding, upload rate limited
I've installed python2.7-dbg package, and am running dbg python (run
/usr/bin/deluged -d), but it won't crash now >:/
I'll keep you posted when (if) it crashes.
P.S.
The pid file always stays after the crash. It is with this pid file that I
check if the process is running, and if not, start it.
Here is the script that runs every 2 minutes via cron:
#!/bin/bash
# If we want to keep deluged off, set to true
KEEPOFF=false
LOGFILE="/home/username/.config/deluge/deluged.log"
# Check to see if the pid file exists
if [ ! -f /home/username/.config/deluge/deluged.pid ]
then
# If it does not, then deluged is off
DELUGED_ON=false
else
# If it does exist, we check if the process is running
DELUGE_PID=`cat /home/username/.config/deluge/deluged.pid | awk -F ";"
'{print $1}'`
if kill -0 $DELUGE_PID
then
DELUGED_ON=true
else
echo " deluged-cron.sh: Pid file exists, but deluged was not
running." | mail -s "Deluge-Cron at $(hostname)" [email protected]
DELUGED_ON=false
fi
fi
if $KEEPOFF
then
if $DELUGED_ON
then
kill $DELUGE_PID
echo "deluged is now off, because of the control variable"
exit 0
else
exit 0
fi
fi
# If we got here, and our checks for DELUGED_ON are false, we turn it on
# Otherwise, we just exit
if [ $DELUGED_ON = "false" ]
then
if ! deluged -L debug -l $LOGFILE
then
# If we fail to start deluged, we get an email notifying us
echo " deluged-cron.sh: deluged failed to start!" | mail -s
"Deluge-Cron at $(hostname)" [email protected]
fi
fi
On Thu, Sep 26, 2013 at 6:25 PM, Andrew Resch <[email protected]> wrote:
> If you're not getting a python stack trace, then it's likely that
> libtorrent is crashing.. Which version of libtorrent do you have installed?
> Is it easy to re-create? Can you attach a gdb to program and grab the back
> trace?
>
>
> On Thu, Sep 26, 2013 at 6:04 AM, Milos Kaurin <[email protected]>wrote:
>
>> Hello everyone
>>
>> I've noticed this behavior months ago, but clearing out all torrents from
>> the queue seems to have resolved the issue back then.
>>
>> Now, deluged (headless) crashes randomly again.
>>
>> Info:
>> OS: Debian Wheezy x86 (updated daily)
>> Deluged version: 1.3.3-2+nmu1 (from debian repos)
>>
>> Log tail:
>>
>> [DEBUG ] 14:30:04 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 8
>> [DEBUG ] 14:30:04 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 1
>> [DEBUG ] 14:30:04 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 2
>> [DEBUG ] 14:30:04 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 23
>> [DEBUG ] 14:30:04 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 43
>> [DEBUG ] 14:30:05 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 43
>> [DEBUG ] 14:30:08 alertmanager:123 external_ip_alert: external IP
>> received: 109.93.109.90
>> [DEBUG ] 14:30:14 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 50
>> [DEBUG ] 14:30:14 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 31
>> [DEBUG ] 14:30:14 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 50
>> [DEBUG ] 14:30:25 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 160
>> [DEBUG ] 14:30:25 alertmanager:123 peer_blocked_alert: blocked peer:
>> 190.172.71.210
>> [DEBUG ] 14:30:25 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 89
>> [DEBUG ] 14:30:25 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 50
>> [DEBUG ] 14:30:47 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 58
>> [DEBUG ] 14:30:47 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 50
>> [DEBUG ] 14:30:55 alertmanager:123 peer_blocked_alert: blocked peer:
>> 74.130.12.221
>> [DEBUG ] 14:30:58 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 73
>> [DEBUG ] 14:31:07 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 52
>> [DEBUG ] 14:31:28 alertmanager:123 dht_reply_alert: REDACTED-TORRENT1 ()
>> received DHT peers: 100
>> [DEBUG ] 14:31:28 alertmanager:123 peer_blocked_alert: blocked peer:
>> 77.54.115.89
>> [DEBUG ] 14:33:13 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT2 resume data generated
>> [DEBUG ] 14:33:13 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT1 resume data generated
>> [DEBUG ] 14:33:13 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT3 resume data generated
>> [DEBUG ] 14:33:13 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT4 resume data generated
>> [DEBUG ] 14:33:13 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT5 resume data generated
>> [DEBUG ] 14:33:13 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT6 resume data generated
>> [DEBUG ] 14:33:13 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT7 resume data generated
>> [DEBUG ] 14:33:13 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT8 resume data generated
>> [DEBUG ] 14:33:13 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:33:13 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:33:13 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:33:13 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:33:13 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:33:13 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:33:13 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:33:13 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:33:13 torrentmanager:718 Opening torrents fastresume file for
>> load.
>> [DEBUG ] 14:33:13 torrentmanager:758 Saving fastresume file:
>> /home/username/.config/deluge/state/torrents.fastresume
>> [DEBUG ] 14:33:23 torrentmanager:678 Saving torrent state file.
>> [DEBUG ] 14:36:23 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT2 resume data generated
>> [DEBUG ] 14:36:23 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT1 resume data generated
>> [DEBUG ] 14:36:23 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT3 resume data generated
>> [DEBUG ] 14:36:23 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT4 resume data generated
>> [DEBUG ] 14:36:23 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT5 resume data generated
>> [DEBUG ] 14:36:23 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT6 resume data generated
>> [DEBUG ] 14:36:23 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT7 resume data generated
>> [DEBUG ] 14:36:23 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT8 resume data generated
>> [DEBUG ] 14:36:23 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:36:23 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:36:23 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:36:23 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:36:23 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:36:23 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:36:23 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:36:23 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:36:23 torrentmanager:718 Opening torrents fastresume file for
>> load.
>> [DEBUG ] 14:36:23 torrentmanager:758 Saving fastresume file:
>> /home/username/.config/deluge/state/torrents.fastresume
>> [DEBUG ] 14:36:43 torrentmanager:678 Saving torrent state file.
>> [DEBUG ] 14:37:06 alertmanager:123 peer_blocked_alert: blocked peer:
>> 80.174.70.159
>> [DEBUG ] 14:39:33 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT2 resume data generated
>> [DEBUG ] 14:39:33 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT1 resume data generated
>> [DEBUG ] 14:39:33 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT3 resume data generated
>> [DEBUG ] 14:39:33 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT4 resume data generated
>> [DEBUG ] 14:39:33 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT5 resume data generated
>> [DEBUG ] 14:39:33 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT6 resume data generated
>> [DEBUG ] 14:39:33 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT7 resume data generated
>> [DEBUG ] 14:39:33 alertmanager:123 save_resume_data_alert:
>> REDACTED-TORRENT8 resume data generated
>> [DEBUG ] 14:39:33 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:39:33 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:39:33 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:39:33 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:39:33 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:39:33 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:39:33 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:39:33 torrentmanager:1013 on_alert_save_resume_data
>> [DEBUG ] 14:39:33 torrentmanager:718 Opening torrents fastresume file for
>> load.
>> [DEBUG ] 14:39:33 torrentmanager:758 Saving fastresume file:
>> /home/username/.config/deluge/state/torrents.fastresume
>> [DEBUG ] 14:40:03 torrentmanager:678 Saving torrent state file.
>> [DEBUG ] 14:40:07 alertmanager:123 peer_blocked_alert: blocked peer:
>> 190.46.140.47
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Deluge Dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/deluge-dev.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Deluge Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/deluge-dev.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/groups/opt_out.
