Configuration Save - Memory size of xxxxxxx bytes exhausted

[Wayne Workman]

On r6991, we are getting an error page when we try to do a configuration save. We looked into the apache error logs and saw the memory limit was being hit. So we increased FOG_MEMORY_LIMIT all the way up to 512 slowly, and that wasn’t enough. So I’m suspecting something else is wrong. There are also some FTP errors in the logs below as well. This particular setup has one storage group and two nodes.

[Wed Mar 30 08:45:30.178881 2016] [:error] [pid 6308] [client 10.64.14.4:49331] PHP Warning: hash_file(ftp://...@10.65.2.20/opt/fog/snapins/): failed to open stream: FTP server reports 550 Could not get file size.\r\n in /var/www/html/fog/lib/client/snapinclient.class.php on line 69
[Wed Mar 30 08:45:00.343359 2016] [:error] [pid 6308] [client 10.13.32.5:52116] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 157548544 bytes) in /var/www/html/fog/lib/fog/schema.class.php on line 36, referer: http://10.51.1.53/fog/management/index.php?node=about&sub=config
[Wed Mar 30 08:44:51.203077 2016] [:error] [pid 8495] [client 10.65.2.124:50696] PHP Warning: hash_file(ftp://...@10.65.2.20/opt/fog/snapins/): failed to open stream: FTP server reports 550 Could not get file size.\r\n in /var/www/html/fog/lib/client/snapinclient.class.php on line 69
[Wed Mar 30 08:44:35.900139 2016] [:error] [pid 8495] [client 10.65.3.91:59894] PHP Warning: hash_file(ftp://...@10.65.2.20/opt/fog/snapins/): failed to open stream: FTP server reports 550 Could not get file size.\r\n in /var/www/html/fog/lib/client/snapinclient.class.php on line 69
[Wed Mar 30 08:44:28.153113 2016] [:error] [pid 8510] [client 10.13.32.5:52068] PHP Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 112099328 bytes) in /var/www/html/fog/lib/fog/schema.class.php on line 36, referer: http://10.51.1.53/fog/management/index.php?node=about&sub=config

[Tom Elliott]

What do those errors have to do with configuration save?

[Wayne Workman]

@Tom-Elliott said:

What do those errors have to do with configuration save?

The memory exhausted error happens exactly at the moment we click the export button for configuration save.

[Wayne Workman]

Another thing is on the exact same revision in my building, I can do a configuration save just fine, but my building is not part of a multi-node setup.

[Tom Elliott]

Please update and try the latest. This should be fixed now.

[Wayne Workman]

the update didn’t work. I think the DB actually is bigger than 512MB.

The history table has 1.4 million rows in it…

MariaDB [fog]> select count(*) from history;
+----------+
| count(*) |
+----------+
|  1396471 |
+----------+
1 row in set (0.00 sec)

[Wayne Workman]

truncating the history table fixed it.

truncate table history;