NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas 102 6.2.2 sabnzbd crash no admin page
Hi,
I have problem with a readynas 102. Once a day when I download using sabnzbd, sabnzbd crash and then my admin page crash also with a "Device is not connected".
I updated sabnzbd to the latest version 0.7.20 and I don't have any information in sabnzbd logs.
The last entry in sabnzbd.log is : Decoding lKvz4el1vqsDlO9HuPK5@JBinUp.local.
In systemd-journal.log I have this :
And when sabnzbd crash I lost connection to the admin page and other stuff and I have to do an systemctl restart readynasd to work again.
I don't know if it's sabnzbd crash or system crash when sabnzbd download a file.
Can anyone help me?
Thanks
I have problem with a readynas 102. Once a day when I download using sabnzbd, sabnzbd crash and then my admin page crash also with a "Device is not connected".
I updated sabnzbd to the latest version 0.7.20 and I don't have any information in sabnzbd logs.
The last entry in sabnzbd.log is : Decoding lKvz4el1vqsDlO9HuPK5@JBinUp.local.
In systemd-journal.log I have this :
Mar 15 19:48:40 MyNas systemd[1]: ctscand.service: main process exited, code=killed, status=9
Mar 15 19:48:41 MyNas systemd[1]: Unit ctscand.service entered failed state.
Mar 15 19:48:44 MyNas systemd[1]: ctscand.service holdoff time over, scheduling restart.
Mar 15 19:49:21 MyNas systemd[1]: ctscand.service: main process exited, code=exited, status=255
Mar 15 19:49:21 MyNas systemd[1]: Unit ctscand.service entered failed state.
Mar 15 19:49:25 MyNas systemd[1]: ctscand.service holdoff time over, scheduling restart.
Mar 15 19:49:35 MyNas systemd[1]: ctscand.service: main process exited, code=exited, status=255
Mar 15 19:49:35 MyNas systemd[1]: Unit ctscand.service entered failed state.
Mar 15 19:49:36 MyNas systemd[1]: fvapp-sabnzbd.service: main process exited, code=killed, status=9
Mar 15 19:49:37 MyNas ctscand-watchdog[18989]: WATCHDOG_SEC: 150
Mar 15 19:49:37 MyNas ctscand-watchdog[18989]: Unable to create pid file: File exists
And when sabnzbd crash I lost connection to the admin page and other stuff and I have to do an systemctl restart readynasd to work again.
I don't know if it's sabnzbd crash or system crash when sabnzbd download a file.
Can anyone help me?
Thanks
8 Replies
Replies have been turned off for this discussion
- What firmware version are you running?
Can you disable the anti-virus service and see if you still run into this issue?
After you encounter this problem and restart readynasd can you download your logs ASAP and email the zip file to me (see the link in my sig)? - Hi,
firmware 6.2.2 and with or without antivirus it's the same.
I just did a test and sabnzbd still the same, I try to get the log and sending to you.
Thanks - Couldn't see enough logs to determine what was going on. Did you reboot the NAS before grabbing the logs? I was hoping that you would have been able to grab them without needing to reboot.
- No, I didn't reboot the Nas I just did an " systemctl restart readynasd".
But I'm not surprised me too I can't find anything on the log but I don't know what is happening when sabnzbd try to put decode file on the nas and then admin page and other applications crash too.
But for a week it's happening all the time.
Do you whant other logs?
I know I have bad sector on disk 2 but sabnzbd is on disk 1 and I have JBOD system so normally this should not be a problem.
I don't whant to reset all data, I tried an os reinstall multiple time and still this error.
I didn't try to delete sabnzbd and reinstall it but how can I backup sabnzbd configuration before I do that?
Where I can search any traces?
Thank you. - The OS is on both disks. Though apps are installed onto a data volume if a disk has a problem that may be relevant.
You may wish to try 6.2.3 Beta: http://www.readynas.com/forum/viewtopic.php?t=78866 - One more think, maybe it help.
This is always happening when sabnzbd try to decode hugh file more than 800 Mo. So I don't think that beta firmware can help here, maybe it's a OS limitation?
Thanks. - Hi,
I have new intel, I manage to do an dmesg before sabnzbd crash and I have this error:
Out of memory: Kill process 20213 (ctscand) score 1085 or sacrifice child
Killed process 20213 (ctscand) total-vm:150600kB, anon-rss:132kB, file-rss:116kB
Do you have any idea?
Thanks - Something is using up lots of memory forcing the NAS to stop some services.
Perhaps what you are doing with sabnzbd requires more memory. As the memory (RAM) is soldered on to the 102 it is not upgradeable.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
