Problems after 1.4.2 to 1.5.5 Upgrade
-
I do this days a migration and upgrade from fog1.4.2 to fog1.5.5 and on this version i have two problems.
firts i can’t list my 88 storagenodes, the node=storage page falls into service unavailable.
second i can’t open the node=about page with the same results as first.the node=host&sub=list go to This page don’t works tryin to list my 14.500 pc’s but node=group&sub=membership&id= works without problems.
Thanks in advance.
-
node=storage page and node=about pages solved.
Solution increase TimeOut and ProxyTimeout to 120 secs.
Currently only fails with list all hosts page.
-
14500 computers in the database are a lot of. I had troubles in the past when I tried to list my 8000 computers, this was solved with the php-fpm module but maybe in you case the problem is other (timeouts in the database or used memory)
Any error in the apache logs?
-
@Fernando-Gietz
yes at the moment i found apache general TimeOut and fast-cgi ProxyTimeout.That solve the storage list (node=storage) and the list of nodes in about page (node=about).
Maybe i must increase a bit more to test, but the error page is diferent.
-
@EduardoTSeoane Which version of PHP do you have?
rpm -qa | grep phpordpkg -l | grep php -
rpm -qa | grep php
php-common-7.2.18-1.el7.remi.x86_64
php-7.2.18-1.el7.remi.x86_64
php-ldap-7.2.18-1.el7.remi.x86_64
php-fpm-7.2.18-1.el7.remi.x86_64
php-json-7.2.18-1.el7.remi.x86_64
php-cli-7.2.18-1.el7.remi.x86_64
php-mysqlnd-7.2.18-1.el7.remi.x86_64
php-mbstring-7.2.18-1.el7.remi.x86_64
php-pecl-zip-1.15.4-1.el7.remi.7.2.x86_64
php-process-7.2.18-1.el7.remi.x86_64
php-pdo-7.2.18-1.el7.remi.x86_64
php-bcmath-7.2.18-1.el7.remi.x86_64
php-gd-7.2.18-1.el7.remi.x86_64 -
To be exactly the NDR is HTTP ERROR 500
-
@EduardoTSeoane Ok, good to know you have PHP 7.2! Increasing the timeout is not too bad of an idea. There were changes since 1.5.5 that might be of help to you. So you might consider updating to 1.5.6 to see if that helps. Those are the changes that should help speed wise:
- https://github.com/FOGProject/fogproject/commit/859fca523636c407187190f3b34b2ced55b98c28
- https://github.com/FOGProject/fogproject/commit/87338676f5aa87687aad243ab47e80798151dd6c
- https://github.com/FOGProject/fogproject/commit/67b4e64ed6ed6190291fb9fbb9599d5c12af1792
- https://github.com/FOGProject/fogproject/commit/0e54cfe594de9da9becea3a88b556ae02697d671 (the most important one I reckon!)
- https://github.com/FOGProject/fogproject/commit/6ccf933d3358ef9e1847a35cc943ad26a03b8dd1
- https://github.com/FOGProject/fogproject/commit/c01e710d0eda05dda3a20767948e9e0534ef89dd
- https://github.com/FOGProject/fogproject/commit/3b4ff68ecd4944920366b18993f23f2da8f13075
You’ve probably one of the biggest FOG installations and I have to admit that we (as in the FOG devs) didn’t write the code with such huge environments in mind. So we need to work together to try and make this work more smoothly with lots and lots of nodes and clients.
So please try updating to 1.5.6 and we’ll take it from there.
-
@Sebastian-Roth @Fernando-Gietz
Solved!!!
Solution:
In /etc/httpd/conf.d/fog.conf (outside and before of VirtualHost tag):
Add this parameters:- TimeOut 120
- ProxyTimeout 120
In /etc/php-fpm.d/www.conf
- Increase php_admin_value[memory_limit] = 1350M
But it’s hard to load the info.
Thank’s to all for help -
@Sebastian-Roth @Fernando-Gietz
I’m glad to help in everything i can, only have to request.Tomorrow I do a test, to start, on my dev environment with the same database.
By the moment I put the following feature request:
-
@EduardoTSeoane Definitely give 1.5.6 a try. The changes should make a difference in your case.
-
@Sebastian-Roth
Upgraded to 1.5.6 as you suggested.It seems to be a bit faster, but i need to do the corrections on the server with the same values.
Now i’m experiencing another issue posted as https://forums.fogproject.org/topic/13328/fog-snapins-not-ordered-on-launching-time