Posts made by zagaeski

@george1421

@george1421 When I select compatibility it shows it loades bzImage32 ok and init_32 ok. Then flashes and goes to the FOG menu again without the formatting.

@george1421 Ah yes, sorry. Corrected that mistake. I now get the white FOG menu, select Client System Information (Compatibility) and it reloads to the same menu but without formatting. If I select Run Memtest, I get a chainloading error.

@george1421 I spoke too soon. After setting BzImage32 and init_32.xz I receive the attached error when selecting Compatibility mode on the FOG menu.

@Sebastian-Roth This is happening on all our G1 machines. The newer version G2 machines work with the ipxe.efi boot file.

@george1421 Made those changes, will boot into FOG, and I am able to test FOG compatibility. Everything shows as passed. When exiting, I get the Linux dump again.

@Sebastian-Roth After updating to latest version I’m getting below.

Sorry for not including that.

FOG V1.5.4 SVN 6078
Installed on Ubuntu 16.04.
bzImage Version: 4.16.6
bzImage32 Version: 4.16.6

Thanks

I can boot using ipxe.efi or snponly.efi, but when trying to register host or image it will not complete task. It appears to error out on exit. Attached is message after trying to deploy image from FOG splash screen.

@george1421 This seems to have worked. I will try another large group tomorrow and see what happens.

@george1421 I made the suggested edits to the www.conf file. Do I need to do anything with php-fpm? I found where the log was located.

@quazz It appears max_children was set to 5. I have edited the www.conf file to increase max_children to 100. I will see what changes this makes.

Attached are the Apache Error log. Only logs related to PHP.0_1529421739894_apache log.txt

Running 1.5.4 on Kubuntu 16. Used to be able to group deploy image to labs of 30-60 machines, FOG would self queue and run, imaging all machines. Now 6-8 start imaging, then after another 6-8 queue up, the FOG server crashes. Unable to access Web GUI, getting gateway timeout error… I tried rolling back Kernel to 14.15.2, no luck.