Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ #13625] Sync: do not artificially limit available memory #665

icinga-migration opened this issue Dec 15, 2016 · 4 comments


Copy link

@icinga-migration icinga-migration commented Dec 15, 2016

This issue has been migrated from Redmine:

Created by tgelf on 2016-12-15 17:40:42 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-12-15 17:40:42 +00:00 (in Redmine)

We currently limit ourselves, even with more memory assigned in the php.ini

Copy link

@saikrishnagaddipati saikrishnagaddipati commented Jun 28, 2017

I am getting the below error when i do a puppetDB sync in Icinga director. Below is the error which is displayed in the IcingaWeb UI.
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /usr/share/icingaweb2/modules/puppetdb/library/Puppetdb/PuppetDbApi.php on line 184

Is my error related to the above issue?

Copy link

@Thomas-Gelf Thomas-Gelf commented Jun 28, 2017

@saikrishnagaddipati: blind guess: no, your error happens at an earlier stage. Please try to raise the memory_limit in your php.ini and reload your web server.

Copy link

@saikrishnagaddipati saikrishnagaddipati commented Jun 29, 2017

Hi Thomas, I am getting the below error even after increasing the memory_limit to 5G in php.ini.
After 20-30 minutes it errors out with the following message in the UI
Fatal error: Maximum execution time of 30 seconds exceeded in /usr/share/icingaweb2/modules/puppetdb/library/Puppetdb/PuppetDbApi.php on line 297

any suggestions?

@Thomas-Gelf Thomas-Gelf added this to the 1.5.0 milestone Feb 25, 2018
@Thomas-Gelf Thomas-Gelf self-assigned this Feb 25, 2018
Copy link

@Thomas-Gelf Thomas-Gelf commented Feb 25, 2018

This should have been fixed on day after v1.4.0, will be released with v1.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.