Last part of the puzzle was that the php-fpm service wasn’t running.
Started it with:

sudo systemctl start php-fpm.service
sudo systemctl enable php-fpm.service
systemctl status php-fpm.service

And now the FOG Web UI is working for me again.

OK, apparently that’s all I needed to figure the rest out on my own.

The ?? operator that the error message seemed to be complaining about was apparently introduced in PHP 7. My old CentOS 7.5 server (Eww, I know ) only had PHP 5.6. (Suggesting the install script check the PHP version to make sure it’s at least 7)
I was able to update PHP with the following commands:

sudo yum remove php*
sudo yum install php php-bcmath php-cli php-common php-fpm php-gd php-ldap php-mbstring php-mcrypt php-mysqlnd php-pdo php-pecl-jsonc php-pecl-zip php-process

Doing so replaced the blank white web UI with a message that stated:
“Service Unavailable - The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.”

I then re-ran the sudo ./installfog.sh, and it ran without any problems. The DB schema update step functioned, and I could then login like normal.

However, I don’t think I’m fully out of the woods yet. The install script for some reason messes up the NIS login system, requiring a reboot to make work again, but after the reboot the FOG Web UI is back to showing “Service Unavailable”. I’m suspecting a user permission problem that I need to dig into next (Maybe I should make this a new topic if I need help).

Last part of the puzzle was that the php-fpm service wasn’t running.
Started it with:

sudo systemctl start php-fpm.service
sudo systemctl enable php-fpm.service
systemctl status php-fpm.service

And now the FOG Web UI is working for me again.

OK, apparently that’s all I needed to figure the rest out on my own.

The ?? operator that the error message seemed to be complaining about was apparently introduced in PHP 7. My old CentOS 7.5 server (Eww, I know ) only had PHP 5.6. (Suggesting the install script check the PHP version to make sure it’s at least 7)
I was able to update PHP with the following commands:

sudo yum remove php*
sudo yum install php php-bcmath php-cli php-common php-fpm php-gd php-ldap php-mbstring php-mcrypt php-mysqlnd php-pdo php-pecl-jsonc php-pecl-zip php-process

Doing so replaced the blank white web UI with a message that stated:
“Service Unavailable - The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.”

I then re-ran the sudo ./installfog.sh, and it ran without any problems. The DB schema update step functioned, and I could then login like normal.

However, I don’t think I’m fully out of the woods yet. The install script for some reason messes up the NIS login system, requiring a reboot to make work again, but after the reboot the FOG Web UI is back to showing “Service Unavailable”. I’m suspecting a user permission problem that I need to dig into next (Maybe I should make this a new topic if I need help).

Thanks for the quick reply

The www-error.log file is full of messages like this:

[05-Feb-2025 08:27:03 America/Toronto] PHP Parse error:  syntax error, unexpected '?' in /var/www/html/fog/lib/fog/fogbase.class.php on line 2594
[05-Feb-2025 08:27:03 America/Toronto] PHP Parse error:  syntax error, unexpected '?' in /var/www/html/fog/lib/fog/fogbase.class.php on line 2594
[05-Feb-2025 08:27:03 America/Toronto] PHP Parse error:  syntax error, unexpected '?' in /var/www/html/fog/lib/fog/fogbase.class.php on line 2594
[05-Feb-2025 08:27:03 America/Toronto] PHP Parse error:  syntax error, unexpected '?' in /var/www/html/fog/lib/fog/fogbase.class.php on line 2594

The same message over and over. They even appears when I’m not trying to access the web UI.

I had a look at the file mentioned in the error log, and that line looks like its setting and “authorized” flag:

$authorized = self::$FOGUser->isValid() ||
  strtolower(($_SERVER['HTTP_X_REQUESTED_WITH'] ?? '')) == 'xmlhttprequest';

This made me wonder if old cookies or other site data in my browser was messing it up. So I cleared my cookies and cache and other browser data. No help.

Good Afternoon

