Ok, I found the issue. The Geo IP filter on the firewall was preventing accessing the remi repository, which was keeping me from updating php. Disabled the Geo IP filter and ran a fresh install and everything is working like a charm.
Thanks again guys for the help!
@Wayne-Workman Yes I am following https://wiki.fogproject.org/wiki/index.php?title=CentOS_7 for the install.
I am not sure on the exact version as I can’t get into the gui, I couldn’t find a way to check the version from cli. Is there a command to check the version of fog that is installed?
Trying to load the /fog/management page after completely fresh install of Centos 7 and Fog and getting a 500 error. Checking /var/log/httpd/error_log I am seeing the following:
[Mon Jan 30 15:41:32.771787 2017] [:error] [pid 21685] [client 172.16.1.153:51263] PHP Parse error: syntax error, unexpected ‘&’ in /var/www/html/fog/commons/init.php on line 105
[Mon Jan 30 15:42:18.075891 2017] [:error] [pid 21686] [client 172.16.1.153:51280] PHP Parse error: syntax error, unexpected ‘&’ in /var/www/html/fog/commons/init.php on line 105
[Mon Jan 30 15:44:11.434489 2017] [:error] [pid 21687] [client 172.16.1.153:51293] PHP Parse error: syntax error, unexpected ‘&’ in /var/www/html/fog/commons/init.php on line 105
[Mon Jan 30 15:44:50.246036 2017] [:error] [pid 21689] [client 172.16.1.153:51310] PHP Parse error: syntax error, unexpected ‘&’ in /var/www/html/fog/commons/init.php on line 105
[Mon Jan 30 15:45:28.739056 2017] [:error] [pid 21686] [client 172.16.1.9:54366] PHP Fatal error: Cannot create references to elements of a temporary array expression in /var/www/html/fog/maintenance/create_update_node.php on line 25
[Mon Jan 30 15:46:28.856688 2017] [:error] [pid 21687] [client 172.16.1.153:51322] PHP Parse error: syntax error, unexpected ‘&’ in /var/www/html/fog/commons/init.php on line 105
[Mon Jan 30 15:47:23.661965 2017] [:error] [pid 23957] [client 172.16.1.96:50435] PHP Parse error: syntax error, unexpected ‘&’ in /var/www/html/fog/commons/init.php on line 105
Now if I edit /var/www/html/fog/commons/init.php and remove the “&” in line 5 the management page then says I need php 5.5 and I am currently running php 5.4.16. I have fully updated centos when I check my php version it does show 5.4.16 installed, but yum update doesn’t show any packages to be updated. Any ideas, this is the third Fog server I have built and the only one that has given me any problems like this.
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.
I have also found that I can login to deploy an image (which I don’t have) and see image names I created. If I try to run a memtest though I get this error. Just trying provide as much info as possible on this.
Also running ipxe.pxe in debug this is what I am seeing.
Ok, I fixed my issue with UEFI pxe booting any have tried all of the .efi boot files, snp and ipxe both pxe boot and load the ipxe fog menu. But again when I select full registration it goes to load the bzimage and hangs at 0%.
@george1421 Ok, yeah sorry I edited my last reply but it loads then aborts when using the ipxe.pxe file. It does this for all ipxe.xxxx files and for the intel files. Yesterday I ran through all of the boot files trying to pxe boot and they either load and abort or load and hang at initializing devices.
@george1421 Ok, in legacy mode and using the boot file ipxe.pxe it loads the file but then reboots into windows. I grabbed a video of the boot proccess as it moves to quick after loading the boot file to snap a pic.
Ideally I would just want to pxe boot using legacy in the bios so that I don’t need to use the thumb drive. I have tried pxe booting with uefi turned on but it never receives a DHCP address. So legacy is preferred.
Correction pxe booting with ipxe.pxe is when this happens.
@Tom-Elliott I have tried the ipxe.pxe file while running the legacy boot option, but it seems to load but then just reboots into windows.
As for the UEFI USB booting I am using the ipxe.efi file pulled off of the FOG server. I followed the wiki for USB bootable media, I tried both the “easy way” and the “harder way” in the wiki. Both with the same result.
@george1421 When I am booting using option 67 on the DHCP server with the boot file undionly.kkpxe I have the laptop bios set to legacy so it is not using UEFI. So this is just the standard pxe boot process, it grabs the pxe file attempts to load but never loads the FOG ipxe menu. But when I am booting from the USB I have the bios set to UEFI and I am able to get the FOG ipxe menu. Sorry for any confusion but I hope that clears this up.
Now when I get the fog ipxe menu I have tired using two different USB to Ethernet dongles. One is a Asix AX88179 and the other is a D-Link DUB-E100. The D-link is a supported device and the Asix is not confirmed as working according to the wiki. But if I tried to run the registration with the D-Link connected it times out when trying to get the bzimage. The D-link also does not show any link like on the dongle when connected. When using the Asix it appears to connect but never downloads the bzimage.
I am completely fine testing and however much work it will take I am sure will be less than manually base configuring 100+ laptops.