Nasty.

[Paul Seymour]

Hello,

Just updated to 3.6.0 and a strange thing is happening (might not be related to 3.6 specifically just testing before making the jump from 2.7 for real).

I have a puppet master running under Apache/Passenger and when testing a client this happens:-

$ puppet agent -t --no-daemonize --noop

Info: Retrieving pluginfacts

Info: Retrieving plugin

Notice: /File[/var/lib/puppet/lib/puppet]/ensure: removed

Notice: /File[/var/lib/puppet/lib/facter]/ensure: removed

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class <CLASS> for ....

Warning: Not using cache on failed catalog

Error: Could not retrieve catalog; skipping run

However if I shutdown the master and run it under a shell with "--debug --no-daemonize" everything is fine and clients (re-download) the facts/plugins

and get a catalog etc.

I am a bit mystified about this, and ideas ?

Thanks

Paul

[Joaquin Menchaca]

My guess.  Incompatible underlying ruby version.

[Kylo Ginsberg]

Kind of a guess, but this *may* be https://tickets.puppetlabs.com/browse/PUP-2610, which is a rack-specific bug we stumbled across yesterday. If so, you *may* be able to workaround it by setting environment_timeout = 0 (for details on that settings see http://docs.puppetlabs.com/puppet/latest/reference/environments.html#tuning-environment-caching).

So that's a conjecture on top of a conjecture, but if you don't mind experimenting, you could see if that setting makes any difference.

Thanks,

Kylo

--

Kylo Ginsberg

ky...@puppetlabs.com

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://puppetconf.com 

Register by May 30th to take advantage of the Early Adopter discount —save $349!

[Paul Seymour]

However if I shutdown the master and run it under a shell with "--debug --no-daemonize" everything is fine and clients (re-download) the facts/plugins

and get a catalog etc.

I am a bit mystified about this, and ideas ?

Kind of a guess, but this *may* be https://tickets.puppetlabs.com/browse/PUP-2610, which is a rack-specific bug we stumbled across yesterday. If so, you *may* be able to workaround it by setting environment_timeout = 0 (for details on that settings see http://docs.puppetlabs.com/puppet/latest/reference/environments.html#tuning-environment-caching).

So that's a conjecture on top of a conjecture, but if you don't mind experimenting, you could see if that setting makes any difference.

 

Thanks,

Kylo

That appears to have worked around that particular issue. Many thanks for the tips. 

[Kylo Ginsberg]

On Mon, May 19, 2014 at 2:09 AM, Paul Seymour <paul.s...@ig.com> wrote:

However if I shutdown the master and run it under a shell with "--debug --no-daemonize" everything is fine and clients (re-download) the facts/plugins

and get a catalog etc.

I am a bit mystified about this, and ideas ?

Kind of a guess, but this *may* be https://tickets.puppetlabs.com/browse/PUP-2610, which is a rack-specific bug we stumbled across yesterday. If so, you *may* be able to workaround it by setting environment_timeout = 0 (for details on that settings see http://docs.puppetlabs.com/puppet/latest/reference/environments.html#tuning-environment-caching).

So that's a conjecture on top of a conjecture, but if you don't mind experimenting, you could see if that setting makes any difference.

That appears to have worked around that particular issue. Many thanks for the tips. 

Cool, glad that worked. Just to reiterate for posterity: that is definitely a *workaround* and should not be needed in 3.6.1+.

Thanks for trying that out!

Kylo