Hostname changer not working



  • I’m running the lastest git build as of today maybe a half hour ago. I uninstalled the old client service from the client, removed the FOG certificate, downloaded the latest one from the server, and installed it, but I’m still having an issue with the hostname changer, as you can see in the fog.log


  • Developer

    @giejo63 said:

    When i try the URL with hostname.php it keeps trying but nothing happens

    You mean in a web browser?? Wow… this is… not as it should be I guess!

    What do you see in the apache error logs while you try to access this URL from a browser. Depending on your distribution those files might be in /var/log/apache2/ or some similar path on the FOG server.



  • @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é.
    

  • Senior Developer

    @Uncle-Frank Absolutely correct.


  • Developer

    Sure you haven’t changed this client’s “Service settings” meanwhile? ‘#!nh’ to me sounds like hostnamechanger is not enabled for this client in the web interface. But maybe I am wrong.



  • @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


  • Senior Developer

    @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.


  • Developer

    I am sorry but I don’t know the code of the new client much yet. So I am not sure how the client would handle this response. Usually ‘#!ih’ means ‘invalid host’. What about if you access the other URLs you see in the log, e.g. http://xxx.xxx.xxx.xxx/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=D4:3D:7E:D2:52:B4|&newService=1

    By the way. Which version of FOG du you use (see in the blue cloud in the webinterface).



  • @Uncle-Frank

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


  • Developer

    I meant that you could try to access this link http://xxx.xxx.xxx.xxx/fog/service/hostname.php?moduleid=hostnamechanger&mac=D4:3D:7E:D2:52:B4|&newService=1 (exchange xxx.xxx.xxx.xxx with the IP of your FOG server) in a normal browser from any host in your network which has access to the FOG server via HTTP (probably most if not all hosts will have access I guess). Then you should see something like ‘#!ok=<hostname> #AD=…’ in that browser window… or possibly an error. Give it a try!



  • @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…


  • Developer

    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=…’



  • @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
    ------------------------------------------------------------------------------
    
    


  • @Jbob Hi Jbob, yes this was indeed my issue and resolved by Tom Elliot. I had rebuilt my FOG server and so had a different CA key on the client which was imaged from the “old” FOG server before I rebuilt it.

    Tom advised issue as:

    The crt file that the client is using to send its authentication data is not signed by the server’s ca, or rather what your client thinks is the server’s certificate authority

    Fix was to download new crt file from http://your_FOG_server/fog/management/other/ca.cert.der and install that on the affected client.


  • Moderator

    @Jbob said:

    @Kiweegie @ch3i The “Reset encryption” button will only fix “Invalid security token” errors. What you have is an untrusted server. Did you reset the CA keys or swap out FOG servers recently?

    I think it’s a problem in my installation. @Tom-Elliott tried to help me via Teamviewer, but as he said : It’s weird ! lol


  • Senior Developer

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



  • 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


  • Senior Developer

    @Kiweegie @ch3i The “Reset encryption” button will only fix “Invalid security token” errors. What you have is an untrusted server. Did you reset the CA keys or swap out FOG servers recently?


  • Moderator

    @Kiweegie Same problem here !


Log in to reply
 

444
Online

39.3k
Users

11.0k
Topics

104.5k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.