strange crash on freenas
Posted: October 19th, 2010, 8:05 pm
version 0.4.12
OS freebsd (freenas)
skin n/a
firewall n/a
ipv6 no
reproducible yes
hardware dual core atom 1.6, 1gb ram
hi guys, i'm not sure if this is an issue that has been fixed in later versions or not, not even sure if the issue can easily be determined. this is an embedded freenas install, sabnzbd and its related files are accessed and run from a ZFS array (/usr containing the necessary binaries copied over at boot to a 396 meg ramdisk).
everything runs fine, until a large download (greater than ~10 gigs seems to do the trick) completes. parts download fine, but when par2 starts, i get an unexplained crash, all that shows in the log is...
when i start sab back up, it tries to start the par2 check again, i get the message "killed" in the console, and that's it, back where i started from, par2 running but sab crashed, and nothing in the log.
i reproduced this twice, both by starting sab manually and by simply rebooting the box and letting the startup scripts handle it.
now, here's the kicker, when i start it non-daemon and just watch it over SSH, it starts up fine...par2 going, next download going, everything seems happy.
OS freebsd (freenas)
skin n/a
firewall n/a
ipv6 no
reproducible yes
hardware dual core atom 1.6, 1gb ram
hi guys, i'm not sure if this is an issue that has been fixed in later versions or not, not even sure if the issue can easily be determined. this is an embedded freenas install, sabnzbd and its related files are accessed and run from a ZFS array (/usr containing the necessary binaries copied over at boot to a 396 meg ramdisk).
everything runs fine, until a large download (greater than ~10 gigs seems to do the trick) completes. parts download fine, but when par2 starts, i get an unexplained crash, all that shows in the log is...
Code: Select all
2010-10-19 18:58:00,175::INFO::[sabnzbd] Saving data for SABnzbd_article_q4JOrl in /mnt/media/extensions/sabnzbd/cache/SABnzbd_article_q4JOrl
2010-10-19 18:58:00,657::INFO::[downloader] Thread 4@secure.usenetserver.com:443: part12of391.uBEXJAFpzTPfMt$XIvDc@postin.things.org done
2010-10-19 18:58:00,659::INFO::[decoder] Decoding <Article: article=part12of391.uBEXJAFpzTPfMt$XIvDc@postin.things.org, bytes=397121, partnum=12, art_id=None>
2010-10-19 18:58:00,678::INFO::[articlecache] Flushing <Article: article=part12of391.uBEXJAFpzTPfMt$XIvDc@postin.things.org, bytes=397121, partnum=12, art_id=SABnzbd_article_iehwvH> to disk
2010-10-19 18:58:00,679::INFO::[sabnzbd] Saving data for SABnzbd_article_iehwvH in /mnt/media/extensions/sabnzbd/cache/SABnzbd_article_iehwvH
2010-10-19 19:11:42,873::INFO::--------------------------------
2010-10-19 19:11:42,900::INFO::SABnzbd.py-0.4.12 (rev=2799)
2010-10-19 19:11:42,901::INFO::Platform = posix
2010-10-19 19:11:42,902::INFO::Python-version = 2.6.4 (r264:75706, Feb 17 2010, 10:45:15)
[GCC 4.2.1 20070719 [FreeBSD]]i reproduced this twice, both by starting sab manually and by simply rebooting the box and letting the startup scripts handle it.
now, here's the kicker, when i start it non-daemon and just watch it over SSH, it starts up fine...par2 going, next download going, everything seems happy.
