Symptoms

After a OneFS upgrade or OneFS reboot, the web administration interface (WebUI) is not available. You receive an error 503, error 404, or even an error 400.

Cause

The services that provide the background and foreground process to produce the WebUI do not start properly.

Resolution

Run the following commands to shut down, and then restart the process.These lines disable all the services that supply the WebUI. isi services -a apache2 disable isi services -a isi_webui disable isi services -a isi_papi_d disable isi services -a isi_stats_d disable isi services -a isi_stats_hist_d disable Verify that the services have shut down prior to re-enabling them. ps auwx | grep httpd | grep -v grep isi_for_array ps auwx | grep webui | grep -v grep isi_for_array ps auwx | grep isi_papi_d | grep -v grep isi_for_array ps auwx | grep isi_stats_d | grep -v grep isi_for_array ps auwx | grep isi_stats_hist_d | grep -v grep When you attempt to start the WebUI on a node with an existing .pid file, the system interprets the existence of these files to mean that the WebUI is already running. Shutting down the processes and starting them back up again would not work if a .pid file is present on any of the nodes.Run the following commands to remove any .pid files that may be present that are preventing the webservice from starting. isi_for_array rm /usr/local/www/webkit/appserver.pid isi_for_array rm /var/apache2/run/httpd.pid isi_for_array rm /var/apache2/run/webui_httpd.pid Once you remove any existing .pid files that may be present, run the following commands to bring all the WebUI services back up. isi services -a apache2 enable isi services -a isi_webui enable isi services -a isi_papi_d enable isi services -a isi_stats_d enable isi services -a isi_stats_hist_d enable Test the WebUI interface and check to see if the issue is resolved. Note: OneFS 9.4 and later includes the ability to use the SmartConnect fully qualified domain name (FQDN) to the cluster's WebUI as sessions move between nodes.

Support Cases