Bug #18369
closed
Foreman-proxy timeout - Error: ERF12-4115 [ProxyAPI::ProxyException]
Description
Hi,
We have 4 environments -- with multiple classes inside.
It seems the problem increased since we added more classes inside the environments.
Our problem: If we add a new module to an environment -- we need first to hit import, like 3-5 times ==> till the environment changes are detected.
Can you please help us related?
Files
Updated by Slagian Momirovici over 7 years ago
- Related to Bug #17942: Timeout during Puppet class import, slow re-initialization of Puppet 3 added
Updated by Dominic Cleal over 7 years ago
Which version of Puppet is in use, and which version is specified in the smart proxy's puppet.yml configuration?
Updated by Slagian Momirovici over 7 years ago
- File environments.png environments.png added
- Subject changed from Foreman-proxy timeou - t Error: ERF12-4115 [ProxyAPI::ProxyException] to Foreman-proxy timeout - Error: ERF12-4115 [ProxyAPI::ProxyException]
I've attached also our environments for info.
thank you in advance
Updated by Slagian Momirovici over 7 years ago
our puppetmaster server: 3.8.5-5.1
in the foreman-proxy/:puppet.yaml
- Puppet version used
:puppet_version: 3.8.5
smart-proxy deployed under separate user => foreman-proxy that uses rvm
puppetmaster:/apps/deployer/foreman-proxy # su - foreman-proxy
foreman-proxy@puppetmaster:~> which puppet
/home/foreman-proxy/.rvm/gems/ruby-2.1.0/bin/puppet
foreman-proxy@puppetmaster:~> puppet --version
3.8.7
Updated by Slagian Momirovici over 7 years ago
does it affect if the gem used is 3.8.7?
Updated by Dominic Cleal over 7 years ago
- Status changed from New to Duplicate
Thanks, since it's Puppet 3 I think it's a duplicate of the issue you've already linked it to so I'm going to close it. If you believe it's a different issue for some reason, please add more info.
Updated by Slagian Momirovici over 7 years ago
Hi Dominic,
I am a little confused - where should I add this setting?
environment-class-cache-enabled ??
Updated by Dominic Cleal over 7 years ago
That's a Puppet Server 2.x (i.e. Puppet 4) setting, I don't think it's relevant to you using Puppet 3.