Topics created by zaccx32

@zaccx32 said in All hosts deleted/not showing in host list/groups:

After cleaning that up, a few hosts showed up but most are still missing and our images are not showing up in the GUI either.

While disk space is an important thing and 99% seems a lot in first sight, I don’t think this was causing the issue here. Why? Because we see you have a large disk with still 31 GB shown as free. I find it very strange that you see some hosts now. From the SHOW DATABASES; output you posted I would have guessed the fog DB is fully corrupted now and needs recovery (keeping my fingers crossed it’s still possible).

Also, when trying to access the fog DB today, is cannot be found any more, almost like it is gone.

Now we really need to figure out what’s going wrong with the DB. First of all let us take a look a the DB files on disk, the real basis: ls -al /var/lib/mysql (post a picture here)

As well stop the DB and take a file backup. Then start it up again and check the log:

service mysqld stop cd /root mkdir backup rsync -av /var/lib/mysql backup service mysqld start tail -n 30 /var/log/my*

Post a picture of the output from the last command as well. I really hope I got all the commands right for your pretty dated CentOS 6.9 install.

@zaccx32 Find the database information in /var/www/html/fog/lib/fog/config.class.php - with FOG 1.5.9 the database user is called fogmaster instead of root that was used in earlier versions. So to login you run this command on the console:

mysql -u fogmaster -p ...

@Sebastian-Roth
Hello, Sebastian,
I believe the reason for why hostnames were not updating was due to the client not being up to date, however, after a name change, AD is still not updating, causing a trust relationship error when logging in and the domain does not change. Also, we a running 0.12.0 client version. Any other ideas on why AD is not communicating correctly? Thanks!

@zaccx32 said in Pxe-Boot gets hung up on TFTP:

I did find a way to identify which machines are being affected by looking for extremely slow copy speeds when deploying files with PDQ. 4MB files will take over an hour to copy on machines that are being affected.

This here kind of tells me its network infrastructure. What I would do is look at the network switch port (hopefully you have a managed switch) and look at the port counters. See if you are having a lot of crc errors. Can you generalize and say all computers from area A have a problem but not from area B. If this is the case then the troubles may be on an uplink port between the area A switch and the next switch in line. Again the port counters might give you a clue to what is not right. IMO if you can duplicate the error with 2 different servers then its probably not the FOG server at fault.

I did notice something in your dhcp screen shot. Its not a problem with fog, but in your polycom scope, you should probably remove the undionly.kpxe boot file name. Its not relevant to a voip phone and may cause problems.

The other thing since your dhcp server supports profiles you might want to take a look at this wiki page to setup profiles for both bios and uefi booting: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy