@Tom-Elliott

Ok was my fault… for this host the hostname changer was disabled.
I activate it in service settings but it doesn’t work.
When i try the URL with hostname.php it keeps trying but nothing happens (so it explain the success for servicemodule-active.php and the error for hostname.php in this log)

22/09/2015 15:18 Client-Info Version: 0.9.5
 22/09/2015 15:18 HostnameChanger Running...
 22/09/2015 15:18 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=D4:3D:7E:D2:52:B4|&newService=1
 22/09/2015 15:18 Middleware::Communication Response: Success
 22/09/2015 15:18 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/hostname.php?moduleid=hostnamechanger&mac=D4:3D:7E:D2:52:B4|&newService=1
 22/09/2015 15:20 Middleware::Communication ERROR: Could not contact FOG server
 22/09/2015 15:20 Middleware::Communication ERROR: Le délai d'attente de l'opération a expiré.

@Tom-Elliott said:

@Uncle-Frank my guess as to why he is seeing ih which is invalid host, is the MAC address being sent is the wifi while the Mac registered to the host is wired. This is just a guess.

This host as only wired LAN it’s not a laptop so i think it’s not a MAC address problem

@Uncle-Frank

when i try the other URL i have : “#!nh”

I’m in version 4682

@Uncle-Frank

when i try in a browser, i see “#!ih”

@Uncle-Frank said:

Pretty weird! Is xxx.xxx.xxx.xxx always the exact same IP address? Please make sure!

Why would one HTTP GET request work and another one the same minute not? Maybe just try this link in your webbrowser and see what response you get. Usually it should be like: ‘#!ok=<hostname> #AD=…’

Hi,
xxx.xxx.xxx.xxx is always the same IP address. I’m sure.
I have never seen ‘#!ok=<hostname> #AD=…’
I dont know why…

@Jbob said:

@giejo63 Can you upload the fog.log anyways? I can’t help unless I know exactly what is or isn’t happening.

Hi,
Here is my fog.log. I dont know why there is a communication error only for Hostname changer ??

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 22/09/2015 15:18 Client-Info Version: 0.9.5
 22/09/2015 15:18 HostnameChanger Running...
 22/09/2015 15:18 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=D4:3D:7E:D2:52:B4|&newService=1
 22/09/2015 15:18 Middleware::Communication Response: Success
 22/09/2015 15:18 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/hostname.php?moduleid=hostnamechanger&mac=D4:3D:7E:D2:52:B4|&newService=1
 22/09/2015 15:20 Middleware::Communication ERROR: Could not contact FOG server
 22/09/2015 15:20 Middleware::Communication ERROR: Le délai d'attente de l'opération a expiré.
------------------------------------------------------------------------------


------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 22/09/2015 21:02 Client-Info Version: 0.9.5
 22/09/2015 21:02 SnapinClient Running...
 22/09/2015 21:02 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/servicemodule-active.php?moduleid=snapinclient&mac=D4:3D:7E:D2:51:69||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 22/09/2015 21:02 Middleware::Communication Response: Success
 22/09/2015 21:02 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/snapins.checkin.php?mac=D4:3D:7E:D2:51:69||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 22/09/2015 21:02 Middleware::Communication Response: No snapins
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 22/09/2015 21:02 Client-Info Version: 0.9.5
 22/09/2015 21:02 PrinterManager Running...
 22/09/2015 21:02 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/servicemodule-active.php?moduleid=printermanager&mac=D4:3D:7E:D2:51:69||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 22/09/2015 21:02 Middleware::Communication Response: Success
 22/09/2015 21:02 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/Printers.php?mac=D4:3D:7E:D2:51:69||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 22/09/2015 21:02 Middleware::Communication Response: No Printers
 22/09/2015 21:02 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/printerlisting.php?newService=1
 22/09/2015 21:02 Middleware::Communication Response: No Printers
------------------------------------------------------------------------------

same problem for me but i have no error about a certificate or authenticate
client are using new fog client 0.9.5 but hostname changer didnt work
I see no error in fog.log

@Tom-Elliott said:

Can you try reupdating your kernels/ and/or re-running the install if you’re running dev version? I’ve updated the kernels to simply remove the qmi_wwan drivers from the mix. From my reading this should essentially keep the GOBI card from loading with the FOG inits.

Hi
same problem for me
using the kernel 4.2.0 of September 14, 2015 doesnt change
When i’m doing a quick registration and inventory (or quick image) it loops on starting wwan0 interface
Any ideas ?

@giejo63 said:

Any news on this problem ?
i have the last GIT version of Fog and seems to have the same problem (on different machine)
It was working great with version 1.2.0
Thanks in advance

I have tested with the init.xz, init_32.xz, bzimage and bzimage32 from Fog_1.2.0 and this error disappeared (putting them in ipxe directory)
but now my problem is that it didnt deploy at all, seems like computers are looping infinitely

Any news on this problem ?
i have the last GIT version of Fog and seems to have the same problem (on different machine)
It was working great with version 1.2.0
Thanks in advance