All,

 

I recently had a drive failure and needed to rebuild it - but that's not really the issue here.  Put in a new drive, started the rebuild, and all was well, until the webGUI crashed.  So now i seemingly don't have a way to monitor the progress of the rebuild.  Judging by the drive activity on the server-front (lots of blinky lights!), and the fact that i can still access the files on the server, the server itself is still humming along just fine.

 

Is there an easy way to restart the webGUI without restarting the server (since i'm going to go ahead and assume that restarting the server during a data rebuild is a bad idea)?  I'm running version 5.0.4.

 

As an aside note - is there a compelling reason (other than having the latest and greatest) to upgrade my installation from 5.04 to 5.05?

Apparently, the webGUI can crash in 5.0.4. Perhaps it's fixed in 5.0.5.

So it would seem.  Since i can't reboot it to install 5.0.5 yet, any answer to my original question?

Is there an easy way to restart the webGUI without restarting the server (since i'm going to go ahead and assume that restarting the server during a data rebuild is a bad idea)?  I'm running version 5.0.4.

No - you cannot restart the Web GUI in v5 without restarting the server.

 

In your case if it looks like the rebuild is still in progress you should probably leave the system running.  You might want to be monitoring the syslog using a command like

tail -n 100 -f /var/log/syslog

from a console/telnet session.  This will show you if you are getting an errors reported that might indicate that the rebuild is having problems.

 

Possibly more important is why the web GUI might not be running.  The commonest problem is an Add-on consuming all the systems RAM and the emhttp process being (wrongly) killed by Linux.  Do you have any add-ons installed?

I had the Crashplan addon installed - i'm wondering if that was what was doing it.  I'll try removing it for the next reboot and see if stability improves.  In the meantime i'll keep an eye on the syslog until the rebuild is complete.

 

Thanks!

I had the Crashplan addon installed - i'm wondering if that was what was doing it.  I'll try removing it for the next reboot and see if stability improves.  In the meantime i'll keep an eye on the syslog until the rebuild is complete.

Although I do not use it myself I have heard that Crashplan is a memory hog! 

 

Not sure this will improve on v6 which as it is 64-bit it can use more than 4GB RAM on an unRAID system effectively.  I personally have found the Web GUI to be completely stable on v6 whereas I used to occasionally have problems on v5.  Also if running Crashplan via a Docker container on v6 (as some beta testers seem to be currently trialling) it should bring the Docker container down in the worst case and leave unRAID itself still running.