I found it.

The setting was called “QUICKREG PENDING MAC FILTER”

I took the USB NIC MAC out of there and everything worked again.

@yas1 George is right, FOG is doing DNS queries mostly as part of a routine check to see if hosts are up. If you don’t like this you can disable the whole service in the web UI (FOG Configuration -> FOG Settings -> FOG Linux Service Enabled -> PINGHOSTGLOBALENABLED) or increase the service sleep/inactive time (FOG Configuration -> FOG Settings -> FOG Linux Service Sleep Times -> PINGHOSTSLEEPTIME) or you can take the big hammer and just disable the whole Linux service (systemctl stop FOGPingHosts ; systemctl disable FOGPingHosts).

I think that’s why every device in the database is shown as offline(“unknown”).

While this is related it’s not the fact that FOG cannot resolve it’s name but that it cannot connect to port 445 on your host(s). The word “ping” might be a bit misleading here, it’s not a standard ICMP ping we are doing but a kind of Windows specific check to see if TCP port 445 is available. Both checks definitely have drawbacks but some years ago the FOG devs decided to go the port 445 way and this is still the case today.

If you got hooked up by the idea to use the host status more there is also a plugin you can enable called “host status”.

that worked, I added the other lines from that section also.

Thanks, Moe. make as solved please

use-host-decl-names on; ddns-update-style interim; ignore client-updates; next-server 10.10.2.58; authoritative;

Make as solved please, I can image. Thank you for the help.

@Sebastian-Roth

I rebuilt the system. Everything is good to go at this time.

This is exactly what I was looking for. Added the LDAP plugin, then added the ldap php module and modified to the php config. I now have it working. This helped greatly thank you!

@Sebastian-Roth Yes this fixed the issue…

@Sebastian-Roth said in Inventory Report 1.5.7:

@Raymond-Bell As the person in the other topic has not replied yet I would ask you to test the first fixes I mentioned there. Would be great to get some feedback if the new search pattern thing is working in the wild (on your system).

@tomatzo It’s great you try to fight your way through it and seem to get a lot of things fixed yourself. But feel free to post here when you hit an error with 1.5.7 and we surely be able to help you out.

Best if you can upload the FOG installer error logs that you find in the subdirectory from which you run the installer, usually something like .../forproject/bin/error_logs/. That will make it way easier for us to see what went wrong and how to help you.

@CoxM Before we actually dive into the pending MAC stuff I want to take one step back and see if what you describe is really caused by pending MACs at all.

