December 17, 201213 yr If I were you I'd shut down and restart selecting "Mem-test" from the boot menu...If it segfaulted before and you restarted and it segfaulted again for a lib, it sounds like you may have a memory issue.
April 15, 201313 yr Hi, Is this issue have been fixed on a rc? Am running 5.0-rc5 since month now and sometimes i have this issues Thanks
October 2, 201312 yr Getting the issue here on 5.0 i386. I'm running 8Gb of memory with Sab, sickbeard, crashplan and cache_dir plugins. Cheers Ryan
October 16, 201312 yr Getting the issue here on 5.0 i386. I'm running 8Gb of memory with Sab, sickbeard, crashplan and cache_dir plugins. Cheers Ryan I believe 8GB is overkill since Unraid is running x86 which maximum support is at 4GB. I do experience the same issue as you and looks like cache_dir is causing it on my end. syslogs.txt
October 17, 201312 yr Getting the issue here on 5.0 i386. I'm running 8Gb of memory with Sab, sickbeard, crashplan and cache_dir plugins. Cheers Ryan I believe 8GB is overkill since Unraid is running x86 which maximum support is at 4GB. I do experience the same issue as you and looks like cache_dir is causing it on my end. I've been running cache_dirs on my systems for YEARS... one server has 512 Meg of RAM, the other 4Gig. It is not cache_dirs, but how you are using it. Limit the depth it is scanning, or the directories it is scanning. you just need to monitor the "low memory" usage. (having more memory above 4G uses more "low" memory to track the high-memory. As a result, adding more memory above 4Gig actually decreases the "low" memory available.) Sab and sickbeard are memory hogs...
December 19, 201411 yr Any way of restarting "emhttp" without bringing the array down and unmounting disks?
December 19, 201411 yr Any way of restarting "emhttp" without bringing the array down and unmounting disks? No.
Archived
This topic is now archived and is closed to further replies.