Fresh Install of 1.5.9 with CentOS 7 issues

Chris Whiteley

#!ipxe
set fog-ip 192.168.20.9
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.20.9/fog/ consoleblank=0 rootfstype=ext4 nvme_core.default_ps_max_latency_us=0 mac=18:66:da:4a:79:d9 ftp=192.168.20.9 storage=192.168.20.9:/images/dev/ storageip=192.168.20.9 osid=9 irqpoll hostname=207521-test chkdsk=0 img=Windows10EDU-2004-Template imgType=n imgPartitionType=all imgid=16 imgFormat=5 PIGZ_COMP=-6 adon=1 addomain="******" adou="" aduser="*****" adpass="*****" hostearly=1 pct=5 ignorepg=1 type=up
imgfetch init_32.xz
boot

george1421

@Chris-Whiteley Just to confirm this is the fog server’s IP address" 192.168.20.9 (I’m sure I know the answer but just double checking).

So does this download the bzImage file?
http://192.168.20.9/fog/service/ipxe/bzImage

Chris Whiteley

@george1421 The bzImage file downloaded when I clicked that link. Yes, the IP is 192.168.20.9.

george1421

@Chris-Whiteley Well this is a good one. It should be working especially if you can download the file via a browser. All of the parts are in place and work individually.

george1421

@Chris-Whiteley if you were to pxe boot to the error and hit s to get to ipxe console.

Then in the ipxe console what happens when you key in imgfetch bzImage ? It should say that it trasferred it. You can’t do anything with it, but this will test the http download to memory of the kernel.

Does only this specific computer do this or does all computers even of different models error out? There is something here we are missing.

Chris Whiteley

@george1421 I just tried that command and got:

