Web UI 1.5.2

[Hammett131]

@wayne-workman Hm nothing looking to high, honestly highest for memory is firefox, but I see compiz time is 69 hours but the server has been shutdown recently.

[Wayne Workman]

@hammett131 You might have a duplicate IP problem. Try shutting down the fog server (if you can) - then try to ping it’s IP address, see if you get a response.

[Hammett131]

@wayne-workman Destination host unreachable.

[Wayne Workman]

@hammett131 Are there any errors in the apache error log from the time when the GUI is not accessible? On ubuntu that will be in /var/log/apache2/error.log

[Hammett131]

@wayne-workman I am seeing ALOT of a non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109 and 110.

[Wayne Workman]

@hammett131 I can give you an SQL statement that can disable the bandwidth charts for all storage nodes later tonight when I’m home - we can see if that helps. You can always re-enable it later.

[Hammett131]

@wayne-workman Sounds good, Thanks I appreciate the help. Seems odd it randomly works then stops.

[Wayne Workman]

@hammett131 If you’re able to use the GUI at any point, you can go to storage management -> node name -> enable graph and just uncheck that checkbox for graphs for all of your storage nodes to do the same thing the SQL will do. See if this helps.

[Hammett131]

@wayne-workman Unable to connect (currently), but I will keep checking back on it, I also don’t have any extra storage nodes not sure if that makes a difference or not.

[Wayne Workman]

@hammett131 If you’re unable to connect, try to restart apache to see if it allows you in. systemctl restart apache2

[Hammett131]

@wayne-workman Nothing came up after I ran the restart.

[Wayne Workman]

@hammett131 Yeah then I have no idea what’s causing the problem other than a suspicion that it’s related to the bandwidth chart. When you are able, disable the bandwidth graphs for your storage node when you can - see if this makes any difference.

[Hammett131]

@wayne-workman Will do

[Hammett131]

@wayne-workman Checked the error log after restarting apache2 and I see
command line: ‘/usr/sbin/apahce2’
AH00169: caught SIGTERM, shutting down
AH00163: Apache/2.4.33 (Ubuntu) OpenSSL.1,1,0h
Not sure if that’s helpful.

[Wayne Workman]

That’s normal stuff. sigterm is the signal to terminate. it’s how the kernel tells a process to stop without just outright killing it.

[Hammett131]

@wayne-workman I was able to use a checkpoint on the VM right after my 1.5.2 upgrade and it let me in this time and turned off the graph. It has been allowing me to use the web ui for about 2 hours now. Fingers crossed it continues to work. Thanks again.

[Hammett131]

Another update, coming back into work this morning by web ui is not working again. The graph thing seemed to help for a while but not a permanent solution.

[Hammett131]

Everything seems to work fine until I go to use it, the web interface works no issue but the moment I go to image a pc it fails to pxe then I can’t get back on the web ui giving me err_connection_timed_out.