Hiker Posted October 3, 2011 Share Posted October 3, 2011 I'm running unRAID 5b12a and, when looking at my syslog today, saw a ton of errors that I've never seen before. An example in my syslog (attached) is from Oct 03, 09:24:32 Any ideas on what's suddenly causing this? syslog-2011-10-03.txt Quote Link to comment
prostuff1 Posted October 3, 2011 Share Posted October 3, 2011 I'm running unRAID 5b12a and, when looking at my syslog today, saw a ton of errors that I've never seen before. An example in my syslog (attached) is from Oct 03, 09:24:32 Any ideas on what's suddenly causing this? Looks like you are running out of RAM. What are you currently doing on the server? What addon's installed and what other things are/where you doing? Quote Link to comment
Hiker Posted October 3, 2011 Author Share Posted October 3, 2011 Addons: unMENU with monthly parity check, openssh/ssl, python, screen, SABnzbd-SickBeard-CouchPotato (all three manually installed) I did suspect CouchPotato might be the cause actually. It was preclearing 2x 2TB drives in separate screen sessions and looking at the preclear finish logs, the last of them finished 4 secs after the last of these errors (there have been no such failures since my preclears finished). The server has 6GB at present. Just checked memory usage and it was using around 5.8GB (I just stopped all python servers and checked memory usage; dropped to about 5.5GB. I then stopped the array and it dropped to around 370MB. Restarted the array, no real jump but I'll monitor it). unRAID did report around 5GB of cached memory. Thanks for the reply. Will leave it a day or so running the python servers and see if mem usage climbs again. I know CouchPotato in particular is known for mem leaks. Thanks for the reply. Quote Link to comment
prostuff1 Posted October 3, 2011 Share Posted October 3, 2011 Addons: unMENU with monthly parity check, openssh/ssl, python, screen, SABnzbd-SickBeard-CouchPotato (all three manually installed) I did suspect CouchPotato might be the cause actually. It was preclearing 2x 2TB drives in separate screen sessions and looking at the preclear finish logs, the last of them finished 4 secs after the last of these errors (there have been no such failures since my preclears finished). The server has 6GB at present. Just checked memory usage and it was using around 5.8GB (I just stopped all python servers and checked memory usage; dropped to about 5.5GB. I then stopped the array and it dropped to around 370MB. Restarted the array, no real jump but I'll monitor it). unRAID did report around 5GB of cached memory. Thanks for the reply. Will leave it a day or so running the python servers and see if mem usage climbs again. I know CouchPotato in particular is known for mem leaks. Thanks for the reply. If I had to guess I would say that the combination of running SAB, SickBeard, CouchPotato, and the 2 preclears is what caused the messages. Might want to run a memtest overnight if you have not already. Quote Link to comment
Hiker Posted October 3, 2011 Author Share Posted October 3, 2011 Quick update: I've started watching a 10GB HD rip from the server and memory usage is climbing like crazy. After less than 5mins of watching, it's climbed another 1GB (and still going) Quote Link to comment
prostuff1 Posted October 3, 2011 Share Posted October 3, 2011 Quick update: I've started watching a 10GB HD rip from the server and memory usage is climbing like crazy. After less than 5mins of watching, it's climbed another 1GB (and still going) That is normal. By design Linux will use any free ram for buffering. Quote Link to comment
Hiker Posted October 3, 2011 Author Share Posted October 3, 2011 Once I finish watching something, shouldn't unRAID then clear the cache? it seems this is the root of the problem; I'd been watching a movie yesterday and when I started the 2 preclears, it was enough to eventually cause the failures. Quote Link to comment
prostuff1 Posted October 3, 2011 Share Posted October 3, 2011 Once I finish watching something, shouldn't unRAID then clear the cache? it seems this is the root of the problem; I'd been watching a movie yesterday and when I started the 2 preclears, it was enough to eventually cause the failures. Nope, the linux kernel controls that, not unRAID directly. Quote Link to comment
Hiker Posted October 3, 2011 Author Share Posted October 3, 2011 Ok. It's never happened before I started preclearing multiple drives in separate screen sessions. Guess it's just something I can live with. Quote Link to comment
joeman2116 Posted October 30, 2011 Share Posted October 30, 2011 I was wondering what might be causing the cron errors. Unraid5 bld 12A it appears to be working fine System Log Oct 28 22:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 28 22:54:28 Tower kernel: mdcmd (25): spindown 0 Oct 28 22:54:29 Tower kernel: mdcmd (26): spindown 1 Oct 28 23:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 00:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 01:32:14 Tower kernel: mdcmd (27): spindown 0 Oct 29 01:32:15 Tower kernel: mdcmd (28): spindown 1 Oct 29 01:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 02:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 03:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 04:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 05:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 06:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 07:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 08:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 09:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 10:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 11:43:26 Tower in.telnetd[22078]: connect from 192.168.1.146 (192.168.1.146) Oct 29 11:43:28 Tower login[22079]: ROOT LOGIN on '/dev/pts/1' from 'acer1' Oct 29 11:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 12:15:22 Tower kernel: usb 1-1: USB disconnect, device number 2 Oct 29 12:15:25 Tower kernel: usb 1-1: new high speed USB device number 5 using ehci_hcd Oct 29 12:15:25 Tower kernel: scsi6 : usb-storage 1-1:1.0 Oct 29 12:15:26 Tower kernel: scsi 6:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 2 Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] 33093632 512-byte logical blocks: (16.9 GB/15.7 GiB) Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] Write Protect is off Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] Mode Sense: 03 00 00 00 Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] No Caching mode page present Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] Assuming drive cache: write through Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] No Caching mode page present Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] Assuming drive cache: write through Oct 29 12:15:26 Tower kernel: sda: sda1 Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] No Caching mode page present Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] Assuming drive cache: write through Oct 29 12:15:26 Tower kernel: sd 6:0:0:0: [sda] Attached SCSI removable disk Oct 29 12:15:30 Tower ntfs-3g[25075]: Version 2010.3.6 integrated FUSE 27 Oct 29 12:15:30 Tower ntfs-3g[25075]: Mounted /dev/sda1 (Read-Write, label "hipstreet16", NTFS 3.1) Oct 29 12:15:30 Tower ntfs-3g[25075]: Cmdline options: rw,umask=111,dmask=000 Oct 29 12:15:30 Tower ntfs-3g[25075]: Mount options: rw,silent,allow_other,nonempty,relatime,fsname=/dev/sda1,blkdev,blksize=4096,default_permissions Oct 29 12:15:30 Tower ntfs-3g[25075]: Global ownership and permissions enforced, configuration type 1 Oct 29 12:21:11 Tower kernel: mdcmd (29): spindown 2 Oct 29 12:21:11 Tower kernel: mdcmd (30): spindown 3 Oct 29 12:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 12:54:24 Tower kernel: mdcmd (31): spindown 0 Oct 29 12:54:25 Tower kernel: mdcmd (32): spindown 1 Oct 29 13:33:29 Tower kernel: mdcmd (33): spindown 1 Oct 29 13:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 14:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 15:21:28 Tower kernel: mdcmd (34): spindown 2 Oct 29 15:21:38 Tower kernel: mdcmd (35): spindown 3 Oct 29 15:39:43 Tower kernel: mdcmd (36): spindown 1 Oct 29 15:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 16:46:03 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 17:09:56 Tower kernel: mdcmd (37): spindown 2 Oct 29 17:10:06 Tower kernel: mdcmd (38): spindown 3 Oct 29 17:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 18:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 19:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 20:43:38 Tower kernel: mdcmd (39): spindown 0 Oct 29 20:43:39 Tower kernel: mdcmd (40): spindown 1 Oct 29 20:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 21:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 21:53:24 Tower in.telnetd[6659]: connect from 192.168.1.42 (192.168.1.42) Oct 29 21:53:27 Tower login[6660]: ROOT LOGIN on '/dev/pts/1' from '192.168.1.42' Oct 29 21:56:35 Tower su[6753]: Successful su for ts by root Oct 29 21:56:35 Tower su[6753]: + /dev/pts/1 root:ts Oct 29 21:58:02 Tower in.telnetd[6790]: connect from 192.168.1.42 (192.168.1.42) Oct 29 21:58:04 Tower login[6791]: ROOT LOGIN on '/dev/pts/1' from '192.168.1.42' Oct 29 21:58:46 Tower su[6822]: Successful su for ts by root Oct 29 21:58:46 Tower su[6822]: + /dev/pts/1 root:ts Oct 29 22:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 29 23:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 00:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 00:48:09 Tower kernel: mdcmd (41): spindown 0 Oct 30 00:48:10 Tower kernel: mdcmd (42): spindown 1 Oct 30 01:33:29 Tower kernel: mdcmd (43): spindown 0 Oct 30 01:33:30 Tower kernel: mdcmd (44): spindown 1 Oct 30 01:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 02:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 03:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 04:40:01 Tower apcupsd[1642]: apcupsd exiting, signal 15 Oct 30 04:40:01 Tower apcupsd[1642]: apcupsd shutdown succeeded Oct 30 04:40:03 Tower apcupsd[16642]: apcupsd 3.14.10 (13 September 2011) slackware startup succeeded Oct 30 04:40:03 Tower apcupsd[16642]: NIS server startup succeeded Oct 30 04:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 05:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 06:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 07:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 08:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 09:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 10:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 11:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 12:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 13:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 14:46:03 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 15:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 16:11:34 Tower kernel: mdcmd (45): spindown 0 Oct 30 16:11:35 Tower kernel: mdcmd (46): spindown 1 Oct 30 16:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Oct 30 17:46:01 Tower crond[1115]: failed parsing crontab for user root: cron="" Any help would be appreciated Joe Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.