Hostname changer
-
[code]5/27/2014 4:19 PM FOG::HostnameChanger Attempting to connect to fog server…
5/27/2014 4:19 PM FOG::HostnameChanger Module is disabled on this host.
5/27/2014 4:19 PM FOG::HostnameChanger Host name was not found in the database.[/code]These lines point at the fact the service was not enabled for the host. This means there’s nothing to find as there’s no work to perform.
While this is what is being reported, I’m also aware of a bug that has since been fixed in svn dealing with the service modules. If you want you can install svn of FOG and see if that helps at all.
-
Thanks for the quick response!
I did verify that it was enabled on the device and this is what made me confused as to why it wasn’t joining. My temporary solution was to delete the host out of FOG and then image it as if it were brand new to the system. I have found so far all brand new devices added to FOG are imaging then joining the domain with no issues.
I will do some more testing and report more specifics when I get more details. I plan to re-image some machines that are already in FOG and I want to see what happens with that.
Thanks for the help so far!!
-
did you verify that the hostnamechanger service is enabled in Host Management->Service Settings ?
-
I’d like to echo what GFm has said, and provide another little detail.
I am also seeing the issue where the hostname changer does not work until the service is restarted. I will image a machine, it’ll come up and just sit there. When I look at the log, I’m seeing the exact same errors:
5/27/2014 4:19 PM FOG::HostnameChanger Attempting to connect to fog server…
5/27/2014 4:19 PM FOG::HostnameChanger Module is disabled on this host.
5/27/2014 4:19 PM FOG::HostnameChanger Host name was not found in the database.However, I seem to have narrowed it down to a specific scenario: It only happens to me if the hostname has been changed in FOG. I’m testing on 3 machines and can reproduce this. Let’s say I have the machines named pc-1, pc-2, and pc-3. If I change pc-3’s name to be pc-10, I can re-image all 3 machines and the 3rd one will have the hostname changer problem. It requires me restarting the service to complete. I have verified that the hostnamechanger service is enabled.
Hope this helps…
-
Yes, hostnamechanger is enabled for my devices. I am testing a lot of stuff today and the rest of the week so I will provide more details as I narrow things down.
Thanks for all your input!
-
Has anyone else seen this issue or come across an answer? I’m still having to restart the fog service before it will change the hostname.
-
Do you have the new FOG service running? I’m still having issues and haven’t pinpointed a solution. You can try that?
I’ve noticed sometimes it automatically renames and joins the domain and sometimes I have to manually restart the computer or the service to get it to rename then join domain.
-
try setting the fog service to delayed start
-
GFm - yep, I downloaded the service installer right from the new version of FOG
Junkhacker - hmm, good suggestion. I will try that and get back to you.
-
Junkhacker - I will try that as well
Thanks
-
Update: Setting the service to delayed start works perfectly. Thanks for the idea!
-
the root of the problem likely has to do with the fact that hostname changer only checks once, on startup. if it does not have a valid network connection at that time, it will not see the server, and won’t change the name, and won’t try again.
-
I did a lot of testing today and found the problem… not a solution yet.
To give a brief background… I updated from 0.32 running ubuntu 10.04. I installed 14.04 and installed 1.0.1 -then migrated my fog install (i did this “clean” migration because when I just upgraded on the 10.04, some of my reports werent working -Pending macs, imaging logs, etc)
My devices change the hostname and join the domain perfectly with…
-newly added devices and delayed startup
-devices deleted out of fog and re-added doing the full host registrationIt does not work when…
-I have a device registered in fog before the migrationI have tried restarting the service/computer, but that didnt help. I get the same errors as I posted before with…
"
5/27/2014 4:19 PM FOG::HostnameChanger Attempting to connect to fog server…
5/27/2014 4:19 PM FOG::HostnameChanger Module is disabled on this host.
5/27/2014 4:19 PM FOG::HostnameChanger Host name was not found in the database.
"I have tried running a hardware inventory report on a machine that has been in fog before my migration… that did not help.
Any ideas? Anyone else seeing this with or without an upgrade to the new 1.0.1 from 0.32?
Thanks a lot!
-
Quickfix I would think would be to go to make a group of the hosts that were registered before your migration going into that group going to service settings uncheck everything save recheck everything safe
-
I will try that first thing tomorrow and let you know what happens.
Thanks!
-
I’m having the same issue after updating fog version from 0.32 to 1.0.1… I’ve already tried the Tom Elliott’s suggestion but unfortunately it didn’t work…
04/06/2014 17:02 FOG::HostnameChanger Module is disabled on this host.
04/06/2014 17:02 FOG::HostnameChanger Host name was not found in the database. -
Try this,
Place all hosts in your fog system into a single group, (ODD I KNOW)
Open a terminal window and ssh to your fog server.
Run:
[code]mysql -u root fog[/code]If you set a mysql root password run:
[code]mysql -u root -p fog[/code]It should ask for your root password.
Run the command:
[code]truncate table moduleStatusByHost;[/code]You can close the terminal.
Go back to your FOG Web GUI.
Go to Group Management.
List the group, or search for what ever you named the group.
Select your group.
Choose Service Settings.
Select the Services you want enabled.
Apply the changes.
-
That seemed to do the trick!
Thank you!
-
This post is deleted! -
I did a clean install of Ubuntu 13.10 with 1.1.0 and deployed our base image from 0.32 / uploaded to new 1.1.0 installation. Do I need to use an updated FOG Service msi before I sysprep or will the 0.32 image version work as is? The snapins seem to deploy fine - just doesn’t change name or join domain.
Thanks,
Andy
