Issues with Fog 1.5.2
-
@k-hays said in Issues with Fog 1.5.2:
max_spare_servers = 6
Set that value to 40 and make sure you have the memory allocated to 256M and you should be good to go. Understand this fix will only address imaging and not your initial post of html in the FOS screen.
-
@george1421 ok so max_spare_servers needs to be 40. gotchya. Should i change the other 2 _servers settings from 6? Also should max_spare_servers be set to the same as number as pm.max_children?
-
@k-hays also we have been able to get to the web gui recently without issue.
-
Well we went ahead and tested it the the _servers options set to 6,6,6 respectively just to see. It is in fact working. The image is running right now but we waited for the next batch in the unicast task to start and they did. We hadn’t previously gotten the first batch to finish successfully before that so it’s lookin good. So the only other thing you think i should change then would be max_spare_servers to 40; not either of the other min_servers/startserver settings from 6?
-
@k-hays Please, only change MAX server AND make sure you added the memory line for 256M. The rest of the values are ok at 6.
-
@george1421 Yep the memory has been changed since this morning; and i will change the max server when the tasks complete. Thank you !! can or should the memory go higher? The server has 32 gigs of ram, not that it needs it.
-
@k-hays Not for the worker threads. We are finding (so far) 256MB per php-fpm worker is working well. Run with these setting and for sure provide feedback. Once we get these number working stable on all that are having issues we will include them in the fog 1.5.5 update.
-
@george1421 So far so good. We were able to deploy to an entire lab using unicast. No errors yet! I’ll be using it more this week and will provide further feedback. Thank you!!
-
@george1421 Also, did these settings change after a certain update? On our old server we had these issues after an update when we were previously getting by alright.
-
@k-hays Between FOG 1.5.0 and 1.5.1 (or 1.5.1 and 1.5.2 sorry I can’t remember) the developers switched from using the built in php engine in apache to using a dedicated php engine (php-fpm). This was done to address an issue with GUI slowness reported with the new 1.5.x Web GUI on certain distributions. Baseline testing then showed an excellent improvement in GUI responsiveness as well as client check ins were not causing an issue with heavy web server load as they were before.
After 1.5.2 was released the developers started seeing other reports of issues with multicasting and unicasting in larger environment that wasn’t see during development. So certain tweaks to the php-fpm config files were made in 1.5.3 and 1.5.4. Increasing the memory limit even more to 256MB resolved a multicasting issue was discovered after 1.5.4. was released. That setting will be in 1.5.5 when its released in a few months. With these new settings you should see a pretty stable multicasting deployment.
-
@george1421 Gotchya, that explains it, Thank you!
