FOG service invalid host
-
Hi,
In legacy versions of FOG, I used to just change the hostname in the Web UI - the FOG client would see that and change the hostname on the host and in AD, etc.Now when you change the hostname in the Web UI, it says “invalid host” on the fog.log on the local machine - yes, it is over wireless but all pending MACs have been approved, etc. - it even lists them in the log.
I can post the log in a few - I have also tried searching for answers on this but haven’t found anything concrete - is there a new method for changing the hostname? What am I missing?
Thank you FOG team and members for all of your hard work,
Dave -
Here is the fog.log - not much to it - you’ll notice the extra MAC addresses, so it is there as a host - all I did was change the hostname in the Web UI.
Thanks!
3/9/2022 11:15:54 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&configure&newService&json 3/9/2022 11:15:54 AM Middleware::Response Success 3/9/2022 11:15:54 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&mac=00:09:0F:AA:00:01|64:6E:E0:53:15:39|66:6E:E0:53:15:38|00:09:0F:FE:00:01|64:6E:E0:53:15:38&newService&json 3/9/2022 11:15:54 AM Middleware::Response Invalid host 3/9/2022 11:15:54 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?clientver&newService&json 3/9/2022 11:15:54 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?newService&json 3/9/2022 11:15:54 AM Service Creating user agent cache 3/9/2022 11:15:54 AM Middleware::Response Module is disabled on the host 3/9/2022 11:15:54 AM Middleware::Response Module is disabled on the host 3/9/2022 11:15:54 AM Middleware::Response Module is disabled globally on the FOG server ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 3/9/2022 11:15:54 AM Client-Info Client Version: 0.12.0 3/9/2022 11:15:54 AM Client-Info Client OS: Windows 3/9/2022 11:15:54 AM Client-Info Server Version: 1.5.9 3/9/2022 11:15:54 AM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 3/9/2022 11:15:54 AM Client-Info Client Version: 0.12.0 3/9/2022 11:15:54 AM Client-Info Client OS: Windows 3/9/2022 11:15:54 AM Client-Info Server Version: 1.5.9 3/9/2022 11:15:54 AM Middleware::Response Module is disabled on the host ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 3/9/2022 11:15:54 AM Client-Info Client Version: 0.12.0 3/9/2022 11:15:54 AM Client-Info Client OS: Windows 3/9/2022 11:15:54 AM Client-Info Server Version: 1.5.9 3/9/2022 11:15:54 AM Middleware::Response Module is disabled on the host ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 3/9/2022 11:15:54 AM Client-Info Client Version: 0.12.0 3/9/2022 11:15:54 AM Client-Info Client OS: Windows 3/9/2022 11:15:54 AM Client-Info Server Version: 1.5.9 3/9/2022 11:15:54 AM Middleware::Response Module is disabled on the host ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PrinterManager-------------------------------- ------------------------------------------------------------------------------ 3/9/2022 11:15:54 AM Client-Info Client Version: 0.12.0 3/9/2022 11:15:54 AM Client-Info Client OS: Windows 3/9/2022 11:15:54 AM Client-Info Server Version: 1.5.9 3/9/2022 11:15:54 AM Middleware::Response Module is disabled on the host ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PowerManagement------------------------------- ------------------------------------------------------------------------------ 3/9/2022 11:15:54 AM Client-Info Client Version: 0.12.0 3/9/2022 11:15:54 AM Client-Info Client OS: Windows 3/9/2022 11:15:54 AM Client-Info Server Version: 1.5.9 3/9/2022 11:15:54 AM Middleware::Response Module is disabled on the host ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------UserTracker--------------------------------- ------------------------------------------------------------------------------ 3/9/2022 11:15:54 AM Client-Info Client Version: 0.12.0 3/9/2022 11:15:54 AM Client-Info Client OS: Windows 3/9/2022 11:15:54 AM Client-Info Server Version: 1.5.9 3/9/2022 11:15:54 AM Middleware::Response Module is disabled on the host ------------------------------------------------------------------------------ 3/9/2022 11:15:54 AM Service Sleeping for 139 seconds -
@dpullin verify that all the macs are registered on the same host,
-
@eduardotseoane thanks for the reply
All MACs are there, see the result from ipconfig - it lists the 1 needed MAC (wireless) in ipconfig, the fog log (see previous post), and the fog web UI (see screenshot)
This is confounding, are there any other ideas or reasons that this could happen?
Connection-specific DNS Suffix . : **********.org Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz Physical Address. . . . . . . . . : 64-6E-E0-53-15-38 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::4d08:6ac:3da5:33e1%8(Preferred) IPv4 Address. . . . . . . . . . . : 172.21.161.147(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.252.0 Lease Obtained. . . . . . . . . . : Wednesday, March 9, 2022 12:16:58 PM Lease Expires . . . . . . . . . . : Sunday, March 20, 2022 8:12:22 AM Default Gateway . . . . . . . . . : 172.21.160.1 DHCP Server . . . . . . . . . . . : 172.21.240.241 DHCPv6 IAID . . . . . . . . . . . : 140799712 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-B1-89-82-38-14-28-B7-4A-15 DNS Servers . . . . . . . . . . . : 172.21.240.237 172.21.240.241 NetBIOS over Tcpip. . . . . . . . : Enabled
-
See the fog log for today - the needed MAC address is there (wireless) 64:6E:E0:53:15:38 - it does try to use the old hostname if you’ll notice, which has been changed on the fog server - I am just trying to get it to update in a test environment, but no dice
Thanks for any help
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 3/15/2022 8:28:52 AM Client-Info Version: 0.12.0 3/15/2022 8:28:52 AM Client-Info OS: Windows 3/15/2022 8:28:52 AM Middleware::Authentication Waiting for authentication timeout to pass 3/15/2022 8:28:52 AM Middleware::Communication Download: http://fogserver/fog/management/other/ssl/srvpublic.crt 3/15/2022 8:28:52 AM Data::RSA FOG Server CA cert found 3/15/2022 8:28:52 AM Middleware::Authentication Cert OK 3/15/2022 8:28:52 AM Middleware::Communication POST URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&authorize&newService 3/15/2022 8:28:52 AM Middleware::Response Invalid host 3/15/2022 8:28:52 AM Middleware::Communication URL: http://fogserver/fog/service/register.php?hostname=9520-Test-2&mac=00:09:0F:AA:00:01|64:6E:E0:53:15:39|66:6E:E0:53:15:38|00:09:0F:FE:00:01|64:6E:E0:53:15:38&newService&json``` -
@dpullin said in FOG service invalid host:
Now when you change the hostname in the Web UI, it says “invalid host” on the fog.log on the local machine
Are you sure the fog-client communication works perfectly fine before you do this?
Quite often this happens due to a duplicated MAC address: https://forums.fogproject.org/topic/15292/fog-client-authentication-after-cloning-windows
Please check the apache and PHP-FPM logs as well to make sure there is no error happening that might be causing this.
-
Yes, I am positive the fog-client communication works fine before doing this - we have done many tasks including printers and MSI, etc. - and in our environment the fog service also sets the initial name of the machine from Desktop-****** (random name from the sysprep run) - the fog service sets it to what we actually want it to be - and that all works great.
The issue seems to be when the name in FOG UI doesn’t match the hostname of the machine (because I changed it in the UI after the fact) - this has started to crop up on other machines due to user error (techs giving machines the wrong names before sending them out the door) - then we try to fix it by changing the name in the UI, then it gives the “invalid host” error as described above. The only way to fix this seems to be removing the machine from fog completely (and usually also AD for good measure) and totally re-registering which is a huge hassle.
It seems like this is a bug in the fog service, or fog application, etc. - because, as I have shown above, the MAC addresses match and everything works fine, as long as you don’t change the name in the fog web UI, then it breaks the connection between the host and fog server - the weird thing is, in previous versions of fog this used to work great, but I guess not now. Anyway thanks.
-
@dpullin Thanks for your update. I will look into this when I have a bit more time. Stay tuned.
-
@sebastian-roth Great thank you! I really appreciate it - there is a workaround, delete and re-register, so I guess that it is not urgent, but it would still be nice to know what is happening, etc.
If I can provide logs I will, but I would need specific instructions,
Thanks! -
@dpullin said in FOG service invalid host:
The issue seems to be when the name in FOG UI doesn’t match the hostname of the machine (because I changed it in the UI after the fact) - this has started to crop up on other machines due to user error (techs giving machines the wrong names before sending them out the door) - then we try to fix it by changing the name in the UI, then it gives the “invalid host” error as described above.
I can’t seem to replicate the issue as described using the following steps - please verify if you do things a different way:
- Check fog.log to see communication works fine
- Make sure AD credentials are set and correct for the test host in the FOG web UI
- Change Host Name in FOG web UI
- Wait for machine to reboot
- Check hostname (Windows GUI as well as CMD ->
hostname) and fog.log (see below).
------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 4/16/2022 7:06:09 AM Client-Info Client Version: 0.12.0 4/16/2022 7:06:09 AM Client-Info Client OS: Windows 4/16/2022 7:06:09 AM Client-Info Server Version: 1.5.9.139 4/16/2022 7:06:09 AM Middleware::Response Success 4/16/2022 7:06:09 AM HostnameChanger Checking Hostname 4/16/2022 7:06:09 AM HostnameChanger Renaming host to Newhostname 4/16/2022 7:06:09 AM HostnameChanger Renaming host inside existing domain binding 4/16/2022 7:06:09 AM HostnameChanger Success, code = 0 4/16/2022 7:06:09 AM Power Creating shutdown command in 60 seconds 4/16/2022 7:06:09 AM Bus Emmiting message on channel: Power ------------------------------------------------------------------------------Works fine in my test setup. Do you use plugins or other special things in your FOG setup? Other than that I con only imagine is has to do with the wireless MAC you seem to be using. Is this the primary MAC?
