MrLondon Posted January 26, 2013 Share Posted January 26, 2013 Hi there, all seemed fine with the server and suddenly today I gotten an unexpected error message from the unRaid server. I upgraded last weekend to rc10 and it ran fine for a week, but I was not really using it much, today and yesterday I transferred lots of files back to the server and now I gotten strange errors in the syslog and the playback was stuttering with xbmc. Should I be concerned that something has failed? Is it hardware or software? Any help will be great Ingo syslog-2013-01-26.zip Quote Link to comment
RobJ Posted January 26, 2013 Share Posted January 26, 2013 I'm not an expert on OOM's, but that is what it looks to me. I believe you ran out of memory. One possible cause is the constant renewing of IP, it claims to get a new lease for one hour (3600 seconds, which is much quicker than necessary), but actually renews it every 30 minutes. This is filling up the syslog, and wasting memory. Either log into your router (or other DHCP server) and change the IP lease interval to something like once every 2 days or once a week, or better yet, set UnRAID to not use DHCP, use a static IP of 192.168.0.110 (which is what your router is giving you anyway, over and over and over). You can change that in the UnRAID Network Settings page. Quote Link to comment
MrLondon Posted January 27, 2013 Author Share Posted January 27, 2013 thanks for that, I have changed it now to static IP address, however it has run out of memory again. I have simple features installed, could that cause the memory issues? Also unmenu. root@Tower:~# cat /proc/meminfo MemTotal: 3971136 kB MemFree: 210660 kB Buffers: 314992 kB Cached: 3150424 kB SwapCached: 0 kB Active: 328616 kB Inactive: 2894684 kB Active(anon): 30180 kB Inactive(anon): 148 kB Active(file): 298436 kB Inactive(file): 2894536 kB Unevictable: 272232 kB Mlocked: 0 kB HighTotal: 3100104 kB HighFree: 10500 kB LowTotal: 871032 kB LowFree: 200160 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 30116 kB Mapped: 14968 kB Shmem: 212 kB Slab: 154816 kB SReclaimable: 114292 kB SUnreclaim: 40524 kB KernelStack: 1088 kB PageTables: 916 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 1985568 kB Committed_AS: 100636 kB VmallocTotal: 122880 kB VmallocUsed: 16016 kB VmallocChunk: 94548 kB DirectMap4k: 6136 kB DirectMap2M: 907264 kB after a reboot of the server I gotten much more free memory root@Tower:/proc# cat meminfo MemTotal: 3971136 kB MemFree: 3482364 kB Buffers: 3876 kB Cached: 346004 kB SwapCached: 0 kB Active: 86764 kB Inactive: 273484 kB Active(anon): 10432 kB Inactive(anon): 148 kB Active(file): 76332 kB Inactive(file): 273336 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 3100104 kB HighFree: 2725748 kB LowTotal: 871032 kB LowFree: 756616 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 10324 kB Mapped: 8688 kB Shmem: 212 kB Slab: 19540 kB SReclaimable: 7196 kB SUnreclaim: 12344 kB KernelStack: 1560 kB PageTables: 560 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 1985568 kB Committed_AS: 67840 kB VmallocTotal: 122880 kB VmallocUsed: 16016 kB VmallocChunk: 104876 kB DirectMap4k: 6136 kB DirectMap2M: 907264 kB After I started to stream one program the memory went straight back up root@Tower:/proc# cat meminfo MemTotal: 3971136 kB MemFree: 156500 kB Buffers: 199700 kB Cached: 3298060 kB SwapCached: 0 kB Active: 219112 kB Inactive: 3038056 kB Active(anon): 30028 kB Inactive(anon): 156 kB Active(file): 189084 kB Inactive(file): 3037900 kB Unevictable: 270464 kB Mlocked: 0 kB HighTotal: 3100104 kB HighFree: 21556 kB LowTotal: 871032 kB LowFree: 134944 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 29844 kB Mapped: 13544 kB Shmem: 220 kB Slab: 177540 kB SReclaimable: 117112 kB SUnreclaim: 60428 kB KernelStack: 1072 kB PageTables: 1112 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 1985568 kB Committed_AS: 111036 kB VmallocTotal: 122880 kB VmallocUsed: 16016 kB VmallocChunk: 104876 kB DirectMap4k: 6136 kB DirectMap2M: 907264 kB syslog-2013-01-27.zip Quote Link to comment
Helmonder Posted January 27, 2013 Share Posted January 27, 2013 No OOM errors but a lot of memory stuff in the log that should not be there... How much memory is in your system ? If you have more then 4 then look for the MEM=4095 parameter and try it out.. There is something flakey with unraid systems having more then 4gig in some hardware combinations. Quote Link to comment
RobJ Posted January 27, 2013 Share Posted January 27, 2013 The syslog is definitely much quieter now, without all of the IP renewals, but you have not rebooted yet, to recover that memory. After restart, can you provide a fresh syslog? Quote Link to comment
MrLondon Posted January 27, 2013 Author Share Posted January 27, 2013 I have only 4gb of memory installed in the server and never ran out of memory before I upgrade to rc10. syslog-2013-01-27_1.zip Quote Link to comment
dgaschk Posted January 28, 2013 Share Posted January 28, 2013 The memory allocated to buffers and cache can also be considered free because Linux will free that allocation if needed. Observing the MemFree value is not sufficient. The free commend will show free memory +/- cache & buffer. Run an overnight memtest. Quote Link to comment
PeterB Posted January 28, 2013 Share Posted January 28, 2013 thanks for that, I have changed it now to static IP address, however it has run out of memory again. What makes you believe that you have run out of memory? Are you seeing error messages? Quote Link to comment
RobJ Posted January 28, 2013 Share Posted January 28, 2013 thanks for that, I have changed it now to static IP address, however it has run out of memory again. What makes you believe that you have run out of memory? Are you seeing error messages? I told him earlier (perhaps wrongly) that I thought he might be running out of memory due to numerous memory allocation failures in the earlier syslogs, plus he had a process that was exploding his syslogs, using up memory. This last syslog does not have any memory faults, so far. It does show segfaults with inotifywait, and ends with very numerous symlink failures. The symlink failures could be an issue with faulty addon configuration, but I think both issues could also just be that some of the addons have not been updated for the latest UnRAID releases. Quote Link to comment
dgaschk Posted January 28, 2013 Share Posted January 28, 2013 The allocation errors in the first syslog all take place during Network IO. It could be a coincidence. 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.