I feel I need to add this, so people stumbling across the post understand.

The UNIQUE key for the hostMAC table is one key with two columns (hmMAC, hmHostID). Basically this means, a MAC cannot exist multiple times for the SAME host, but they can appear multiple times for different hosts. The idea is to allow the mac’s to show up with the hosts they reside in, but when it comes to identifying a host based on the MAC address, this becomes much more of a “no man’s land”.

This, we hope, will not be the case for much longer. One, MAC Addresses can be spoofed (and the same mac can exist on different machines even) so we’ve kind of lost the MAC Address as a unique identifier for a host. It probably doesn’t help that it’s not uncommon for a Laptop to have 2 or 3 MAC Addresses on it. Image an organization with only 1000 laptops. That’s potentially 2000 to 3000 MAC Addresses. Now I realize the unique identifier number is extremely high (each manufacturer has a potential of 16,777,215 addresses available) but as you see you can have the same mac address on multiple systems, it’s not very good for the hometeam.

It is uncommon to see the error itself, but when it has come up it’s usually because of a VM or TUNNEL adapter that is embedded as a part of the image. This, more or less, is where the pending filter comes in though.

While this field was, I think, only intended to filter any incoming “pending” mac addresses, it really should be applied to any mac address and it has been made to do exactly that.

OK, I fixed the Apache/HTTPD issue. After much, much, much searching I found this site for a fix and it worked for me.
http://awsadminz.com/httpd-service-main-process-exited-kill-cannot-find-process/
Should I post a separate tutorial as a fix for this issue?
As for the kernel thing, I tried a different PC and it is working fine. I guess I’ll have to figure that one out.

@88fingerslukee In the bios/uefi firmware settings, what is the boot order?

i.e and or also…

Is UEFI enabled and Legacy enabled, or just UEFI?
What pxe boot file are you using? I’ve seen that make a difference. I haves some cheaper HP’s that won’t boot with sanboot to the hard drive if you use ipxe.kkpxe, but they work fine with ipxe.pxe or ipxe.kpxe.

Also have you played with the refind boot settings? There’s a file on the fog server at
/var/www/fog/service/ipxe/refind.conf
there is a line that starts with scanfor I’ve changed mine to only look for internal,external which means it only looks for uefi options and not legacy options. On a few of my devices, if I have it set as uefi only it has a pause on the host every boot if UEFI CSM isn’t set and it searches for the bios options that are enabled in fog by default.

@Olduser Normally this is an FTP issue (as ftp is used to move the image from the /images/dev to /images folder).

Please run through:

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

I’m guessing your Antivirus installs a Filter Driver in your Network Adapter. If correct, uncheck it, save, and try again.

@Wayne-Workman
Thank you Wayne. I am agree with you. I will use now command line to manage mysql.
This will be the opportunity to improve my knowledge in sql 😉

Have a good day

@sudburr what you performed is correct, if you already had a prior config laid out. Sorry I didn’t recognize this sooner but a fix for this has been added to the next working branch.

Essentially the variable was being set properly, but it was being overwritten when the fog settings file was imported.

Good News Everyone!!!

I was able to get ipxe.efi to work, got a new USB to Ethernet adapter. The client was able to load and run the full registration without issue.

USB Ethernet adapter that works is HP P/N829834-001, it’s a USB 3.0 to Gigabit adapter. May want to add this to the confirmed working hardware list.

Thank you @george1421 for all the help was just about to load the bootable usb when the adapters arrived.

@Tom-Elliott
Work fine, thanks a lot!

@Wayne-Workman I can confirm this is now working - I just had to re-image the system and sysprep it again. It’s now uploading fine.
Thanks for the help and suggestions 🙂

If you’re running FOG 1.3.0 Release Candidate, you can protect images so that they are less likely to be accidentally deleted.

Also, 1.3.0 Release Candidate has a table in the database called history that you can look through to see what user deleted what image, or did what action. So at least they can be accountable for their actions.

@Tom-Elliott said in "Could not find a Storage Node in this group, is there one enabled?":

which would explain the “is one enabled” message.

This is a higher than normal brought up message on the forums recently. Perhaps not on bug-scale but it is higher than average. I’m hoping these issues go away with RC-27’s fixes whenever that is released.

I agree with Quazz about updating to the latest RC. Every new RC has fixes.

Linking in similar thread: https://forums.fogproject.org/topic/8944/centos-7-2-uuid-for-swap-wrong

@Wayne-Workman It had nothing to do with PHP. It had to do with the FOG Services not being properly picked up. PHP code had nothing to do with any of these problems. (Not saying there wasn’t a coding problem, just want people to more properly know what/where a problem is.)

The php not installing proper wasn’t something I’ve been able to replicate. But after this, a fresh install didn’t start the proper portions of the services which has been addressed.

Ok, thanks for letting us know. Marking this as solved then.

@Mokomoko I’m free today if you want help. IM me.

@Wayne-Workman
I think i cracked it, after you mentioned DB connection issues i checked everything using workbench and found fogstorage user had no schema privaleges at all ! Not sure how they would dissapear but after adding back in fog seems to be picking other storagenodes correctly.
Thank you for the help and guidance.
This can be marked as no bug but maybe helpful for others to check if they encounter issues.

@tseraj First, troubleshoot that it is the device and not the network. Hookup a dumb switch (unmanaged consumer grade switch) between your building’s network and this computer, and try again. If it succeeds, it’s your network. If it’s the same issue, it’s something with the device. If it’s something with the device, You may need to use the 10-second delay boot ROMs that Tom recently added. What is the filename that you have set in DHCP option 067/filename ? There’s a directory on the fog server, I think it’s /tftpboot/10secdelay or something similar. What you need to try is rename your currently in-use to blah.old and then move the 10secdelay version of that file to the /tftpboot directory so that it starts getting used, and then try again.

@Wayne-Workman

This issue is resolved. I built a new server as you and Tom suggested. Thanks for the help.