Could not start download: Operation not supported (http://ipxe.org/3c092003)

Sebastian Roth

@Chris-Whiteley That sounds really strange. Do you have SELinux enabled or disabled? Though you wouldn’t be able to download the file through the browser it SELinux would be in the way.

So let’s try to rule out some things:

Use a different machine (best different vendor and all) and try to upload an image from that.
Re-download iPXE binaries and put in /tftpboot just to make sure there is no issue with those: https://github.com/FOGProject/fogproject/tree/master/packages/tftp

Chris Whiteley

@Sebastian-Roth I just make SELINUX disabled. It was set to permissive. That didn’t make a difference.

I tried using a different machine, but all we have are Dells, but I tried 3 different models and encountered an issue where it would sometimes download the bzImage, but then get to init.xz and do the [connecting]… that goes across the screen and then fail.
I downloaded the iPXE binaries and that didn’t help either.

Is there a log I can look at specifically for this issue?

Thanks for the help!

Tom Elliott

@Chris-Whiteley I don’t have access to a server right now but if I remember correctly, there is a fog setting (fog configuration->fog settings) that stores the fog service directory.

If that field is fog/service then I’m not sure what’s wrong, but if it’s fogservice as we’ve seen in the past, I imagine this could be causing the problem.

Based on what I can see, this is currently just set to fog, if that’s the case can you change it to be fog/service

The part that’s making me think this is the output of

set boot-url http://${fog-ip}/${fog-webroot}

This should be
set boot-url http://${fog-ip}/${fog-webroot}/service/ipxe

Sebastian Roth

@Tom-Elliott said in Fresh Install of 1.5.9 with CentOS 7 issues:

This should be
set boot-url http://${fog-ip}/${fog-webroot}/service/ipxe

No I don’t think so. iPXE pulls files that do not a full URL from the same location it got the last file from. So it pulls http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php and would download kernel and init from that same location as well.

Chris Whiteley

This post is deleted!

Sebastian Roth

@Chris-Whiteley Unfortunately there is no log file for this except the Apache logs.

Please run tail -f /var/log/httpd/access_log while doing the PXE boot and see if you get the requests logged in there.

Chris Whiteley

@Sebastian-Roth This is what I saw:

192.168.20.41 - - [06/Oct/2020:08:37:18 -0700] "POST /fog/service/ipxe/boot.php HTTP/1.1" 200 652 "-" "iPXE/1.20.1+ (g4bd0)"

192.168.20.41 is the client

Sebastian Roth

@Chris-Whiteley Nothing after that?

Chris Whiteley

@Sebastian-Roth It just had a connection thing with my browser. At least that’s what I think it is.

192.168.20.9 - - [06/Oct/2020:08:43:58 -0700] "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 4350 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"

Sebastian Roth

@Chris-Whiteley There must be something we are missing here. Is that machine that is not able to PXE boot from your FOG server in the same subnet as the FOG server? Connected to the same switch?

Can you please take a picture of the error on screen and post here? Just wanna make sure we are not missing something here.

Tom Elliott

I was simply thinking of what potentially be the issue. In the past I know we had a type of issue with fog/service being set as fogservice. So it was just a thought.

As you’re using centos, can you provide logs for:

/var/log/php-fpm/www-error.log (or very close)

Php errors will show up there for centos typically.

Chris Whiteley

@Sebastian-Roth

The error on the screen is the same one that I have posted below in this thread. Here are a couple of more pictures about it.

It is connected through 3 different switches, but I have not had issues with this before. They are also on the same subnet: 192.168.20.1/24.

Chris Whiteley

@Tom-Elliott

[04-Oct-2020 03:47:02] NOTICE: error log file re-opened
[04-Oct-2020 15:32:43] NOTICE: [pool www] child 26930 exited with code 0 after 138892.087835 seconds from start
[04-Oct-2020 15:32:43] NOTICE: [pool www] child 15042 started
[04-Oct-2020 15:32:50] NOTICE: [pool www] child 26795 exited with code 0 after 138950.201260 seconds from start
[04-Oct-2020 15:32:50] NOTICE: [pool www] child 15045 started
[04-Oct-2020 15:35:30] NOTICE: [pool www] child 27071 exited with code 0 after 138908.805085 seconds from start
[04-Oct-2020 15:35:30] NOTICE: [pool www] child 15194 started
[04-Oct-2020 15:39:14] NOTICE: [pool www] child 27318 exited with code 0 after 138879.587345 seconds from start
[04-Oct-2020 15:39:14] NOTICE: [pool www] child 15486 started
[04-Oct-2020 15:39:42] NOTICE: [pool www] child 27320 exited with code 0 after 138907.167868 seconds from start
[04-Oct-2020 15:39:42] NOTICE: [pool www] child 15512 started
[04-Oct-2020 15:41:12] NOTICE: [pool www] child 27405 exited with code 0 after 138913.195601 seconds from start
[04-Oct-2020 15:41:12] NOTICE: [pool www] child 15600 started
[04-Oct-2020 16:46:31] NOTICE: [pool www] child 31676 exited with code 0 after 138896.314150 seconds from start
[04-Oct-2020 16:46:31] NOTICE: [pool www] child 19773 started
[04-Oct-2020 18:49:32] NOTICE: [pool www] child 7284 exited with code 0 after 138870.684686 seconds from start
[04-Oct-2020 18:49:32] NOTICE: [pool www] child 27795 started
[04-Oct-2020 21:13:51] NOTICE: [pool www] child 16588 exited with code 0 after 138930.860352 seconds from start
[04-Oct-2020 21:13:51] NOTICE: [pool www] child 4701 started
[05-Oct-2020 08:34:51] NOTICE: Terminating ...
[05-Oct-2020 08:34:51] NOTICE: exiting, bye-bye!
[05-Oct-2020 08:35:31] NOTICE: fpm is running, pid 1089
[05-Oct-2020 08:35:31] NOTICE: ready to handle connections
[05-Oct-2020 08:35:31] NOTICE: systemd monitor interval set to 10000ms
[05-Oct-2020 20:25:46] NOTICE: [pool www] child 1813 exited with code 0 after 42614.612041 seconds from start
[05-Oct-2020 20:25:46] NOTICE: [pool www] child 16127 started
[05-Oct-2020 20:27:04] NOTICE: [pool www] child 1811 exited with code 0 after 42692.732221 seconds from start
[05-Oct-2020 20:27:04] NOTICE: [pool www] child 16220 started
[05-Oct-2020 20:27:47] NOTICE: [pool www] child 3239 exited with code 0 after 42730.396625 seconds from start
[05-Oct-2020 20:27:47] NOTICE: [pool www] child 16263 started
[05-Oct-2020 20:27:51] NOTICE: [pool www] child 1812 exited with code 0 after 42740.360500 seconds from start
[05-Oct-2020 20:27:51] NOTICE: [pool www] child 16273 started
[05-Oct-2020 20:27:52] NOTICE: [pool www] child 1815 exited with code 0 after 42740.447148 seconds from start
[05-Oct-2020 20:27:52] NOTICE: [pool www] child 16275 started
[05-Oct-2020 20:28:04] NOTICE: [pool www] child 1814 exited with code 0 after 42752.756222 seconds from start
[05-Oct-2020 20:28:04] NOTICE: [pool www] child 16289 started
[05-Oct-2020 20:29:55] NOTICE: [pool www] child 1939 exited with code 0 after 42862.776461 seconds from start
[05-Oct-2020 20:29:55] NOTICE: [pool www] child 16407 started
[06-Oct-2020 07:03:34] NOTICE: Terminating ...
[06-Oct-2020 07:03:34] NOTICE: exiting, bye-bye!
[06-Oct-2020 07:03:52] NOTICE: fpm is running, pid 1061
[06-Oct-2020 07:03:52] NOTICE: ready to handle connections
[06-Oct-2020 07:03:52] NOTICE: systemd monitor interval set to 10000ms

Tom Elliott

@Chris-Whiteley that’s the error log itself, there should also be one for www

Fresh Install of 1.5.9 with CentOS 7 issues

272

12.0k

17.3k

155.2k