Fog using a huge amount of memory and failing
- 
 
- 
 @joe-gill Ok you are using php-fpm. That is good. Now we need to understand what is consuming the memory. I had a previous post where I was asking specific questions about your current setup. Please respond to that… and Depending on your distro there is a php-fpm file that fog creates it should be in /etc (in a sub directory) called www.conf. Under centos 7 its in/etc/php-fpm.dLets review that file, towards the middle there should be this line uncommented.pm.max_requests = 2000Let make sure its not commented out. 
- 
 @george1421 
 Running on a Hyper V Virtual Machine
 FOG OS - Debian 9.4
 Memory - 4 GB
 CPU - 2 CPUs allottedI used Top to determine these. If their is a better command let me know and I will certainly run that and report back. Memory Usage (in order from most to least) – 
 Apache2 (20 percent)
 mysql
 FOGImageSize
 FOGPingHosts
 FOGSnapinHashCPU Usage – 
 Apache2
- 
 @joe-gill Can I get to bits of info I forgot to ask? - Top CPU usage service
- Number of clients you have in your FOG environment
- Fog check in interval Fog Configuration -> Fog Settings -> Fog Client -> FOG_CLIENT_CHECKIN_TIME (if you have less than 300 [5 minutes] you might want to bump that up to 300 or 600 seconds).
 
- 
 @george1421 
 Top CPU usage service is Apache2.
 Total hosts is ~500.Where is the www.conf file located in Debian? I searched high and low and could not find it. I found something in the /etc/php/7.0/ directory but it didn’t have pm.max_requests. Thanks! 
- 
 @joe-gill said in Fog using a huge amount of memory and failing: /etc/php/7.0/ is probably a close directory for php 7.x in there should be a maybe a /etc/php-fpm.d directory and in that there should be www.conf. The file name is consistent its just the location of the file that changes with the version of php. Also I added an additional question to my list. Fog check in interval Fog Configuration -> Fog Settings -> Fog Client -> FOG_CLIENT_CHECKIN_TIME (if you have less than 300 [5 minutes] you might want to bump that up to 300 or 600 seconds). 
- 
 I seem to be having bigger issues. PHP is completely un-responsive now. I can and have been able to reach the Apache test page on our server but cannot get anything to run in php. I tried restarting the service, rebooting the server, unistalling php and re-running the fog installer. I will start a new thread and tag you in it. 
- 
 @george1421 Huh. I’ve got Apache 2.0 Handler here. Should I follow the steps in the link or is there something else that I should do? 
- 
 @jstephen You have 1.5.4 installed, but you have the apache handler in place and you didn’t change it? If that is true then I can understand why your UI is a bit sucky. That is why they moved to php-fpm. Wait your info.php page showed that you had the fast cgi enabled. edit: Hint, make sure you are replying to the proper thread.  
- 
 @george1421 George, I think I did reply to the proper thread… it is just a little confusing since someone else with a similar problem seems to have popped in! Fog is version 1.5.4. This same server has been updated through many, many versions for 4 years or mo so maybe it has some lingering old stuff! My phpinfo page does not indicate that I have FastCGI enabled. I’m reading through this thread ( https://forums.fogproject.org/topic/10717/can-php-fpm-make-fog-web-gui-fast/4 ) now to see whether there is information about getting mpm working. 
- 
 @jstephen Sorry my mistake same issue and same color avatar. I don’t think the FOG installer is setting mpm by design. That will help with performance but not using php-fpm will give you a craptacular experience with the new gui. So you ran the info-php script and its still reporting Apache handler?  
- 
 I was able to remote in and find out what was going sideways with the OP’s system. I’ll fill out the details in a bit, but there is the keys. mods-enabled/php5.conf set handler 9.4 sites-enabled/001-fog.config It appears to be an issue with at least debian 9.4 at the moment where php-fpm wasn’t being enabled causing the sluggish UI and high apache usage. 

