core dump every few days

Report & discuss bugs found in SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
tixetsal
Newbie
Newbie
Posts: 8
Joined: June 7th, 2013, 8:58 pm

core dump every few days

Post by tixetsal »

Version: 0.7.14-1
OS: Arch Linux
Install-type: Arch User Repository
Skin (if applicable): Default
Firewall Software: None
Are you using IPV6? No
Is the issue reproducible? Yes, it happens every few days.

I have been experiencing crashes. I've noticed that this error message is sometimes the last thing that appears in the logs before the crash:

Code: Select all

2013-07-21 20:50:33,496::INFO::[__init__:499] Fetching http://nzbs.org/getnzb/5acaa3e66f80afd144e70fabec3ffe11.nzb&i=XXXXX&r=SANITIZED
2013-07-21 20:50:33,546::INFO::[nzbqueue:211] Saving queue
2013-07-21 20:50:33,547::DEBUG::[__init__:829] Saving data for SABnzbd_nzo_R7ONZS in /home/shaun/.sabnzbd.ini/admin/future
2013-07-21 20:50:33,548::INFO::[__init__:904] Saving data for queue9.sab in /home/shaun/.sabnzbd.ini/admin/queue9.sab 

Code: Select all

2013-07-25 04:14:43,479::INFO::[__init__:499] Fetching http://nzbs.org/getnzb/91b40ad67b077c7e9ad0b9c479df87dd.nzb&i=XXXXX&r=SANITIZED
2013-07-25 04:14:43,670::INFO::[nzbqueue:211] Saving queue
2013-07-25 04:14:43,690::INFO::[__init__:904] Saving data for queue9.sab in /home/shaun/.sabnzbd.ini/admin/queue9.sab 
Has anyone else experienced this as well?
Last edited by tixetsal on July 27th, 2013, 7:03 pm, edited 1 time in total.
tixetsal
Newbie
Newbie
Posts: 8
Joined: June 7th, 2013, 8:58 pm

core dump every few days

Post by tixetsal »

Code: Select all

sudo systemctl status sabnzbd
sabnzbd.service - SABnzbd binary newsreader
   Loaded: loaded (/usr/lib/systemd/system/sabnzbd.service; enabled)
   Active: failed (Result: core-dump) since Thu 2013-07-25 04:14:51 EDT; 8h ago
 Main PID: 18030 (code=dumped, signal=ABRT)
   CGroup: name=systemd:/system/sabnzbd.service

Jul 25 04:14:45 brpc sh[18030]: 7f7737685000-7f7737686000 r--p 00008000 08:05 268412 /usr/lib/python2.7/li...array.so
Jul 25 04:14:45 brpc sh[18030]: 7f7737686000-7f7737688000 rw-p 00009000 08:05 268412 /usr/lib/python2.7/li...array.so
Jul 25 04:14:45 brpc sh[18030]: 7f7737688000-7f773768c000 r-xp 00000000 08:05 268430 /usr/lib/python2.7/li...elect.so
Jul 25 04:14:45 brpc sh[18030]: 7f773768c000-7f773788c000 ---p 00004000 08:05 268430 /usr/lib/python2.7/li...elect.so
Jul 25 04:14:45 brpc sh[18030]: 7f773788c000-7f773788d000 r--p 00004000 08:05 268430 /usr/lib/python2.7/li...elect.so
Jul 25 04:14:45 brpc sh[18030]: 7f773788d000-7f773788f000 rw-p 00005000 08:05 268430 /usr/lib/python2.7/li...elect.so
Jul 25 04:14:45 brpc sh[18030]: 7f773788f000-7f7737892000 r-xp 00000000 08:05 268406 /usr/lib/python2.7/li...fcntl.so
Jul 25 04:14:45 brpc sh[18030]: 7f7737892000-7f7737a91000 ---p 00003000 08:05 268406 /usr/lib/python2.7/li...fcntl.so
Jul 25 04:14:51 brpc systemd[1]: sabnzbd.service: main process exited, code=dumped, status=6/ABRT
Jul 25 04:14:51 brpc systemd[1]: Unit sabnzbd.service entered failed state. 
EDIT: I'm now using monit to watch the process and restart sabnzbd when it crashes. My best guess is that it's caused by some interaction between couchpotato and sabnzbd.
ptheabstract
Newbie
Newbie
Posts: 1
Joined: November 23rd, 2013, 10:30 am

Re: core dump every few days

Post by ptheabstract »

Hey -- just wondering if you managed to resolve this.. I'm having the same issue :s

Thanks!
tixetsal
Newbie
Newbie
Posts: 8
Joined: June 7th, 2013, 8:58 pm

Re: core dump every few days

Post by tixetsal »

I did. It believe it was caused by bad sectors on a failing hard drive.

As a workaround, monit works really well to keep things moving until you can pinpoint the problem. I hope that helps.
Post Reply