SABnzbd shuts down/crashes on DS212J
Forum rules
Help us help you:
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.
SABnzbd shuts down/crashes on DS212J
Dear,
For over a year now I am using my DS211J without any problem as a true download station. To do this I use the 3rd party tools SABnzbd, sickbeard and couchpotato.
Recently I bought a DS212J with the exact same purpose.
However the DiskStation shuts the SABnzbd package down regularly during download. The only way to continue is to manualy restart the package in package center.
I realise that your first reaction would be to take this issue to the developer of the package. This is already done.
I tested with several different versions (0.5.6 - 0.6.XX) from several different developers (SynoCommunity & Zebulon). All of them have the same problem.
I also tested these SABnzbd packages with my older DS211J and here not a single crash occurs.
All my folders have the correct rights and the SABnzbd application uses the exact same settings as it does on my DS211J.
To execute my tests with other versions from other developers, I always correctly deleted the previous one.
When downloading files the crash occurs sometimes after minutes, sometimes after hours. The size of the download does not matter. Sometimes the app crashes with a download of 8GB, sometimes with 300MB.
More disturbing is the fact that when I restart the SABnzbd package, it occurred a couple times that the complete DiskStation crashes and reboots. I then receive the error 'System booted up from an improper shutdown'.
There is however one consistent property when it crashes/shuts down:
When I check my logfiles in SABnzbd the crash always occurs right after the following kind of line:
19:57:30,706::INFO::[assembler:85] Decoding /volume1/varia/sabnzbd/incomplete/Brothers.and.Sisters.S05.DVDRip.XviD-REWARD/brothers.and.sisters.s05e05.dvdrip.xvid-reward.r11 yenc
Because I have no other ideas how to solve this, I already sent a ticket to synology because I have the feeling that the internal memory is corrupt. They replied with the answer that I should do a hard reset and reinstall dsm. They also said that they do not support 3rd party packages...as expected.
I have not did this reinstall of DSM because I was hoping any of you have another idea to solve this?
For over a year now I am using my DS211J without any problem as a true download station. To do this I use the 3rd party tools SABnzbd, sickbeard and couchpotato.
Recently I bought a DS212J with the exact same purpose.
However the DiskStation shuts the SABnzbd package down regularly during download. The only way to continue is to manualy restart the package in package center.
I realise that your first reaction would be to take this issue to the developer of the package. This is already done.
I tested with several different versions (0.5.6 - 0.6.XX) from several different developers (SynoCommunity & Zebulon). All of them have the same problem.
I also tested these SABnzbd packages with my older DS211J and here not a single crash occurs.
All my folders have the correct rights and the SABnzbd application uses the exact same settings as it does on my DS211J.
To execute my tests with other versions from other developers, I always correctly deleted the previous one.
When downloading files the crash occurs sometimes after minutes, sometimes after hours. The size of the download does not matter. Sometimes the app crashes with a download of 8GB, sometimes with 300MB.
More disturbing is the fact that when I restart the SABnzbd package, it occurred a couple times that the complete DiskStation crashes and reboots. I then receive the error 'System booted up from an improper shutdown'.
There is however one consistent property when it crashes/shuts down:
When I check my logfiles in SABnzbd the crash always occurs right after the following kind of line:
19:57:30,706::INFO::[assembler:85] Decoding /volume1/varia/sabnzbd/incomplete/Brothers.and.Sisters.S05.DVDRip.XviD-REWARD/brothers.and.sisters.s05e05.dvdrip.xvid-reward.r11 yenc
Because I have no other ideas how to solve this, I already sent a ticket to synology because I have the feeling that the internal memory is corrupt. They replied with the answer that I should do a hard reset and reinstall dsm. They also said that they do not support 3rd party packages...as expected.
I have not did this reinstall of DSM because I was hoping any of you have another idea to solve this?
Re: SABnzbd shuts down/crashes on DS212J
I have no Synology experience, but can you logon to your Synology with ssh/telnet (so: a terminal session), and then start SABnzbd? That way all output should appear in the terminal, including a crash message.
You should keep the terminal session open until SAB stops, and then copy the output in the terminal session to this thread.
You should keep the terminal session open until SAB stops, and then copy the output in the terminal session to this thread.
Re: SABnzbd shuts down/crashes on DS212J
Yes of course. I will do this tonight or tomorrowmorning the latest and keep you posted
Re: SABnzbd shuts down/crashes on DS212J
I opened a SSH to my NAS.
Then I cd'd to: usr/local/sabnzbd/share/SABnzbd/SABnzbd.py
But then it starts with port 8080 while I configured port 9200. And I can also not access my web browser (not on both ports).
Am I starting the program correctly in the terminal?
Then I cd'd to: usr/local/sabnzbd/share/SABnzbd/SABnzbd.py
But then it starts with port 8080 while I configured port 9200. And I can also not access my web browser (not on both ports).
Am I starting the program correctly in the terminal?
Re: SABnzbd shuts down/crashes on DS212J
There's probably a file sabnzbd.ini somewhere on the Synology system. Start sabnzbd with the option "-f <fullPathtoINIfile>"tboheeren wrote:I opened a SSH to my NAS.
Then I cd'd to: usr/local/sabnzbd/share/SABnzbd/SABnzbd.py
But then it starts with port 8080 while I configured port 9200. And I can also not access my web browser (not on both ports).
Am I starting the program correctly in the terminal?
HTH
Re: SABnzbd shuts down/crashes on DS212J
Okay thanks. I can perform the test(s) in the beginning of next week. I will post the results here then.
Re: SABnzbd shuts down/crashes on DS212J
As promised: the output
012-05-23 11:36:31,045::INFO::[assembler:85] Decoding /volume1/varia/incomplete/John Carter 2012 720p Bluray 101/John Carter 2012 720p Bluray - 101.part24.rar yenc
2012-05-23 11:36:41,419::INFO::[__init__:846] Saving data for totals9.sab in /volume1/varia/admin/totals9.sab
2012-05-23 11:36:44,854::INFO::[assembler:85] Decoding /volume1/varia/incomplete/John Carter 2012 720p Bluray 101/John Carter 2012 720p Bluray - 101.part25.rar yenc
Segmentation fault (core dumped)
012-05-23 11:36:31,045::INFO::[assembler:85] Decoding /volume1/varia/incomplete/John Carter 2012 720p Bluray 101/John Carter 2012 720p Bluray - 101.part24.rar yenc
2012-05-23 11:36:41,419::INFO::[__init__:846] Saving data for totals9.sab in /volume1/varia/admin/totals9.sab
2012-05-23 11:36:44,854::INFO::[assembler:85] Decoding /volume1/varia/incomplete/John Carter 2012 720p Bluray 101/John Carter 2012 720p Bluray - 101.part25.rar yenc
Segmentation fault (core dumped)
Re: SABnzbd shuts down/crashes on DS212J
Ouch: segmentation fault. That is a serious error. AFAIK, SABnzbd (as a python script) can not cause that error itself. It can be caused by programs called by SAB (like the unrar executable), or by the python executable, or by a (unstable) system itself (think buggy RAM / OS / etc).tboheeren wrote:As promised: the output
012-05-23 11:36:31,045::INFO::[assembler:85] Decoding /volume1/varia/incomplete/John Carter 2012 720p Bluray 101/John Carter 2012 720p Bluray - 101.part24.rar yenc
2012-05-23 11:36:41,419::INFO::[__init__:846] Saving data for totals9.sab in /volume1/varia/admin/totals9.sab
2012-05-23 11:36:44,854::INFO::[assembler:85] Decoding /volume1/varia/incomplete/John Carter 2012 720p Bluray 101/John Carter 2012 720p Bluray - 101.part25.rar yenc
Segmentation fault (core dumped)
The "assembler"-log message is from this part of the code of assenmbler.py:
Code: Select all
filepath = get_filepath(cfg.download_dir.get_path(), nzo, filename)
if filepath:
logging.info('Decoding %s %s', filepath, nzf.type)
try:
filepath = _assemble(nzf, filepath, dupe)
Re: SABnzbd shuts down/crashes on DS212J
Yesterday I did a hard reset in the DS212j. This allows you to reinstall DSM and format the system partition. Then a complete reinstall of sabnzbd, cp and sb.
All this did not help (as you can see in the latest output).
Your comment about buggy ram intrested me so I did a memory check in synology assistant. This returned 0 errors...
Hopefully shypike can indeed give some advice
All this did not help (as you can see in the latest output).
Your comment about buggy ram intrested me so I did a memory check in synology assistant. This returned 0 errors...
Hopefully shypike can indeed give some advice
Re: SABnzbd shuts down/crashes on DS212J
Your earlier posts suggest that the _yenc.pyd file crashes.
SABnzbd doesn't really need this, it's only used for speed reasons.
Maybe you can remove that specific file and try again?
I'm not sure where this file is in the package (and whether that's actually the name).
SABnzbd doesn't really need this, it's only used for speed reasons.
Maybe you can remove that specific file and try again?
I'm not sure where this file is in the package (and whether that's actually the name).
Re: SABnzbd shuts down/crashes on DS212J
I will try to locate the file.
In the meantime I did the following:
I received a patch from Synology to repair improper shutdowns. At the same time I removed the USB stick in the back of my synology. I did this because I checked my logfiles and it reported the following (the text below contains 3 improper shutdowns:
I also shutdown sickbeard & couchpotato. Both of them were using the USB stick. SABnzbd does not use the stick for logging.
At the moment I did 3 succesfull downloads, I will continue downloading today to see if crashes occur.
My question: is it possible that an old ubs stick caused all this?
On some forums people are having issues with this http://59.124.41.244/enu/viewtopic.php? ... 0&start=30
In the meantime I did the following:
I received a patch from Synology to repair improper shutdowns. At the same time I removed the USB stick in the back of my synology. I did this because I checked my logfiles and it reported the following (the text below contains 3 improper shutdowns:
Code: Select all
May 23 11:05:03 syslogd started: BusyBox v1.16.1
May 23 11:05:04 spacetool: spacetool.c:2214 [Info] Activate all VG
May 23 11:05:05 s30_synocheckuser: CheckGUserExist(1792): user [sabnzbd] not found!
May 23 11:05:05 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=sabnzbd:*:15483:0:99999:7:::
May 23 11:05:05 s30_synocheckuser: CheckGUserExist(1792): user [couchpotato] not found!
May 23 11:05:05 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=couchpotato:*:15483:0:99999:7:::
May 23 11:05:05 s30_synocheckuser: CheckGUserExist(1792): user [sickbeard] not found!
May 23 11:05:05 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=sickbeard:*:15483:0:99999:7:::
May 23 11:05:05 s30_synocheckuser: CheckGUserExist(1792): user [nzbget] not found!
May 23 11:05:05 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=nzbget:*:15483:0:99999:7:::
May 23 11:05:05 s42_synocheckgrp: SYNOICheckLocalGrp(315): replace szBuf=[users:x:100:couchpotato,sabnzbd,sickbeard,nzbget] with szOutBuf=[users:x:100:couchpotato,sabnzbd,nzbget,sickbeard]!
May 23 11:05:05 s42_synocheckgrp: SYNOICheckLocalGrp(357): Fix Local group files.
May 23 11:05:13 scemd: scemd.c:131 fan_type=3, raid_type=1, led_type=1, thermal_type=2, diskled_ctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=2, fan_number=1, ebox_type=1, pis_type=1, rtc_type=2
May 23 11:05:14 scemd: modules/fan_speed_adjust_common.c:116 Type: INTERNAL Fan Mode: LOW
May 23 11:05:15 scemd: modules/raid_sys_volume_check.c:150 MD0 active disks 2, designed disks 2
May 23 11:05:15 scemd: modules/raid_sys_volume_check.c:150 MD1 active disks 2, designed disks 2
May 23 11:05:15 scemd: modules/disk_hibernation.c:1685 Force hibernation enable, idle minutes 60
May 23 11:05:15 scemd: modules/disk_hibernation.c:1693 SATA Deep sleep timer 1
May 23 11:05:15 synoprint: printer_enable_ext.c:488 delete printer failed: no bus id
May 23 11:05:17 synocheckshare: Fix shares in smb.conf.
May 23 11:05:18 synocheckshare: service_disable_set.c(68)Not defined date : id=4
May 23 11:05:22 synousbdisk: RCClean succeeded
May 23 11:05:22 synosata: synosata.c:150 failed to enum all external sata devices
May 23 11:05:24 kernel: [ 68.060000] Got empty serial number. Generate serial number from product.
May 23 11:05:24 syno_hdd_util: Model:[ST2000DL003-9VT1], Firmware:[CC3C], S/N:[5YD6Q9S5] in [/dev/sdb] is not ssd
May 23 11:05:25 syno_hdd_util: Model:[ST2000DL003-9VT1], Firmware:[CC3C], S/N:[5YD6TPST] in [/dev/sda] is not ssd
May 23 11:05:25 heartbeatd: heartbeatd.c:170 Failed to get DDNS provider config: name = Synology
May 23 11:05:26 ddnsd: ddnsd.c:2086 First update for ChangeIP.com
May 23 11:05:26 hotplugd: hotplugd.c:988 failed get usb status from usb config, DEVICE=/proc/bus/usb/001/001, usbid=1d6b:0002:orion-ehci.0
May 23 11:05:26 hotplugd: ##### ACTION:add
May 23 11:05:26 hotplugd: DEVICE:/proc/bus/usb/001/001
May 23 11:05:26 hotplugd: DEVPATH:usb1
May 23 11:05:26 hotplugd: SUBSYSTEM:usb
May 23 11:05:26 hotplugd: hotplugd.c:763 Fail to recognize usb DEVNAME=, DEVPATH=usb1
May 23 11:05:26 hotplugd: hotplugd.c:1289 failed to setup usb config, (DEVPATH, DEVICE, ACTION, DEVNAME, INTERFACE)=(usb1, /proc/bus/usb/001/001, add, , )
May 23 11:05:26 hotplugd: hotplugd.c:988 failed get usb status from usb config, DEVICE=/proc/bus/usb/001/001, usbid=1d6b:0002:orion-ehci.0
May 23 11:05:26 hotplugd: ##### ACTION:add
May 23 11:05:26 hotplugd: DEVICE:/proc/bus/usb/001/001
May 23 11:05:26 hotplugd: DEVPATH:1-0:1.0
May 23 11:05:26 hotplugd: SUBSYSTEM:usb
May 23 11:05:26 hotplugd: INTERFACE:9/0/0
May 23 11:05:26 hotplugd: ##### ACTION:add
May 23 11:05:26 hotplugd: DEVICE:/proc/bus/usb/001/002
May 23 11:05:26 hotplugd: DEVPATH:1-1
May 23 11:05:26 hotplugd: SUBSYSTEM:usb
May 23 11:05:26 hotplugd: ##### ACTION:add
May 23 11:05:26 hotplugd: DEVICE:/proc/bus/usb/001/002
May 23 11:05:26 hotplugd: DEVPATH:1-1:1.0
May 23 11:05:26 hotplugd: SUBSYSTEM:usb
May 23 11:05:26 hotplugd: INTERFACE:9/0/0
May 23 11:05:26 hotplugd: hotplugd.c:790 ##### complete device hotplug!!
May 23 11:05:26 hotplugd: ##### ACTION:add
May 23 11:05:26 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 11:05:26 hotplugd: DEVPATH:1-1.1
May 23 11:05:26 hotplugd: SUBSYSTEM:usb
May 23 11:05:26 hotplugd: ##### ACTION:add
May 23 11:05:26 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 11:05:26 hotplugd: DEVPATH:1-1.1:1.0
May 23 11:05:26 hotplugd: SUBSYSTEM:usb
May 23 11:05:26 hotplugd: INTERFACE:8/6/80
May 23 11:05:29 kernel: [ 73.680000] drivers/scsi/sd.c (2344) Got USB disk
May 23 11:05:29 kernel: [ 73.740000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 11:05:29 kernel: [ 73.790000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 11:05:29 kernel: [ 73.830000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 11:05:31 hotplugd: ##### ACTION:add
May 23 11:05:31 hotplugd: DEVNAME:sdq
May 23 11:05:31 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 11:05:31 hotplugd: DEVGUID:06040514471500380
May 23 11:05:31 hotplugd: hotplugd.c (1401) ==== USB disk [sdq] plugged in ====
May 23 11:05:31 hotplugd: hotplugd.c:1402 goto USB disk, szDeviceName=sdq
May 23 11:05:31 hotplugd: hotplugd.c:1404 ret=-1, fsType=0
May 23 11:05:32 hotplugd: ##### ACTION:add
May 23 11:05:32 hotplugd: DEVNAME:sdq
May 23 11:05:32 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 11:05:32 hotplugd: DEVGUID:06040514471500380
May 23 11:05:32 hotplugd: DEVPATH:sdq
May 23 11:05:32 hotplugd: SUBSYSTEM:block
May 23 11:05:32 hotplugd: PHYSDEVPATH:/devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0/host2/target2:0:0/2:0:0:0
May 23 11:05:32 hotplugd: hotplugd.c:790 ##### complete device hotplug!!
May 23 11:05:32 hotplugd: hotplugd.c (1401) ==== USB disk [sdq] plugged in ====
May 23 11:05:32 hotplugd: hotplugd.c:1402 goto USB disk, szDeviceName=sdq
May 23 11:05:32 hotplugd: hotplugd.c:1404 ret=-1, fsType=0
May 23 11:07:23 scemd: scemd.c:328 stop manutild.
May 23 11:18:17 PkgMan.cgi: pkgtool.cpp:2445 No script for python
May 23 11:19:13 PkgMan.cgi: pkgtool.cpp:2445 No script for python
May 23 11:19:14 PkgMan.cgi: pkgtool.cpp:2445 No script for python
May 23 13:07:51 scemd: SCEMD: disk 2 wake up from hibernation
May 23 13:07:59 scemd: SCEMD: disk 1 wake up from hibernation
May 23 13:25:30 PkgMan.cgi: pkgtool.cpp:2445 No script for python
May 23 13:25:51 PkgMan.cgi: pkgtool.cpp:2445 No script for python
May 23 13:36:36 syslogd started: BusyBox v1.16.1
May 23 13:36:37 spacetool: spacetool.c:2214 [Info] Activate all VG
May 23 13:36:38 s30_synocheckuser: CheckGUserExist(1792): user [sabnzbd] not found!
May 23 13:36:38 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=sabnzbd:*:15483:0:99999:7:::
May 23 13:36:38 s30_synocheckuser: CheckGUserExist(1792): user [couchpotato] not found!
May 23 13:36:38 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=couchpotato:*:15483:0:99999:7:::
May 23 13:36:38 s30_synocheckuser: CheckGUserExist(1792): user [sickbeard] not found!
May 23 13:36:38 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=sickbeard:*:15483:0:99999:7:::
May 23 13:36:38 s30_synocheckuser: CheckGUserExist(1792): user [nzbget] not found!
May 23 13:36:38 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=nzbget:*:15483:0:99999:7:::
May 23 13:36:49 scemd: scemd.c:131 fan_type=3, raid_type=1, led_type=1, thermal_type=2, diskled_ctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=2, fan_number=1, ebox_type=1, pis_type=1, rtc_type=2
May 23 13:36:49 scemd: modules/fan_speed_adjust_common.c:116 Type: INTERNAL Fan Mode: LOW
May 23 13:36:50 scemd: modules/raid_sys_volume_check.c:150 MD0 active disks 2, designed disks 2
May 23 13:36:50 scemd: modules/raid_sys_volume_check.c:150 MD1 active disks 2, designed disks 2
May 23 13:36:50 scemd: modules/disk_hibernation.c:1685 Force hibernation enable, idle minutes 60
May 23 13:36:50 scemd: modules/disk_hibernation.c:1693 SATA Deep sleep timer 1
May 23 13:36:51 synoprint: printer_enable_ext.c:488 delete printer failed: no bus id
May 23 13:36:52 synocheckshare: Fix shares in smb.conf.
May 23 13:36:54 synocheckshare: service_disable_set.c(68)Not defined date : id=4
May 23 13:36:58 synousbdisk: RCClean succeeded
May 23 13:36:58 synosata: synosata.c:150 failed to enum all external sata devices
May 23 13:36:59 kernel: [ 71.390000] Got empty serial number. Generate serial number from product.
May 23 13:37:00 syno_hdd_util: Model:[ST2000DL003-9VT1], Firmware:[CC3C], S/N:[5YD6Q9S5] in [/dev/sdb] is not ssd
May 23 13:37:00 syno_hdd_util: Model:[ST2000DL003-9VT1], Firmware:[CC3C], S/N:[5YD6TPST] in [/dev/sda] is not ssd
May 23 13:37:01 heartbeatd: heartbeatd.c:170 Failed to get DDNS provider config: name = Synology
May 23 13:37:02 hotplugd: hotplugd.c:988 failed get usb status from usb config, DEVICE=/proc/bus/usb/001/001, usbid=1d6b:0002:orion-ehci.0
May 23 13:37:02 hotplugd: ##### ACTION:add
May 23 13:37:02 hotplugd: DEVICE:/proc/bus/usb/001/001
May 23 13:37:02 hotplugd: DEVPATH:usb1
May 23 13:37:02 hotplugd: SUBSYSTEM:usb
May 23 13:37:02 hotplugd: hotplugd.c:763 Fail to recognize usb DEVNAME=, DEVPATH=usb1
May 23 13:37:02 hotplugd: hotplugd.c:1289 failed to setup usb config, (DEVPATH, DEVICE, ACTION, DEVNAME, INTERFACE)=(usb1, /proc/bus/usb/001/001, add, , )
May 23 13:37:02 hotplugd: hotplugd.c:988 failed get usb status from usb config, DEVICE=/proc/bus/usb/001/001, usbid=1d6b:0002:orion-ehci.0
May 23 13:37:02 hotplugd: ##### ACTION:add
May 23 13:37:02 hotplugd: DEVICE:/proc/bus/usb/001/001
May 23 13:37:02 hotplugd: DEVPATH:1-0:1.0
May 23 13:37:02 hotplugd: SUBSYSTEM:usb
May 23 13:37:02 hotplugd: INTERFACE:9/0/0
May 23 13:37:02 ddnsd: ddnsd.c:2086 First update for ChangeIP.com
May 23 13:37:02 hotplugd: ##### ACTION:add
May 23 13:37:02 hotplugd: DEVICE:/proc/bus/usb/001/002
May 23 13:37:02 hotplugd: DEVPATH:1-1
May 23 13:37:02 hotplugd: SUBSYSTEM:usb
May 23 13:37:02 hotplugd: ##### ACTION:add
May 23 13:37:02 hotplugd: DEVICE:/proc/bus/usb/001/002
May 23 13:37:02 hotplugd: DEVPATH:1-1:1.0
May 23 13:37:02 hotplugd: SUBSYSTEM:usb
May 23 13:37:02 hotplugd: INTERFACE:9/0/0
May 23 13:37:02 hotplugd: hotplugd.c:790 ##### complete device hotplug!!
May 23 13:37:02 hotplugd: ##### ACTION:add
May 23 13:37:02 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 13:37:02 hotplugd: DEVPATH:1-1.1
May 23 13:37:02 hotplugd: SUBSYSTEM:usb
May 23 13:37:02 hotplugd: ##### ACTION:add
May 23 13:37:02 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 13:37:02 hotplugd: DEVPATH:1-1.1:1.0
May 23 13:37:02 hotplugd: SUBSYSTEM:usb
May 23 13:37:02 hotplugd: INTERFACE:8/6/80
May 23 13:37:05 kernel: [ 76.960000] drivers/scsi/sd.c (2344) Got USB disk
May 23 13:37:05 kernel: [ 77.020000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 13:37:05 kernel: [ 77.050000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 13:37:05 kernel: [ 77.090000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 13:37:07 hotplugd: ##### ACTION:add
May 23 13:37:07 hotplugd: DEVNAME:sdq
May 23 13:37:07 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 13:37:07 hotplugd: DEVGUID:06040514471500380
May 23 13:37:07 hotplugd: hotplugd.c (1401) ==== USB disk [sdq] plugged in ====
May 23 13:37:07 hotplugd: hotplugd.c:1402 goto USB disk, szDeviceName=sdq
May 23 13:37:07 hotplugd: hotplugd.c:1404 ret=-1, fsType=0
May 23 13:37:08 hotplugd: ##### ACTION:add
May 23 13:37:08 hotplugd: DEVNAME:sdq
May 23 13:37:08 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 13:37:08 hotplugd: DEVGUID:06040514471500380
May 23 13:37:08 hotplugd: DEVPATH:sdq
May 23 13:37:08 hotplugd: SUBSYSTEM:block
May 23 13:37:08 hotplugd: PHYSDEVPATH:/devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0/host2/target2:0:0/2:0:0:0
May 23 13:37:08 hotplugd: hotplugd.c:790 ##### complete device hotplug!!
May 23 13:37:08 hotplugd: hotplugd.c (1401) ==== USB disk [sdq] plugged in ====
May 23 13:37:08 hotplugd: hotplugd.c:1402 goto USB disk, szDeviceName=sdq
May 23 13:37:08 hotplugd: hotplugd.c:1404 ret=-1, fsType=0
May 23 13:38:25 logout.cgi: login.c (810) SynoCgiLoginRemoveUser failed.
May 23 13:38:59 scemd: scemd.c:328 stop manutild.
May 23 13:39:08 PkgMan.cgi: pkgtool.cpp:2445 No script for python
May 23 13:39:12 PkgMan.cgi: pkgtool.cpp:2445 No script for python
May 23 13:39:12 PkgMan.cgi: pkgtool.cpp:2445 No script for python
May 23 13:46:56 syslogd started: BusyBox v1.16.1
May 23 13:46:57 spacetool: spacetool.c:2214 [Info] Activate all VG
May 23 13:46:58 s30_synocheckuser: CheckGUserExist(1792): user [sabnzbd] not found!
May 23 13:46:58 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=sabnzbd:*:15483:0:99999:7:::
May 23 13:46:58 s30_synocheckuser: CheckGUserExist(1792): user [couchpotato] not found!
May 23 13:46:58 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=couchpotato:*:15483:0:99999:7:::
May 23 13:46:58 s30_synocheckuser: CheckGUserExist(1792): user [sickbeard] not found!
May 23 13:46:58 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=sickbeard:*:15483:0:99999:7:::
May 23 13:46:58 s30_synocheckuser: CheckGUserExist(1792): user [nzbget] not found!
May 23 13:46:58 s30_synocheckuser: CheckConsistentWithPasswd(2003): user not exist in /etc/passwd, and remove it. szBuf=nzbget:*:15483:0:99999:7:::
May 23 13:47:07 scemd: scemd.c:131 fan_type=3, raid_type=1, led_type=1, thermal_type=2, diskled_ctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=2, fan_number=1, ebox_type=1, pis_type=1, rtc_type=2
May 23 13:47:07 scemd: modules/fan_speed_adjust_common.c:116 Type: INTERNAL Fan Mode: LOW
May 23 13:47:08 scemd: modules/raid_sys_volume_check.c:150 MD0 active disks 2, designed disks 2
May 23 13:47:08 scemd: modules/raid_sys_volume_check.c:150 MD1 active disks 2, designed disks 2
May 23 13:47:09 scemd: modules/disk_hibernation.c:1685 Force hibernation enable, idle minutes 60
May 23 13:47:09 scemd: modules/disk_hibernation.c:1693 SATA Deep sleep timer 1
May 23 13:47:09 synoprint: printer_enable_ext.c:488 delete printer failed: no bus id
May 23 13:47:10 synocheckshare: Fix shares in smb.conf.
May 23 13:47:12 synocheckshare: service_disable_set.c(68)Not defined date : id=4
May 23 13:47:16 synousbdisk: RCClean succeeded
May 23 13:47:16 synosata: synosata.c:150 failed to enum all external sata devices
May 23 13:47:17 kernel: [ 69.280000] Got empty serial number. Generate serial number from product.
May 23 13:47:19 syno_hdd_util: Model:[ST2000DL003-9VT1], Firmware:[CC3C], S/N:[5YD6Q9S5] in [/dev/sdb] is not ssd
May 23 13:47:19 syno_hdd_util: Model:[ST2000DL003-9VT1], Firmware:[CC3C], S/N:[5YD6TPST] in [/dev/sda] is not ssd
May 23 13:47:19 heartbeatd: heartbeatd.c:170 Failed to get DDNS provider config: name = Synology
May 23 13:47:20 ddnsd: ddnsd.c:2086 First update for ChangeIP.com
May 23 13:47:20 hotplugd: hotplugd.c:988 failed get usb status from usb config, DEVICE=/proc/bus/usb/001/001, usbid=1d6b:0002:orion-ehci.0
May 23 13:47:20 hotplugd: ##### ACTION:add
May 23 13:47:20 hotplugd: DEVICE:/proc/bus/usb/001/001
May 23 13:47:20 hotplugd: DEVPATH:usb1
May 23 13:47:20 hotplugd: SUBSYSTEM:usb
May 23 13:47:20 hotplugd: hotplugd.c:763 Fail to recognize usb DEVNAME=, DEVPATH=usb1
May 23 13:47:20 hotplugd: hotplugd.c:1289 failed to setup usb config, (DEVPATH, DEVICE, ACTION, DEVNAME, INTERFACE)=(usb1, /proc/bus/usb/001/001, add, , )
May 23 13:47:20 hotplugd: hotplugd.c:988 failed get usb status from usb config, DEVICE=/proc/bus/usb/001/001, usbid=1d6b:0002:orion-ehci.0
May 23 13:47:20 hotplugd: ##### ACTION:add
May 23 13:47:20 hotplugd: DEVICE:/proc/bus/usb/001/001
May 23 13:47:20 hotplugd: DEVPATH:1-0:1.0
May 23 13:47:20 hotplugd: SUBSYSTEM:usb
May 23 13:47:20 hotplugd: INTERFACE:9/0/0
May 23 13:47:20 hotplugd: ##### ACTION:add
May 23 13:47:20 hotplugd: DEVICE:/proc/bus/usb/001/002
May 23 13:47:20 hotplugd: DEVPATH:1-1
May 23 13:47:20 hotplugd: SUBSYSTEM:usb
May 23 13:47:20 hotplugd: ##### ACTION:add
May 23 13:47:20 hotplugd: DEVICE:/proc/bus/usb/001/002
May 23 13:47:20 hotplugd: DEVPATH:1-1:1.0
May 23 13:47:20 hotplugd: SUBSYSTEM:usb
May 23 13:47:20 hotplugd: INTERFACE:9/0/0
May 23 13:47:20 hotplugd: hotplugd.c:790 ##### complete device hotplug!!
May 23 13:47:20 hotplugd: ##### ACTION:add
May 23 13:47:20 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 13:47:20 hotplugd: DEVPATH:1-1.1
May 23 13:47:20 hotplugd: SUBSYSTEM:usb
May 23 13:47:20 hotplugd: ##### ACTION:add
May 23 13:47:20 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 13:47:20 hotplugd: DEVPATH:1-1.1:1.0
May 23 13:47:20 hotplugd: SUBSYSTEM:usb
May 23 13:47:20 hotplugd: INTERFACE:8/6/80
May 23 13:47:23 kernel: [ 74.830000] drivers/scsi/sd.c (2344) Got USB disk
May 23 13:47:23 kernel: [ 74.890000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 13:47:23 kernel: [ 74.940000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 13:47:23 kernel: [ 74.990000] sd 2:0:0:0: [sdq] Assuming drive cache: write through
May 23 13:47:25 hotplugd: ##### ACTION:add
May 23 13:47:25 hotplugd: DEVNAME:sdq
May 23 13:47:25 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 13:47:25 hotplugd: DEVGUID:06040514471500380
May 23 13:47:25 hotplugd: hotplugd.c (1401) ==== USB disk [sdq] plugged in ====
May 23 13:47:25 hotplugd: hotplugd.c:1402 goto USB disk, szDeviceName=sdq
May 23 13:47:25 hotplugd: hotplugd.c:1404 ret=-1, fsType=0
May 23 13:47:26 hotplugd: ##### ACTION:add
May 23 13:47:26 hotplugd: DEVNAME:sdq
May 23 13:47:26 hotplugd: DEVICE:/proc/bus/usb/001/003
May 23 13:47:26 hotplugd: DEVGUID:06040514471500380
May 23 13:47:26 hotplugd: DEVPATH:sdq
May 23 13:47:26 hotplugd: SUBSYSTEM:block
May 23 13:47:26 hotplugd: PHYSDEVPATH:/devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0/host2/target2:0:0/2:0:0:0
May 23 13:47:26 hotplugd: hotplugd.c:790 ##### complete device hotplug!!
May 23 13:47:26 hotplugd: hotplugd.c (1401) ==== USB disk [sdq] plugged in ====
May 23 13:47:26 hotplugd: hotplugd.c:1402 goto USB disk, szDeviceName=sdq
May 23 13:47:26 hotplugd: hotplugd.c:1404 ret=-1, fsType=0
May 23 13:48:24 logout.cgi: login.c (810) SynoCgiLoginRemoveUser failed.
May 23 13:50:19 syslogd started: BusyBox v1.16.1
At the moment I did 3 succesfull downloads, I will continue downloading today to see if crashes occur.
My question: is it possible that an old ubs stick caused all this?
On some forums people are having issues with this http://59.124.41.244/enu/viewtopic.php? ... 0&start=30
Re: SABnzbd shuts down/crashes on DS212J
Yes, SABnzbd is defenseless against malfunctioning storage and so are most programs.tboheeren wrote:My question: is it possible that an old ubs stick caused all this?
This is especially true of the "admin" and "incomplete" folders.
Write issues are one thing, but if corrupt data comes back from important files this can cause crashes.
For the final destination the assumption is not full reliability.
Re: SABnzbd shuts down/crashes on DS212J
I understand.
However, SABnzbd was not using this USB stick. Not for logfiles, admin or any kind of folders. So that would mean that a USB stick that is not being used by an application, still could crash that particular application?
Anyway to test I will:
download a lot today without USB stick with sickbeard & couchpotato disabled (24/05)
download a lot on 25/05 without USB stick with sickbeard enabled & couchpotato disabled
download a lot on 26/05 without USB stick with all enabled.
I will keep you posted.
However, SABnzbd was not using this USB stick. Not for logfiles, admin or any kind of folders. So that would mean that a USB stick that is not being used by an application, still could crash that particular application?
Anyway to test I will:
download a lot today without USB stick with sickbeard & couchpotato disabled (24/05)
download a lot on 25/05 without USB stick with sickbeard enabled & couchpotato disabled
download a lot on 26/05 without USB stick with all enabled.
I will keep you posted.
Re: SABnzbd shuts down/crashes on DS212J
Does the OS do anything with it?
A defective stick could possibly influence operation, but that's just speculation.
A defective stick could possibly influence operation, but that's just speculation.
Re: SABnzbd shuts down/crashes on DS212J
It was only used to handle the logfiles from SickBeard & CouchPotato.shypike wrote:Does the OS do anything with it?
A defective stick could possibly influence operation, but that's just speculation.
In DSM (the OS) the usb stick was mounted and could be accessed with file station. But it was not doing something with it actively.