We originally setup our FOG system back in 2018, and it has been working well. As part of some upgrade work we are trying to capture an image of a newer version of Linux to upgrade our HPC Cluster. The old FOG client was having trouble on the newer version of Alma Linux, so we decided that it might be a good idea to upgrade FOG as well.

The install/update script seemed to run without a hitch, but at the step where it indicates that you need to open a web browser to http://xxx.xxx.xxx.xxx/fog/management, I did so, but only got a blank webpage.
I didn’t know what feedback I was expecting for “updating the db schema”, so I assumed that it had happened.

Now, any attempt to access the FOG Web UI results in a blank white web page. The only other thing I know is the browser sees it as an HTTP 500 error.

OS: CentOS 7.5
FOG: 1.5.10.1634 (Updated to this today)

Any help would be greatly appreciated.

@george1421 I managed to find a PCIe network card in an old server on its way to the junk heap. Salvaged that, and placed it in the node in question. iPXE worked fine with it.
So, I guess the moral of the story is some super new network cards iPXE can’t talk to.

@Sebastian-Roth They are managed switches, but pretty much all settings are in their defaults - and, I’m not really familiar with with Spanning Trees, or how to set them up with these switches.
I can however confirm that the network cards are linking up, and that the first stage DHCP for PXE gets an address.

@george1421 I have tried ipxe.pxe, ipxe.kpxe, and ipxe.kkpxe, as well as some of the Intel, Realtek, and UNDIonly variants.
None work, all refusing to see the Ethernet network card
(And, the Intel and Realtek ones won’t see the Infiniband card either, but that doesn’t really matter)

Thanks for the speedy response.

I believe the network cards are booting the old BIOS mode (They are set to “Legacy” in system setup. If I change them to “EFI”, it works even less well).

The boot image is set to ipxe.pxe, although I’ve tried several different files. None work better.

I’m pretty sure the iPXE is starting:
PXE starts and gets and address, then the normal startup messages for iPXE print.
But when it normally (on other computers) says that it is configuring net1, it just says DHCP fails.

Screen shot:

Looking at the screen shot, you can see the standard network boot, and DHCP, and then it switching to iPXE.
iPXE then tries net0, however this is our Infiniband network, not our Ethernet network, so it can be ignored.
It then fails.
I can then run the ifstat utility, and it only shows the Infiniband, no other network cards.

All our other nodes have both Infiniband as well as Ethernet, and they work fine; the iPXE uses “net1”.

Hope this helps.

We have purchased a SuperMicro 4029GP-TRT to be used for scientific computing.
We are using FOG to distribute our OS image, and have had no problems with other computers (except issues that were previously resolved on this forum).
However, this 4029 refuses to boot the iPXE. Here is what happens:
-Computer starts, and starts to boot PXE.
-PXE gets DHCP address, then switches to iPXE.
-iPXE does not get an address, fails, and reboots after 10 seconds.
It seems the iPXE simply doesn’t recognize the network card.

More details:
When iPXE fails, I can select “s” to enter a minimal shell. If I enter the command “ifstat”, it does not show the Ethernet network card.
-(It shows our Infiniband network card, but we’re not booting over that.)
I have tried changing the ipxe image selected by the DHCP server to all the other files provided for PXE. None of them work.
The network card is an on-board adapter, from the Intel C622 chipset.

This is a pretty new system, and a 10gig network card.
Has anyone seen this before?

Thank you

@Quazz
IT WORKED! Thank you!
The ATOM based node started and went into it’s debug task, and is able to see the network (I was concerned about the network as well, as some slightly older Linux distributions couldn’t see the network cards)
We also tested it on a KNL based node, and two Xeon based nodes, and they can all use the Kernel fine.

So, I am curious to know: why isn’t that Kernel feature enabled all the time?

Also, do you guys have any merchandise or swag? We’d like to support you, but a donation may be difficult from within our company’s various structures.

Again, thank you so much!

(Screen shot of ATOM based node in “debug” task)