Recently something new has started for me on my Unraid.  Although the system is up and running, I lose the ability to browse to my shares from any system (Windows, Linux, etc).  When looking at the log I see some errors about being "out of memory."  I'm not running any Dockers or VMs.  The problem clears up after a reboot but comes back.

 

Running quad core with 2 Gb of RAM.  It's been running fine in this config for years.  I did recently update to 6.4.0 from 6.3.x and that's when the issues seem to have started.  I apologize I don't have any logs, since I recently rebooted.

 

I'll try to get some logs uploaded.

 

thanks in advance

2GB of RAM is stretching it, would recommend to upgrade to 4GB.

 

I have 4GB of RAM and have been running for years with months of up-time, but this latest version has been causing me problems after a few days of running.

 

Are you seeing anything like this in the logs?
 

Feb 15 03:45:35 NAS nginx: 2018/02/15 03:45:35 [crit] 2796#2796: *504395 pwrite() "/var/lib/nginx/client_body/0000001105" failed (28: No space left on device), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Feb 15 03:46:29 NAS emhttpd: error: shcmd_test, 1180: Cannot allocate memory (12): system
Feb 15 03:46:59 NAS kernel: php[28283]: segfault at 0 ip 0000000000603e0d sp 00007fff33673170 error 4 in php[400000+74a000]
Feb 15 03:48:01 NAS crond[1530]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb 15 03:48:17 NAS nginx: 2018/02/15 03:48:17 [crit] 2796#2796: *504783 pwrite() "/var/lib/nginx/client_body/0000001106" failed (28: No space left on device), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Feb 15 03:49:01 NAS crond[1530]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null)
Feb 15 03:50:01 NAS crond[1530]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null)
Feb 15 03:51:01 NAS crond[1530]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /Feb 15 04:08:24 NAS rpc.mountd[2727]: Cannot export /mnt/user/Movies, possibly unsupported filesystem or fsid= required
Feb 15 04:08:24 NAS rsyslogd: action 'action 0' resumed (module 'builtin:omfile') [v8.29.0 try http://www.rsyslog.com/e/2359 ]

 

I have 4GB of RAM and have been running for years with months of up-time, but this latest version has been causing me problems after a few days of running.
 
Are you seeing anything like this in the logs?
 

Feb 15 03:45:35 NAS nginx: 2018/02/15 03:45:35 [crit] 2796#2796: *504395 pwrite() "/var/lib/nginx/client_body/0000001105" failed (28: No space left on device), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"Feb 15 03:46:29 NAS emhttpd: error: shcmd_test, 1180: Cannot allocate memory (12): systemFeb 15 03:46:59 NAS kernel: php[28283]: segfault at 0 ip 0000000000603e0d sp 00007fff33673170 error 4 in php[400000+74a000]Feb 15 03:48:01 NAS crond[1530]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/nullFeb 15 03:48:17 NAS nginx: 2018/02/15 03:48:17 [crit] 2796#2796: *504783 pwrite() "/var/lib/nginx/client_body/0000001106" failed (28: No space left on device), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"Feb 15 03:49:01 NAS crond[1530]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null)Feb 15 03:50:01 NAS crond[1530]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null)Feb 15 03:51:01 NAS crond[1530]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /Feb 15 04:08:24 NAS rpc.mountd[2727]: Cannot export /mnt/user/Movies, possibly unsupported filesystem or fsid= requiredFeb 15 04:08:24 NAS rsyslogd: action 'action 0' resumed (module 'builtin:omfile') [v8.29.0 try http://www.rsyslog.com/e/2359 ]

 

Yes the “unable to fork” is familiar.

I am now maxed out at 4Gbs and haven’t had any lockups. Please keep the great info coming.




Sent from my iPhone using Tapatalk