Solved. See here.
Basically I changed the php version to 7.3 (which took a lot of effort…)

… And it did!
Solved so far. Even the memory limit problem is gone.
Well, I keep this post in case anybody needs this information later.
@admin : You can decide otherwise and delete the entries.

@fogusnew said in Installation / php / mysql / apache2 - I messed it up:

• However, the install script of Fog does not take this password. “Failed” is the only answer it gives.

Hold your breath! I needed to upgrade the database tables. Now the the script has access to the database. So maybe the install script will cure the story…

Hi community!

Well, I think I really messed it up. Trying to get a memory limit error solved (probably) I created a lot of new problems.

Here is the situation:

• I had a debian 9 running with fog for about 1 year
• I updated Fog to 1.5.9-RC2 to get rid of a problem with snapins (could not upload any anymore)
• So I ran into the memory limit problem, but alt least Fog was running (I could deploy)
• To solve this I decided to upgrade the machine to debian 10 to get php7.3 (also maraDB was upgraded)
• This worked well on the first glance, Fog was running deployment was still possible, but apache was still using php7.0
• So I removed php completely and installed php7.3 “manually” (which is standard in Debian 10)
• This put Fog to death. The installation of php7.3 was no problem, but apache was not taking the new php version to action. Whatever I tried.
• As a last resort I tried to run the Fog Install script. This works until the script asks for the root mysql password. I know this password, I wrote it down, I am able to get root access to the database via sudo mysql_secure_installation, I can change it, etc.
• However, the install script of Fog does not take this password. “Failed” is the only answer it gives.

Anyone out there, who can help me sort this out? Any help is appreciated!
Thanks!
Chris

@george1421 said in Upgrade to 1.5.9-RC2 gone wrong:

@fogusnew said in Upgrade to 1.5.9-RC2 gone wrong:

I was looking for memory_limit values in the files I mentioned above.

If php-fpm is managing the php on your FOG server this should be the proper config file /etc/php/7.0/fpm/pool.d/www.conf

This is the proper value to change php_admin_value[memory_limit] Then restart pphp-fpm.

I did that.

How many computers (with fog client installed) are hitting this FOG server? If you have a master node and multiple storage nodes, I need to know all computers from all sites that have the fog client installed.

I run only one bar metal server with fog on it. We have ~60 PCs to manage. I did not hit the memory limit before I did the upgrade.
I’m off site again, but will be back next week. I’ll check everything once more and report back. Thanks, again!

@Sebastian-Roth I restarted the services and the system. I can see the the increasing memory in the log; but still “more” is requested.
@george1421 I was looking for memory_limit values in the files I mentioned above. I doubled them several times from 128M to 256M, and then step by step to 2048M. In all those files.

Still no change.

Thnaks a lot for your efforts

Increasing the memory limit in /etc/php/7.0/fpm/php.ini and /etc/php/7.0/apache2/php.ini and /etc/php/7.0/fpm/pool.d/www.conf does not help.

Well, sorry, that I bring up this issue after such a long time. But I’ve been off site for a while. Now I was able to look at the logs.
I get a white screen and a PHP error

[proxy_fcgi:error] [pid 9320] [client 172.28.171.4:53982] AH01071: Got error 'PHP message: PHP Fatal error:  Allowed memory size of 2097152 bytes exhausted (tried to allocate 16384 bytes) in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 260\n', referer: http:// .... fog/management/index.php?node=home

when I try to access the “hosts list” page.

a similar one when I try to get to the fog settings:

[proxy_fcgi:error] [pid 9320] [client 172.28.171.4:55178] AH01071: Got error 'PHP message: PHP Fatal error:  Allowed memory size of 2097152 bytes exhausted (tried to allocate 65536 bytes) in /var/www/html/fog/lib/fog/fogbase.class.php on line 467\n', referer: .... /fog/management/index.php?node=about

No errors in the php7.0-fpm log
I searched the forum for similar topics, could find some, but can not make a solution out of them.

I had a 1.5.3 running
I upgraded according to the wiki to 1.5.9-RC2.
No errors in the script, so far. Everything went smoothly.

I can login to the WebGUI, but here some problems occur: Several link just show blank pages. Without any content:

• Hosts
• FOG Settings
• Tasks -> list hosts
• Tasks -> active snapins (no tasks are running)
• Several reports just generate blank pages, too.

Please, can anybody tell me how to track this down?

Thanks a lot!
Chris

Dear community!

I found descriptions of the very same problem on several threads here in the forum. See (as example) here.
It’s suggested to check the upload limit, but I already created snapins with several 100MB size and everything worked very well until now. Which means the limit is ok.
This time I wanted to create a simple snapin with ~100MB but FOG would not accept it throwing the error message regarding missing snapin name. Weird.
The only thing I did differently I can think of is this:
I can access Fog from outside my local network. When I do so obviously the bandwidth is far lower than being present. At some point I tried to create the snapin from outside over the internet, but I did not get any response from FOG for a longer time. So I canceled the process (I guess while the upload was still going on). I decided to wait until I was on site again. But since then I was not able to create any snapin whether on site nor over the remote connection.
Could there be a connection?
How do I investigate this?
Perhaps there is some temp file lying around that blocks further snaping creation?

My 1.5.4 Fog is running on CentOS

Thanks for any input on this.