RC37 + Client 011.7 = Response Invalid Host

[sudburr]

Server

• FOG Version: RC37
• OS: CentOS 7.2.1511

Client

• Service Version: 0.11.7
• OS: Windows 7(32)

Description

Installed FOG client for first time on a system via scheduled task:

msiexec.exe /i FOGService.msi /quiet USETRAY="0" WEBADDRESS="devfog"

Reboot, then Fog.log says:

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 20/12/2016 6:00 PM Client-Info Version: 0.11.7
 20/12/2016 6:00 PM Client-Info OS:      Windows
 20/12/2016 6:00 PM Middleware::Authentication Waiting for authentication timeout to pass
 20/12/2016 6:00 PM Middleware::Communication Download: http://devfog/fog/management/other/ssl/srvpublic.crt
 20/12/2016 6:00 PM Data::RSA FOG Server CA cert found
 20/12/2016 6:00 PM Middleware::Authentication Cert OK
 20/12/2016 6:00 PM Middleware::Authentication ERROR: Could not get security token
 20/12/2016 6:00 PM Middleware::Authentication ERROR: Could not find file 'C:\Program Files\FOG\token.dat'.
 20/12/2016 6:00 PM Middleware::Communication POST URL: http://devfog/fog/management/index.php?sub=requestClientInfo&authorize&newService
 20/12/2016 6:00 PM Middleware::Response Invalid host
 20/12/2016 6:00 PM Middleware::Communication URL: http://devfog/fog/service/register.php?hostname=rjs201612201615&mac=6C:F0:49:25:FF:3B||00:00:00:00:00:00:00:E0&newService&json

There is no token.dat … or spoon.

[Tom Elliott]

I’m just guessing but is the host this client was installed on registered?

After seeing this message, is it displaying in Pending Hosts?

[Tom Elliott]

Just a bit more info:

The “Could not get security token” and “Could not find file” are normal after the client has been freshly installed (as the token is not found and the file doesn’t exist until the first cycle.)

[Wayne Workman]

I’d suggest just for troubleshooting purposes try to uninstall and reinstall the client manually on that one machine and monitor the results. Also - a reboot isn’t necessary but just simplifies things. After installing clean for the 1st time, you can just start the FOGService and it’ll start working.

[Tom Elliott]

And a little more info:

When the client sends the self registration the, Invalid Host, message is how it knows to do this. Hopefully this helps clarify that, from the messages in the log, to the urls it’s sending, are showing there currently is no bug. The system is doing exactly what it’s supposed to be doing.

Of course, confirmation of the fact that the host registered itself and is now in “pending hosts” would be even further showing that this is indeed working properly.

[Wayne Workman]

Yeah, re-reading over this, Tom is right. The system is probably sitting in the pending list right now waiting to be approved.

[sudburr]

The server itself had no hosts; it’s my development server so I regularly blast it; and it was indeed waiting in Pending Hosts.

Thank you for clarifying what to expect .