Web UI 1.5.2
-
@wayne-workman Ok, well I’m not sure what happened I went to lunch and came back and it decided to work? I am at a loss. I am willing to do some tests if you have any ideas what was going on.
-
@hammett131 possibly a very large number of fog clients updated themselves after you updated your fog server - and now they are done.
-
@wayne-workman maybe but I don’t have many registered to it. Also it just dropped again. Even on the ubuntu server.
-
@hammett131 check
topagain. -
@wayne-workman Am I just looking for high usage?
-
@hammett131 Yes. High CPU or high memory usage. In top, you can sort by memory usage by pressing Shift + m
-
@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.
-
@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.
-
@wayne-workman Destination host unreachable.
-
@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
-
@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.
-
@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.
-
@wayne-workman Sounds good, Thanks I appreciate the help. Seems odd it randomly works then stops.
-
@hammett131 If you’re able to use the GUI at any point, you can go to
storage management -> node name -> enable graphand 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. -
@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.
-
@hammett131 If you’re unable to connect, try to restart apache to see if it allows you in.
systemctl restart apache2 -
@wayne-workman Nothing came up after I ran the restart.
-
@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.
-
@wayne-workman Will do
-
@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.
