Solved Issues with Fog 1.5.2
-
@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!