First, can you reproduce the issue?`Please take a screenshot of the host settings of the two systems running into the problem where we see the MACs and post here.

@tlehrian It’s usually good to open new topics on different issues. People will find answers more easily and hopefully be able to help themselves using the forum search. We’ll discuss this other topic here as well but I just want to encourage you to open as many topics as you have issues. There is no limit.

I’m running into another error that Restoring GPT Partition Tables failed (see pic).

We were able to track down an issue that sounds very similar last week. Find the details here: https://forums.fogproject.org/topic/13440/fog-1-5-6-auto-resize-is-unpredictable

To try the fixed binaries download 64 Bit and 32 Bit and put those in /var/www/html/fog/service/ipxe/ dir on your FOG server. Probably good to rename the original ones instead of overwriting.

Ok, back to the initial multicast topic: The log you posted seems fine from my point of view. There is no message saying "This is not the master node.” as you mentioned before.

If you seem to have problems with multicasting I’d advise you to try and not spawn new sessions before you made sure the old one is completely terminated. Take a look at the logs as well as run ps ax | grep 'udp-sender' (make sure you use single quotes here!) to see if some left overs are still running. If so you want to terminate those processes (killall udp-sender).

Edit: Just had another thought on the “This is not the Master Node” message: Please read this: https://github.com/FOGProject/fogproject/issues/268

@IHCRCDan said in Attempting to check in failed : No Open Slots, There are 0 Before Me:

What I can’t figure out is how to remove the stuck queued and active tasks that are no longer valid.

First check the task view lists in the web UI. Do you still see them there?

If not you might try the database maintenance: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands

@azra What kind of hardware is this?? We see two disks in the output, same model, same size. Is this a RAID setup? Most probably a RAID 0 setup where two 500 GB disks are used to build a whole 1 TB disk chunk.

Interesting things in the picture:

Message ... invalid ...?! Do you remember what the full message was? File system column is empty which means Linux is not able to detect the filesystem used within that partition. My guess is this is caused by the RAID setup. Possibly this is some kind of fancy software RAID controller where that adds a layer which Linux is not able to decrypt and therefore FOG is only able to capture it raw. Small partition seems to be at the beginning of the disk as Linux sees it Big partition is at the end and is full 1000 GB - different to what we saw in the Windows disk management screenshot No partitions in second disk -> pretty sure this is a RAID 0 setup with the partition table only being populated on the first disk

Would have been good if you’d told us this is not a normal 1 TB disk way earlier.

I am wondering if you ever deployed the image to another machine successfully?!

hey folks,
the thread is old, but we had also a fight with all the certificates.
after installation of fog 1.5.6 all the clients we imaged bevor stopped communicating with this fog server, they had certificate issues.
we created a gpo that deletes all the installed fog certificates with 3 powershell commands:
Get-Childitem Cert:LocalMachine\root | where-object Thumbprint -eq “4737f594b54cb9fe1103e3c325d9c6963e57c911” | remove-item -force

Get-Childitem Cert:LocalMachine\root | where-object Thumbprint -eq “c84f54d1f654e2f9f04d3c2bf99b3a36371856d4” | remove-item -force

Get-Childitem Cert:LocalMachine\root | where-object Thumbprint -eq “CBE3E738F63C3B1BB93A296F70E73E527D12C637” | remove-item -force

then it worked…

@bogle SSL enabled this time or not? Where did you put the certificates?

@frankv24 said in tftp server issue:

we found a NETGEAR wireless router connected in student lab

Ah you found a rogue dhcp server hiding on your network. Well done. I know its very difficult to find these devices and keep them off your network.

@Ray_RDS You can download them with your windows computer. Then you will need to use WinSCP if you are command line challenged or pscp (from putty) to copy the files to the FOG server placing them in the directories provided by Sebastian. The next thing you will need to do is update your dhcp server option 67 to request the new file name.

@george1421 said in Mounting failed, connection refused:

@faresalandlos Well at this point I don’t think its a firewall issue, but to answer your question for ubuntu this is the command to disable the firewall sudo ufw disable

So what do I think:

You need to understand why nfs is not starting on that system. your exports are right and once nfs is running the when you run the showmount command you should see what is posted in the /etc/exports file. The exports file is configured correctly. Your /images/dev directory is not complete. You are missing the post init scripts directory.
Your directory should look like this: [root@sonic ~]# ls -la /images/dev total 428 drwxrwxrwx 5 fog fog 4096 Jun 24 13:11 . drwxrwxrwx 18 fog root 4096 May 28 11:11 .. -rwxrwxrwx 1 fog fog 0 Mar 16 2016 .mntcheck drwxrwxrwx 2 fog root 4096 Oct 4 2018 postinitscripts

You may need to just rerun the fog installer and it should fix this file path.

For your nfs service there are a number of sub services like portmapper and such that nfs depends on. Does running sudo systemctl status nfs.service give you any clue to why nfs is not starting?

thank you so much for all the help turning off the firewall fixed the problem! it’s like the system was not happy that i used FTP to play with the folders

@Sebastian-Roth Actually, on the latest VirtualBox it seems that there is a way to UEFI PXE boot now. (chipset ICH9 and network adapter type to virtio-net), but I haven’t really tested it any significant amount. It gets to the FOG menu at any rate.

@thebrennan47 why don’t you explain more how you fixed it?

@Quazz said in Corrupt file in image?:

then it could also potentially be something far more silly such as a faulty ethernet cable.

Or faulty RAM in the client machine.