@Wayne-Workman That IS AWESOME! Save me and my team a few minutes in config…very cool.

For others reading and who are suing FOG for the first time. PXe boots up perfectly fine, DHCP will “Spin” and then you’re machine will likely not boot past a black screen perhaps with a flashing cursor. The steps from my previous post (copied inline here) fixed that issue for me:

Steps I have taken to correct:

Boot into BIOS Change the security settings to remove Secure boot change boot type (away from UEFI to BOTH) Set Legacy to first on the boot options.

However as soon as 1.3.0 is out if the issue you had was like mine it likely wouldn’t have been an issue. Also the instructions at the end of the install if using FOG in a Windows DHCP server environment are critical. The Fog team should be given a lot of credit for including those. It made my first install of FOG incredibly fast.

@Wayne-Workman I appreciate that. I did a search and couldn’t find Kernel Errors Fog. I will test the manual edit of the Settings and see if that corrects the error.

@Quazz that’s it 😄 Stupid me, i should find that by myself in normal… grrrr 😉
Thank you for your help.

Regards X23

Follow up: https://forums.fogproject.org/topic/7606/legacy-partimage-images-with-fog-trunk

SOLVED https://forums.fogproject.org/topic/7489/around-100-cpu-usage-constantly/16

mysql not accessible outside 127.0.0.1 (localhost)!

Regards X23

@adukes40 said in Issues with FOG Client Pre-Sysprep (Or maybe it's me):

@Wayne-Workman batting .1000 so far lol. maybe a trip to the casino is in order

I wish I had such luck about a week and a half ago. Since the newest client is so much more efficient, there is a great chance it will screw up sysprep. I got lucky on only one PC out of 26 before I made the change in the SetupComplete.cmd. That was a bad day lol.

Edit: I should mention after the changes, I’ve not had a single issue.

Notifying @joe-schmitt about the issue.

@abibbas said in cant image a host:

I select a host to image and it will just sit in the que

That could mean a lot of things.

We need very specifically exactly any error messages that you’re seeing on the target computer. Photos/screenshots would be very helpful if you could provide them.

What is the model of the computer, the OS it’s running? What distribution of Linux and version are you running FOG on?

@Tom-Elliott

Here is the latest in my error logs:

BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
[Fri May 27 12:04:35.841463 2016] [:error] [pid 26076] [client 172.52.8.7:58657] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 105, referer: http://172.28.2.21/fog/management/index.php?node=report&sub=host-list
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
[Fri May 27 12:03:19.508898 2016] [:error] [pid 22082] [client 172.52.8.7:58558] PHP Strict Standards: Only variables should be passed by reference in /var/www/html/fog/lib/pages/schemaupdaterpage.class.php on line 46, referer: http://172.28.2.21/fog/management/index.php?node=schema
[Fri May 27 12:03:19.218924 2016] [:error] [pid 25953] [client 172.24.8.30:50751] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in /var/www/html/fog/lib/client/servicemodule.class.php on line 21
[Fri May 27 12:03:19.218895 2016] [:error] [pid 25953] [client 172.24.8.30:50751] PHP Warning: array_combine(): Both parameters should have an equal number of elements in /var/www/html/fog/lib/fog/fogbase.class.php on line 262
[Fri May 27 12:03:19.133697 2016] [:error] [pid 22091] [client 172.24.8.30:50750] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in /var/www/html/fog/lib/client/servicemodule.class.php on line 21
[Fri May 27 12:03:19.133666 2016] [:error] [pid 22091] [client 172.24.8.30:50750] PHP Warning: array_combine(): Both parameters should have an equal number of elements in /var/www/html/fog/lib/fog/fogbase.class.php on line 262
[Fri May 27 12:03:19.030185 2016] [:error] [pid 22084] [client 172.24.8.30:50749] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in

@Tom-Elliott No, I found it. Discovered underlying issues with Centos, not FOG, so I’m taking backups of config and images, and reinstalling.

Long story short, systemd got corrupted due to me being an idiot.

@george1421 said in Cannot PXE boot:

I have also seen that some projects actually have a service page that lists if the services are running or not, and gives the admin a choice to stop or start a service.

I’ve got a DHCP plugin ready to be integrated into fog… just having a lot of trouble understanding the plugin system for such a large plugin.

But, I can easily create a two-file + small DB change plugin that will detect the status of services and offer the ability to restart on a click.

Again though, the one thing holding me back from going wild is a lack of understanding of the plugin system. People have attempted to explain it to me many times but it just doesn’t click. I need to be shown.

@adukes40 Sounds right.

@adukes40 no problem.

I can say for sure that the e6410 pxe boots just fine using the trunk (dev) build of 1.2.0.

The e6410 is a bios only system that does boot with the undionly.kpxe. Since you said that you had an older version of FOG installed, can you tell me what you have defined for dhcp option 67?

When iPXE boots, there is a series if hex values that indicate the build beyond the version number. What is the build number.

@Rwest Are you using FOG trunk or version 1.2.0. Please post a picture of the error you see when trying to deploy!

@fdrouard wol/wol.php path no longer exists.

@arnaudrigole As you can see there are no udp-sender processes running. So multicast just cannot happen. Those should be started by the FOGMulticastManager service (which seems fine on your server). So please check the logs as I suggested earlier.

@MadsMagnus Great to hear that you found out what was causing the issue! Marking this for addition to the #wiki article on debugging boot problems.

You’re experiencing FTP related issues. There are a number of things that cause this, but greater than 90% of the time it’s simply bad credentials.

This article contains everything you need to get it sorted:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@Tom-Elliott ok roger that. Thanks so much.