Web UI 1.5.2
-
@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. -
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.
-
@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.
-
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.
-
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.