Hi,

FOG was working perfectly, however in the last couple of weeks at some point it has stopped assigning tasks to the master node in my storage group, they are all going to the other node in the group. Both nodes are configured identically in terms of config except the master node of course has the “Is Master Node” box checked - I tried to upload a screenshot but it isn’t letting me.
Both nodes have Max clients of 5 and are enabled, so I can’t see why it won’t assign tasks to the master node like it used to. If I disable the second node then it will assign tasks to the master no problem but stops once I enable the other node again. I’m lost at what else to try or even what caused it.

Any help would be greatly apprectiated!

Managed to sort this now. Ran the install again with -C and -K and then redeploying the client from the updated server

Thanks for your help

Hi,

Yes, all fresh hosts. we are running 1.5.8

Hi,

I have been rolling out the FOG Client to all our computers, and it has installed fine and the hosts show up on the server, however once I have approved them, they are all stuck on “Pending Registration created by FOG_CLIENT”

When looking at client log files this is what I am given:

--------------------------------Authentication--------------------------------

30/04/2020 13:57:27 Client-Info Version: 0.11.19
30/04/2020 13:57:27 Client-Info OS: Windows
30/04/2020 13:57:27 Middleware::Authentication Waiting for authentication timeout to pass
30/04/2020 13:59:27 Middleware::Communication Download: http://10.101.15.2/fog/management/other/ssl/srvpublic.crt
30/04/2020 13:59:27 Data::RSA FOG Server CA cert found
30/04/2020 13:59:27 Middleware::Authentication Cert OK
30/04/2020 13:59:27 Middleware::Communication POST URL: http://10.101.15.2/fog/management/index.php?sub=requestClientInfo&authorize&newService
30/04/2020 13:59:27 Middleware::Response Failed to decrypt data on server

I have tried reinstalling clients, removing them from the Fog host list and letting them rejoin and also a Kernel update. Could someone help me figure out what has gone wrong please?

Any help appreciated
Lewis

@Sebastian-Roth It’s just started working now, thank you for your support!

@Sebastian-Roth Hi, thank you for your help so far but no, we are now back to having the IP address tagged on the end now:

Interface not ready, waiting for it to come up: 10.101.15.2

If it helps both servers are running Ubuntu 18.04.4 and I have done the fix you gave to both servers as well as both have been restarted

Hi,

I have tried that, it gives me the same error just without the IP address on the end:

Interface not ready, waiting for it to come up:

Any other ideas?

@Sebastian-Roth I would be more than happy to give it a go, how do I get it?

@Sebastian-Roth That is the IP of the main server

Hi,

I am having the same issue, I have tried the fix mentioned by Florent about the Web Host setting but it hasn’t changed anything. Could anyone help me? It has only happened since the update. Both the main server and storage node have internet and local network access and can ping each other, but these errors are being shown in all the service logs on the storage node:

Interface not ready, waiting for it to come up: 10.101.15.2

I have tried rebuilding the storage server and nothing has changed, has anyone got any ideas?

Thanks a lot
Lewis