[Solved] Is this Safe to do?


Recommended Posts

Okay, the long details are in my question about shutting down via Telnet, but before I try this sequence, I'd like to see if there's a better one.

 

My array is working fine;  but I can't get to the web GUI.  Interestingly, UnMenu responds; but it hangs if I click the "unRAID Main" link, so it can't get to the web GUI either.

 

I've found a couple references on how to reset the web GUI.  This seems to be the preferred set of commands:

 

killall emhttp

nohup /usr/local/sbin/emhttp &

 

Two questions:

 

(1)  Is that sequence "safe" -- meaning will it have any impact on the array itself (which is working fine)

(2)  What does "nohup" do/mean ?  I found a link that says it means "no hang up" -- does that mean it will try forever?

(3)  Is there a better way to restart the web GUI ?

 

Link to comment

The segfault is what I had remembered reading about -- but what you're saying is that's not an issue with 4.7 (which I what I'm running).

 

So ... this should be a "safe" sequence, right?

 

killall emhttp

nohup /usr/local/sbin/emhttp &

 

"Safe" meaning that if it doesn't work, the array will still be running -- I'll just still not have a webGUI.

 

... and if that doesn't work, I'll just click on the "Power Down" button on Unmenu's User Scripts page, which should shut down gracefully.  [Note that I tried typing "powerdown" in a telnet window last night, but it didn't work -- but I think that was the built-in powerdown;  not the "clean powerdown" script that I think UnMenu would use].    Or do you think it's better to use the sequence described in the wiki?  [stop samba; umount all the drives one-at-a-time;  then do a mdcmd stop] ... and if so, does that actually power down, or just stop everything?

Link to comment

The segfault is what I had remembered reading about -- but what you're saying is that's not an issue with 4.7 (which I what I'm running).

I hadn't seen it reported, nor had I encountered the segfault on 4.7

So ... this should be a "safe" sequence, right?

 

killall emhttp

nohup /usr/local/sbin/emhttp &

 

 

"Safe" meaning that if it doesn't work, the array will still be running -- I'll just still not have a webGUI.

Correct.  I remember on v5 that it gave segfault messages, but I could still telnet.

... and if that doesn't work, I'll just click on the "Power Down" button on Unmenu's User Scripts page, which should shut down gracefully.  [Note that I tried typing "powerdown" in a telnet window last night, but it didn't work -- but I think that was the built-in powerdown;  not the "clean powerdown" script that I think UnMenu would use].    Or do you think it's better to use the sequence described in the wiki?  [stop samba; umount all the drives one-at-a-time;  then do a mdcmd stop] ... and if so, does that actually power down, or just stop everything?

I'd try the powerdown in unMenu, and if that doesn't work - the command line described above.  It just cleanly stops everything, at which point you can hit the power button (without incurring a parity check on reboot).

Link to comment

Voila !!

 

Did this:

 

killall emhttp

nohup /usr/local/sbin/emhttp &

 

... and the WebGUI is now responding -- all okay;  no errors or anything.

 

No idea what killed the GUI, but nice to know it can be restarted ... and really nice that UnRAID itself continued to work perfectly.

 

Not sure I'm even going to bother with a reboot  :)

 

[Actually I will in a day or two;  but thought I'd see if the problem reoccurs first.  This server has been VERY reliable for the past 4 years or so ... I think 4.7 has only been rebooted twice since I installed it (current uptime is 93 days; when I rebooted it December after a long power outage it had been up something like 157 days).    This is, however, the first time I've ever lost the web GUI.

 

Link to comment

For future reference (if someone else has this problem and finds this discussion) ...

 

... I found several references to restarting emhttp (the web interface) causing segfaults with v5;  but as I was running v4.7 I went ahead and tried it (as noted above).

 

My original plan was to simply do a restart when I got the array back up;  but after it worked so smoothly I thought I'd give it a couple days to see if there were any residual effects.    It was working perfectly after a day;  so I did a parity check -- which worked perfectly.    So I let it run another couple days;  then did yet-another parity check (again perfect).    In between I copied 30-40 GB to the array;  and just for grins copied about the same FROM the array.    We also streamed a couple of movies.  Everything is working just fine.

 

So ... I'm not going to bother with a restart.    I generally only restart after a more-than-5-minute power failure (when the APC UPS package shuts it down); or if I'm adding a drive or upgrading the software;  so I'll just wait for the next one of those events  :)

 

I gather from the other links I found, however, that if I was on v5 (my 2nd array is) and this happened, the first thing to do would be restart the array.

 

Link to comment
  • 2 months later...

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.