@george1421 Hello, I just reverted it back to version 0.11.0 but sadly I’m still having the same issue.

Any other ideas to try out?

Thank you for the reply.
I have not been in the office until today so will try it and reply.

Hello,
I updated my FOG server from 1.5.4 to 1.5.8 a couple of weeks ago to be able to image some new laptops (HP Elitebook 850 G6) that were not imaging with the older version. After some google-ing all the answers pointed to the latest version supporting that laptop’s NVMe drive.

I installed version 1.5.8 and was able to image the laptops. However, now I have an even bigger problem. All my lab computers that have the newer version of HP’s BIOS (the one that you can use the mouse on) get stuck at a rEFInd Initializing... screen. All those computers were working fine with FOG and rEFInd before upgrading to 1.5.8. The computers with the older BIOS type work fine. I am using UEFI for all my computers so my DHCP is setup to use ipxe.efi.
Example:
HP EliteDesk 800 G1 - Works
HP EliteDesk 800 G2 - Doesn’t Work

I have googled for a couple of weeks now trying different things but still no luck. I have tried everything from these links and more (I didn’t save all the links):
https://forums.fogproject.org/topic/10773/fog-with-uefi-refind-error-failure-booting-legacy-bios-os
https://forums.fogproject.org/topic/14189/fog-1-5-7-uefi-refind-boot-to-win-10

I have tried downloading the newest version of refind_x64.efi and changing the Exit to Hard Drive Type(EFI) option in FOG’s iPXE Menu Settings.

Maybe I just didn’t type the right combination of search terms and there is already a solution for this, if so, sorry for the duplicate.

Thanks in advance!

TL;DL:
Updated from 1.5.4 to 1.5.8 now computers with newer BIOS getting stuck at rEFInd Initializing....

@george1421 So I am pretty sure it is fixed now. I looked at the logs for php and found this error

[20-Aug-2019 17:28:19] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

So I changed the pm.max_children setting to 150, just to be sure, and it is now working perfectly!
I re-imaged the same lab with 20 computers and monitored the server to see how many php-fpm services ran and I found that at one point I had 10 instances so bringing that up from 5 did help for sure.

@Sebastian-Roth I restarted the service and the server too just to be sure.

@george1421 I checked the logs and I think I found the issue. I’m not at my office anymore so I’ll test it tomorrow and update the thread.
Thank you so much for your support, quick response, and excellent help!!

@george1421 Made the changes on the server and deployed the image to a lab of 20 computers and it’s giving me the same issue.

@george1421 Thank you so much! I just did that and will test it by imaging more labs. If anything I keep having this issue today or tomorrow I will update the thread.

@george1421 I found it in /etc/php/7.1/fpm/pool.d

@george1421 Thank you! The php_admin_value line is actually commented out (I don’t know why). Does this mean some other setting could be active somewhere else?

Also, what about adding more than 256M to that value?

@george1421 I can’t access the web interface at all, it gives me either a 503 error or 504. The FOG server works fine for day-to-day imaging, but this happens when I am trying to image multiple labs at a time.

I ran the command that you put in your comment and this is the result

Hello everyone.
I’m having an issue that I have no idea how to solve. I am capturing an image and deploying a different image to 20 computers. Once the upload finished it gave me an error when trying to update the database

I am not able to get into the web interface, It gives me a 503 Error

I am able to SSH into the server though!
I know that I can just restart the server but this is not the first time this happens so I would like to fix it for good.

FOG Version: 1.5.4
Server has 4TB storage and 32GB RAM (don’t think this is the issue but in case someone asks)

Any help is extremely appreciated! Thanks!

!!Update: It now gives me a 504 Gateway error (bottom of screen)