October 11, 201312 yr After creating the 1st share ("Shared" folder) within the HTTP interface the page is no longer accessible. This is a new install with pro.key. I can access the machine in unmenu and SMB is still up. I could not figure out how to get the HTTP cpanel back up. After this happened I ran a few commands that I found in the forum: /usr/sbin exec inetd killall emhttp /usr/local/sbin/emhttp & nohup /usr/local/sbin/emhttp & From http://lime-technology.com/forum/index.php?topic=11503.0 Here is a log http://screencast.com/t/9RiL6gUwC This machine has been fully tested with PC-Check and passed. It has shown no sign of problems. Only add-on is unmenu. 1. How do restart / start emhttp properly without rebooting the server? 2. Will this happen again in the future? 3. If so, how do I stop that from happening? 4. What does the above log really state?
October 12, 201312 yr After creating the 1st share ("Shared" folder) within the HTTP interface the page is no longer accessible. This is a new install with pro.key. I can access the machine in unmenu and SMB is still up. I could not figure out how to get the HTTP cpanel back up. After this happened I ran a few commands that I found in the forum: /usr/sbin exec inetd killall emhttp /usr/local/sbin/emhttp & nohup /usr/local/sbin/emhttp & From http://lime-technology.com/forum/index.php?topic=11503.0 Here is a log http://screencast.com/t/9RiL6gUwC This machine has been fully tested with PC-Check and passed. It has shown no sign of problems. Only add-on is unmenu. 1. How do restart / start emhttp properly without rebooting the server? This is not possible. 2. Will this happen again in the future? Yes. 3. If so, how do I stop that from happening? Correct the problem with the system. 4. What does the above log really state? Attach the complete log, zipped, to a post, for advise.
October 14, 201312 yr Author After rebooting the system I went back to the share and I see this http://screencast.com/t/keqrxbynC. After change this setting here http://screencast.com/t/DAe2SyLR1Oj and click apply this is when the HTTP GUI fails.
October 14, 201312 yr Author Thanks but this is a clean install. Past having done connected it to the active directory and start up unmenu.
October 15, 201312 yr It's really annoying that the GUI is randomly going unresponsive and there is no way to restart it. #1 If one doesn't install the powerdown script there isn't even a safe way to restart the whole server! The stock powerdown also calls emhttp for a shut down! #2 Without installing "third party" plugins you can't assess the status of the array if the GUI is not working. You may be running on parity with a failed drive without notice. #3 You can be really unlucky if you have to do a rebuild or some crtitical operation on a live array when the GUI goes offline. From my point of view this is a serious issue and I'm very astonished that the dev isn't taking it as one! We can provide many syslogs but after having a closer look at some, there is no log of emhttp when it fails. While linux claims to be 365x24/7 this GUI is definitely not! GUI unresponsive 1 - here GUI unresponsive 2 - here GUI unresponsive 3 - here this thread and some more when using the search...
October 16, 201312 yr The GUI does not appear to be freezing when the system is booted in safe mode. One of the add-ons is causing this issue. There is something incompatible in the system because this is not a common problem.
Archived
This topic is now archived and is closed to further replies.