Joe Posted March 5, 2011 Share Posted March 5, 2011 This happens on a regular basis. After a while the standard management page will no longer come up even by IP address. The server is still working (thankfully) as the shares are still accessible, Transmission torrent web is still working, and the :8080 page is working. Is there a way to restart the standard page as that is how I start and stop the array to shut it down? Anybody else see this. I am running 4.5.6 I believe. Quote Link to comment
dgaschk Posted March 5, 2011 Share Posted March 5, 2011 This is an indication of RAM becoming too full. How much RAM do you have and which add-ons are you running? Quote Link to comment
Joe Posted March 5, 2011 Author Share Posted March 5, 2011 Thanks for the response. The server has 8GB and the 8080 menu this is the RAM stats Memory Info (from /usr/bin/free) total used free shared buffers cached Mem: 8310492 530596 7779896 0 3768 461028 -/+ buffers/cache: 65800 8244692 Swap: 0 0 0 Thanks Joe Quote Link to comment
CNDdrdave Posted March 5, 2011 Share Posted March 5, 2011 I too see this, sometimes its the main interface that stops, sometimes its the 8080 interface. The 8080 interface is easy to restart from a terminal session /boot/unmenu/uu and that seems to bring the 8080 interface back. Tho when MAIN stops, im not shure how to get it back.... (I have 3 UNRAID Towers, #2 currently is not responding to main though its up, works, and the 8080 interface works (cept no main through it either) Also - I had a folder get wrong permissions, using midnight commander i tried to correct it - but lo and behold, even duplicating the settings of a "good" folder, the permissions were STILL 40777 !!!! NOT 42777 as the good folder showed - how do i correct this from the terminal directly (looking up CHMOD doccs now) The shutdown of unmenu or menu happens alot on all my towers. How can i assist in the troubleshooting process? Quote Link to comment
mbryanr Posted March 5, 2011 Share Posted March 5, 2011 I had this happen today. Here is the sequence of events: 1. Unable to reach unRAID MAIN 2. Stopped array from unMENU. 3. Shutdown from unMENU. 4. Restarted by hitting the power button 5. Upon restart, unable to reach unMENU, but could reach MAIN and unRAID-Web 6. Rebooted from MAIN, and able to reach all ports. Quote Link to comment
kasper Posted March 5, 2011 Share Posted March 5, 2011 I am new to UnRaid and no very little about Linnux but I have the same problem with the web interface ceasing to respond about 20 minutes after starting the box. The shares still work so I can still access the content, just can't start/stop the array. This happens to me on all the versions I have tried, 4.7 5B5 and 5B6. Obviously a power reboot corrects it. It is interesting to note that I have an LCD monitor on the box and the freeze of the web interface, only happens sometime after the LCD goes into suspend mode and the disks have spun down. Telnet still works. Is there a Linux command to type from the command line that will restart it. The motherboard is an new Asus MicroATX M4A78LT with and AMD Athlon II and a single 2gb RAM chip. The system has been running about a week, but the problem has only occurred in the last 2 or 3 days. Quote Link to comment
Joe L. Posted March 5, 2011 Share Posted March 5, 2011 Step one. Perform a memory test. Quote Link to comment
Joe Posted March 5, 2011 Author Share Posted March 5, 2011 Now that there are 3 of us reporting the problem I seriously doubt a memory issue. Especially since we all have the same issue consistently on more than 3 servers, running various versions. Is there a name for the process or demon running the web menu that we can try stopping and starting? Joe Quote Link to comment
kasper Posted March 5, 2011 Share Posted March 5, 2011 Now that there are 3 of us reporting the problem I seriously doubt a memory issue. Especially since we all have the same issue consistently on more than 3 servers, running various versions. Is there a name for the process or demon running the web menu that we can try stopping and starting? Joe And for the linux virgins like me tell me how to execute it Thanks Quote Link to comment
kasper Posted March 6, 2011 Share Posted March 6, 2011 I may be completely off the mark with this one and am still testing but I think I may have had success in restarting the web service by the followin. From the terminal or a telnet session. Log on as root CD /usr cd /sbin exec inetd The service does not start immediately, but within about 30 seconds I can connect again. Maybe co-incidence but am waiting for more failures to retest Quote Link to comment
kasper Posted March 6, 2011 Share Posted March 6, 2011 Further to the above. I have started copying files to the box and the web server has not failed for the last couple of hours while I am copying. So must be something associated with disks powering down as I only started spinning down the disks a couple of days ago (I am still experimenting with things) and that is about when my problem started. A colleague of mine suggested the following from the command line or telnet. To restart the webserver use these commands killall emhttp /usr/local/sbin/emhttp & Quote Link to comment
dgaschk Posted March 6, 2011 Share Posted March 6, 2011 Joe L. is the person who is most likely to help you all resolve this issue. Everyone start their own threads and follow his advise. Quote Link to comment
kasper Posted March 6, 2011 Share Posted March 6, 2011 One final post. But wait there is more. The server crashed again after 3 hours, interestingly after I closed a telnet window from another computer. Leaving it running overnight with the telnet session logged on to see what happens. Report in the morning Quote Link to comment
dgaschk Posted March 6, 2011 Share Posted March 6, 2011 Capture the syslog with tail as described here http://lime-technology.com/forum/index.php?topic=9880.0 Quote Link to comment
prostuff1 Posted March 6, 2011 Share Posted March 6, 2011 One final post. But wait there is more. The server crashed again after 3 hours, interestingly after I closed a telnet window from another computer. Leaving it running overnight with the telnet session logged on to see what happens. Report in the morning The server crashed or emhttp crashed? There is a huge difference! your above command is not quite enough to get emhttp going properly. You need to type: nohup /usr/local/sbin/emhttp & Quote Link to comment
SSD Posted March 6, 2011 Share Posted March 6, 2011 In general, when asking for help, it is wise to run the tests and post the results. Saying it's unlikely the helper suggested test will uncover the problem is not the kind of response that leads to further help. Quote Link to comment
kasper Posted March 6, 2011 Share Posted March 6, 2011 Prostuff 1 you are technically correct. The NAS box did not crash but the web interface to it did. Quote Link to comment
kasper Posted March 6, 2011 Share Posted March 6, 2011 Capture the syslog with tail as described here http://lime-technology.com/forum/index.php?topic=9880.0 Right attached is the syslog tail which shows very little. Also attached is a copy of the syslog. Hope all this helps as it seems to be increasing in severity. Now the web interface won't connect anymore within a few minutes of the box being rebooted. Syslog_tail_0703_2.txt syslog.txt Quote Link to comment
prostuff1 Posted March 6, 2011 Share Posted March 6, 2011 Right attached is the syslog tail which shows very little. Also attached is a copy of the syslog. Hope all this helps as it seems to be increasing in severity. Now the web interface won't connect anymore within a few minutes of the box being rebooted. The no connect for a couple of minutes is likely because of some Journaled Transactions that might be being replayed if the server was shut down improperly. Quote Link to comment
mazma Posted March 6, 2011 Share Posted March 6, 2011 not sure if this is the same issues being reported here, but I did recently have an experience where I also couldn't connect to the web menu. I could ping and browse shares on the box and had connectivity just fine on my mac to everything else. Other macs in the house could connect to the web menu just fine, but not mine. In the end rebooting the router fixed it. Weird. Quote Link to comment
marcusone Posted March 6, 2011 Share Posted March 6, 2011 I have had this issue with 4.7 as well. Seems intermitent (RAM not near fully utilized, telnet, shares, uuMenu all work fine, but unraid's menu dies and a reboot returns it to normal. Sorry didn't think to take logs, as I was changing things and thought it might be that causing it. Sounds like 4.7 may have a minor bug. If it happens again I'll take and post a log. Quote Link to comment
CNDdrdave Posted March 11, 2011 Share Posted March 11, 2011 Hmmm the :8080 interface is working - and the regular web interface is not. What is the command to restart the Web service (80) as the NAS is working fine, just no access to the main control interface, which IS a handy thing for some things. is /usr/local/sbin/emhttp & the correct command JUST TO RESTART THE :80 interface? Quote Link to comment
kasper Posted March 11, 2011 Share Posted March 11, 2011 As a follow up. Another member suggested not leaving the web interface open for long periods. So I have been opening it up, doing something then closing the browser. So far this has worked 80 % of the time. A couple of times on initial run it goes into its waiting for 192.168.... mode and takes about 5 minutes to actually load the page, but before it was virtually every time. Note that the web server does not seem to stop, it just goes incredibly slow at responding and eventually gets there. Through all this unMenu doesn't exhibit any of the symptoms Regards Wayne Quote Link to comment
dgaschk Posted March 11, 2011 Share Posted March 11, 2011 Mar 7 05:52:25 NAS emhttp: unRAID System Management Utility version 5.0-beta6 Mar 7 05:52:25 NAS emhttp: Copyright (C) 2005-2011, Lime Technology, LLC Mar 7 05:52:25 NAS emhttp: Pro key detected, GUID: 1005-B113-07A8-0807B128EB78 Mar 7 05:52:25 NAS emhttp: diskSpinupGroupMask.1 not found Mar 7 05:52:25 NAS kernel: emhttp[2177]: segfault at 0 ip b751a96c sp bfa40580 error 4 in libc-2.11.1.so[b74ea000+15c000] Mar 7 05:53:20 NAS emhttp: unRAID System Management Utility version 5.0-beta6 Mar 7 05:53:20 NAS emhttp: Copyright (C) 2005-2011, Lime Technology, LLC Mar 7 05:53:20 NAS emhttp: Pro key detected, GUID: 1005-B113-07A8-0807B128EB78 Mar 7 05:53:20 NAS emhttp: diskSpinupGroupMask.1 not found Mar 7 05:53:20 NAS kernel: emhttp[2221]: segfault at 0 ip b746a96c sp bfcf7c80 error 4 in libc-2.11.1.so[b743a000+15c000] The tail log show emhttp crashing with a segfault directly after a reference to spinup group mask. Try disabling spinup groups and see if that helps. EDIT: I just realized that you are running beta software. Use 4.7 if you want reliable performance. Please report this bug in a version 5.0 forum. Welcome to the beta test community. Quote Link to comment
kasper Posted March 11, 2011 Share Posted March 11, 2011 Mar 7 05:52:25 NAS emhttp: unRAID System Management Utility version 5.0-beta6 Mar 7 05:52:25 NAS emhttp: Copyright (C) 2005-2011, Lime Technology, LLC Mar 7 05:52:25 NAS emhttp: Pro key detected, GUID: 1005-B113-07A8-0807B128EB78 Mar 7 05:52:25 NAS emhttp: diskSpinupGroupMask.1 not found Mar 7 05:52:25 NAS kernel: emhttp[2177]: segfault at 0 ip b751a96c sp bfa40580 error 4 in libc-2.11.1.so[b74ea000+15c000] Mar 7 05:53:20 NAS emhttp: unRAID System Management Utility version 5.0-beta6 Mar 7 05:53:20 NAS emhttp: Copyright (C) 2005-2011, Lime Technology, LLC Mar 7 05:53:20 NAS emhttp: Pro key detected, GUID: 1005-B113-07A8-0807B128EB78 Mar 7 05:53:20 NAS emhttp: diskSpinupGroupMask.1 not found Mar 7 05:53:20 NAS kernel: emhttp[2221]: segfault at 0 ip b746a96c sp bfcf7c80 error 4 in libc-2.11.1.so[b743a000+15c000] The tail log show emhttp crashing with a segfault directly after a reference to spinup group mask. Try disabling spinup groups and see if that helps. EDIT: I just realized that you are running beta software. Use 4.7 if you want reliable performance. Please report this bug in a version 5.0 forum. Welcome to the beta test community. Interesting I thought I had disabled Spinup Groups I will need to recheck. Thanks for your research. As I said in another thread I have tried V4.7 and the problem existed in that version also. 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.