Gui not responsive
-
@UWPVIOLATOR said in Gui not responsive:
---------------------------------ClientUpdater--------------------------------
9/14/2016 3:27 PM Client-Info Client Version: 0.11.2
9/14/2016 3:27 PM Client-Info Client OS: Windows
9/14/2016 3:27 PM Client-Info Server Version:
9/14/2016 3:27 PM Middleware::Response Success
9/14/2016 3:27 PM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe
9/14/2016 3:27 PM Data::RSA FOG Project cert found
9/14/2016 3:27 PM Data::RSA ERROR: Certificate validation failed
9/14/2016 3:27 PM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (NotTimeValid)
9/14/2016 3:27 PM ClientUpdater ERROR: Update file is not authentic@Tom-Elliott this is exactly what is being seen here, I believe these two threads are suffering from the same thing.
-
@UWPVIOLATOR Crosslinking similar threads:
https://forums.fogproject.org/topic/8561/rc10-broken-items-on-upgrade/82 -
@Tom-Elliott said in Gui not responsive:
So that particular system is off time a bit. But why?
I don’t think it is. He posted the log 2 hours ago. 2 hours ago was 3:30, and the log says about 3:30. There’s something going on with the installer. I’m going to test client updating myself and see if I have the issue.
-
@Tom-Elliott said in Gui not responsive:
@ablohowiak a bit out of norm but can you change the config.class.php filr to use 127.0.01? I suspect the sockets are dropping to make room for other sockets, causing some portions to just drop php code. So because the socket is lost mid stream it causes the GUI to crash. Again this is all theoretical but it files like an issue I’ve seen before, which was why I switched from a socket connection to a TCP connection
So changing the client communication to 900 sec didn’t improve the gui performance, nor did disabling the client auto updater. Do you still suggest changing the config.class.php, and if so are there particular line or every instance of the server IP address?
Thanks. -
Auto update client is found in fog configuration font settings please disable app if it’s not already done stop web services for probably 5 minutes or so and all your clients should stop trying to download any file because there will be nothing to download then start web services do you still see the clients trying to update
-
@Tom-Elliott
Now with the client communication set to 900 and finding the second client update checkbox things are behaving better.
-
We were having this issue to. However, I haven’t had the time to dive into why the clients were failing to updated. But Wayne stated that the clients kept downloading from the server, which with a couple thousand hosts, this was flooding the pipe, and basically making the GUI unusable because the NIC was pegged. Once I unchecked those boxes things have been great. Maybe one day I will get that magical thing called time to dive into it with someone.
-
Cross-linking similar threads, and to give this thread a bump.
https://forums.fogproject.org/topic/8636/fog-client-is-not-updating
https://forums.fogproject.org/topic/8561/rc10-broken-items-on-upgrade
https://forums.fogproject.org/topic/8556/gui-not-responsive
https://forums.fogproject.org/topic/8616/updating-fog-client -
The issue with client updating has been found and a patch is being worked on. The patch will not require any additional work to be done on your side, just a simple server update once ready.
-
-
@Joe-Schmitt
RC11 has started out well. I did need to rerun the install and reboot the system before the client updater started working. The GUI remains responsive even after all the clients start up in the morning. After a few days I may try shortening the client communication period from 900 so the snapins run more timely.
