I just wanted to update the forums incase anyone else came across this issue.
I ended up changing the settings /etc/xinetd.d/tftp to adjust the block size.

Old:
server_args     = -s /tftpboot
New:
server_args     = -B 1350 -s /tftpboot

@sebastian-roth yeah, thanks for the tip plugins have got me in the past I should have tried that before posting.

@sebastian-roth
I have Accesscontrol, Location, persistentgroups, subnetgroup and wolbroadcast installed.

**UPDATE: I Just removed HostStatus and SubnetGroups as I wasn’t using it, and the problem is gone. I don’t know which plugin was causing it.

@sebastian-roth I did what you asked.
The Fog Client is installed on the client system.
This is happening on 2 UEFI Systems so far. I don’t have that many
I made sure the machine was powered off. I went into the host settings and set the Host client Bios Exit Type to Exit and clicked save. I refreshed the page and made sure the setting was still present. I powered on the client and pressed the ESC key to access the fog menu. (I have the fog menu hidden) I refreshed the fog web page and the Host Bios Exit Type was changed back to “- Please Select an Option”.

@sebastian-roth If the machine reboots for any reason manually or through fog task it gets reverted

“Host Bios Exit Type” and “Host EFI Exit Type” get reverted back to “-Please select an option” after the client reboots.

@sebastian-roth
Here is a screenshot:

The strange thing is it works with UEFI bios

This is a site that was working correctly with our previous service provider.
Now we have a Fortigate 60F as the router instead of a Cisco 1941. I am convinced it has to be something on the Fortigate that is blocking the traffic.

I have a storage node at one of our remote sites. The client PXE boot will not download the undionly.kkpxe file.

I have included the log file that shows successful attempts from clients and then the unsuccessful clientIP=10.26.100.115

One thing in particular that I noticed is that the client gets assigned 2 different IP addresses (10.10.150.90 10.10.150.195) during the PXEboot and TFTP exchange. Is there a reason to why it would assign 2 different IP addresses?

May 19 12:28:05 10fogserver in.tftpd[7343]: Client 10.26.100.115 finished undionly.kkpxe
May 19 12:28:05 10fogserver in.tftpd[7343]: Client 10.26.100.115 timed out
May 19 12:34:02 10fogserver in.tftpd[10201]: Error code 0: TFTP Aborted
May 19 12:34:02 10fogserver in.tftpd[10202]: Client 10.10.150.90 finished undionly.kkpxe
May 19 12:34:06 10fogserver in.tftpd[10218]: Client 10.10.150.195 finished default.ipxe
May 19 12:41:34 10fogserver in.tftpd[13599]: Error code 0: TFTP Aborted
May 19 12:41:34 10fogserver in.tftpd[13600]: Client 10.10.112.115 finished undionly.kkpxe
May 19 12:41:38 10fogserver in.tftpd[13620]: Client 10.10.112.193 finished default.ipxe
May 19 12:42:40 10fogserver in.tftpd[14122]: Error code 0: TFTP Aborted
May 19 12:42:40 10fogserver in.tftpd[14123]: Client 10.10.112.115 finished undionly.kkpxe
May 19 12:42:44 10fogserver in.tftpd[14159]: Client 10.10.112.193 finished default.ipxe
May 19 12:43:56 10fogserver in.tftpd[14625]: Error code 0: TFTP Aborted
May 19 12:43:56 10fogserver in.tftpd[14626]: Client 10.10.112.115 finished undionly.kkpxe
May 19 12:44:00 10fogserver in.tftpd[14646]: Client 10.10.112.193 finished default.ipxe
May 19 12:46:18 10fogserver in.tftpd[16079]: Error code 0: TFTP Aborted
May 19 12:46:24 10fogserver in.tftpd[16080]: Client 10.26.100.115 finished undionly.kkpxe
May 19 12:46:24 10fogserver in.tftpd[16080]: Client 10.26.100.115 timed out
May 19 12:48:32 10fogserver in.tftpd[17077]: Error code 0: TFTP Aborted
May 19 12:48:38 10fogserver in.tftpd[17078]: Client 10.26.100.115 finished undionly.kkpxe
May 19 12:48:38 10fogserver in.tftpd[17078]: Client 10.26.100.115 timed out

If anyone has any suggestions please let me know.

Thanks.

@sebastian-roth said in Boot Porteus Kiosk iso from fog pxe menu:

@Greg-Plamondon From what I read you can’t really install the kiosk client. Maybe I missed that part. But the FAQ states that you can customize the ISO file.

For PXE booting, have you tried memdisk iso booting yet? Thou this is legacy BIOS mode only:

initrd http://${fog-ip}/path/to/porteus.iso
chain memdisk iso raw
boot || goto MENU

Edit: Quickly extracted the ISO and found this in boot/pxelinux.cfg/default:

label pxe
kernel vmlinuz
append initrd=initrd.xz,pxelinux.cfg/initrdpxe.xz quiet http_server=

So you might be able to boot the extracted ISO. But on the other hand we don’t know too much about the kernel parameters for network booting this beside the litte information on their website: https://porteus-kiosk.org/pxe-server.html

Be aware that FOG is not using pxelinux anymore. We use iPXE now and while you can do many more things with iPXE it’s not always possible to translate things over from the old pxelinux.

Thanks @Sebastian-Roth for looking into this for me. I guess I will stick the the USB stick installs for now.

We use Porteus Kiosk for our open enrollment process. instead of inserting a USB stick and installing the kiosk, I would like to install it from PXE.
If someone could help me with this it would be greatly appreciated.

After uploading the FOG Banner image, the fields are empty for both:
FOG_CLIENT_BANNER_IMAGE
FOG_CLIENT_BANNER_SHA
in the GUI.

When accessing the user reports section I get the following message:

Could I please have Wiki access?
Thanks.

the Force Reboot option does not update the DB “hostEnforce” value stays at ‘0’ if you manually set it to ‘1’ in the database the GUI shows it checked and unchecking it returns the value to ‘0’ as expected.

The browse for file dialogue window does not appear.

Keep up the good work the new interface looks amazing!

Is there any way that I can see what fog clients are having issues with the fogserver?
I have come across multiple clients recently that have not been checking in for user reports. A simple resetting of the Encryption Data in the GUI fixed the issue. If there was a report I could run that displayed the last successful check-in of the clients I think that would help.

@sebastian-roth yes I believe that was the case. I don’t remember the record count as I already purged data older than 30 days. I set up a SQL event that runs daily.

DELETE from userTracking WHERE utDate < now() - interval 30 DAY;

I can now run the reports

any time I try and use the user tracking to find what PC a user is logged into I get:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

The apache error.log:

[Wed Apr 07 09:39:23.233725 2021] [proxy_fcgi:error] [pid 23644] (70007)The timeout specified has expired: [client 192.168.10.170:49336] AH01075: Error dispatching request to :, referer: http://10fogserver.xxxxxxx.com/fog/management/index.php?node=report

I figured it out… I must have screwed up some permissions on the web_root so I removed /var/www/html/fog/ and re-installed fog and all is well…

Thanks!