May 29, 201214 yr Hi. I'm having an issue. Running latest unraid 5.0 rc3. I have SimpleFeatures installed along with 4 plugins installed (sab, sickbeard, couch potato, transmission). All plugins work fine, all running on the same nas, but every now and then if I try hit my nas on port 80 from a browser it just sits a connecting and never loads up simple features. If I reboot the array it loads up fine. Again all plugins still function as expected, just the home page hangs. In var/log/syslog there is the following: transmission-daemon[11877]: Saved pidfile "/var/run/transmission/transmission.pid" (daemon.c:500) transmission-daemon[11877]: Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:72) transmission-daemon[11877]: Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:72) transmission-daemon[11877]: Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwarding.c:93) transmission-daemon[11877]: Port Forwarding State changed from "Starting" to "" (port-forwarding.c:93) transmission-daemon[11877]: DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:247) sshd[11959]: Accepted password for root from xx.xx.xx.xx port 56614 ssh2 sshd[11963]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory sshd[11963]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory crond[1071]: exit status 1 from user root /usr/lib/sa/sa1 1 1 kernel: crond[12010]: segfault at b771b51c ip b771b51c sp bfdfbb34 error 15 in ld-2.11.1.so[b771b000+1000] crond[1071]: exit status 1 from user root /usr/lib/sa/sa1 1 1 kernel: crond[12076]: segfault at b771b51c ip b771b51c sp bfdfbb34 error 15 in ld-2.11.1.so[b771b000+1000] After searching these forums it appears segfault is a memory issue. Co-incidentally I added an extra 1GB memory about 3 days ago.
June 16, 201214 yr I'm having the same issue... exactly... I think it's related to crond hanging.... Every hour I get a segfault Jun 16 12:47:01 knox crond[1260]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jun 16 12:47:01 knox kernel: crond[27002]: segfault at b779351c ip b779351c sp bffd6df4 error 15 in ld-2.11.1.so[b7793000+1000] Jun 16 13:47:01 knox crond[1260]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jun 16 13:47:01 knox kernel: crond[30877]: segfault at b779351c ip b779351c sp bffd6df4 error 15 in ld-2.11.1.so[b7793000+1000] I thought it was related to the stats add-on of Simple Features because it had an hourly check in the cron. I have removed that add-on and the problem continues... whiteatom
June 16, 201214 yr At first glance I thought this might be related to the permission changes made to the 'root' account, however this change was implimented in rc4 Changes from 5.0-rc3 to 5.0-rc4 ------------------------------- - linux: use kernel version 3.0.33 - linux: add "AMD Family 10h+ temperature sensor" driver (k10temp) - linux: add "AMD Family 15h processor power" driver (fam15h_power) - linux: add "Intel 10GbE PCI Express" driver (ixgbe) - linux: add "SCSI generic support" (sg) - shfs: fix NFS stale file handle problems - samba (SMB protocol): put 'root' in 'invalid users' list in /etc/samba/smb.conf - samba (SMB protocol): set 'max protocol = SMB2' in /etc/samba/smb.conf instead of in /etc/rc.d/rc.samba - emhttp: when user deleted, purge user from all access lists - emhttp: improve start/stop array operations Syslog/s? Might help to pinpoint what is going on. Fairly sure this is an issue with SF though, not unRAID. After searching these forums it appears segfault is a memory issue. Co-incidentally I added an extra 1GB memory about 3 days ago. Restart your unRAID server and run memtest from the unRAID boot menu, leave it for at least 2 passes (preferably overnight) and post the results. It's very likely the memory you added is either faulty or could be an issue with the timings/mixing brands/speeds etc. Some motherboards are pickier than others with mixing & matching RAM. Alternatively just remove the stick you added and see if the issue goes away.
June 21, 201214 yr I have just totally removed SF.. so I'll let you know on the next 47 mins if this fixes the problem or not.
June 21, 201214 yr Problem gone with SF taken out. Going to re-add just the base and see what happens.
April 23, 201313 yr I have just added SF to the latest version of unraid (RC12). When I connected, it would not find the unraid home. So I typed the ip address, and the new plugin homepage loaded fine. Clicked on another tab, it hung and here I am now, with no homepage.
April 23, 201313 yr I have just added SF to the latest version of unraid (RC12). When I connected, it would not find the unraid home. So I typed the ip address, and the new plugin homepage loaded fine. Clicked on another tab, it hung and here I am now, with no homepage. You should post this on the SF thread with a syslog attached.
April 23, 201313 yr I have, but have not added the syslog yet. Will do. The plugin was not dead but dormant. Very very slow on my machine, timing out ever so often Sent from my GT-I9300 using Tapatalk 2
Archived
This topic is now archived and is closed to further replies.