Ask Your Question
1

Attempted to pop --> no 'environments' in

asked 2014-05-27 10:22:38 -0500

updated 2014-05-27 10:43:46 -0500

I'm using the puppet, puppet-common, puppetmaster and puppetmaster-common (all version 3.6.1-1puppetlabs1 , released this month) packages from http://apt.puppetlabs.com on Ubuntu Precise.

Since the upgrade I'm getting a failure which stops puppet from serving and giving clients an "Error 400 on SERVER".

All runs fine for a few minutes, until in the logs I see:

May 27 10:34:28 kernhem puppet-master[19006]: Attempted to pop, but already at root of the context stack.

May 27 10:34:28 kernhem puppet-master[19006]: no 'environments' in {:root_environment=>#<Puppet::Node::Environment:0x7fd86413eb80 @manifest="/", @modulepath=[], @watching=true, @config_version=nil, @name=:"*root*">, :current_environment=>#<Puppet::Node::Environment:0x7fd86413eb80 @manifest="/", @modulepath=[], @watching=true, @config_version=nil, @name=:"*root*">} at top of [[0, nil, nil]]

May 27 10:35:01  puppet-master[19006]: last message repeated 46 times

(and so-on -- all requests cause this error to come up rather than puppet doing its work).

Any suggestions, beyond downgrading and sticking with the previous version? I downgraded to 3.6.0-1puppetlabs1 for the time being.

edit retag flag offensive close merge delete

Comments

I'm facing the same problem. I was changing my modules to a directory environment config. While troubleshooting, I've discovered the issue starts when two or more clients access the puppet master at one time. If any hit it alone, it works. Once two hit at the same time, it fails and stays failed.

8None1 gravatar image8None1 ( 2014-05-27 16:19:33 -0500 )edit

IT also breaks in spectacular fashion if you are not using any explicit environments, which is the default. and works just fine if you have a small deployment you are managing. no need for the added complexity of environments. but alas, looks like those days are over. set environment explicitly to "production" (which according to puppetlabs docs should be a no-op) and then also disabled deprecation warnings as I was REALLY tired of the noise when trying to see if puppet had started working again. I am now hoping thr duck tape has fixed it for now.

strobert gravatar imagestrobert ( 2014-06-15 18:26:55 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
2

answered 2014-05-27 16:38:39 -0500

8None1 gravatar image

This is a bug in Webrick's concurrency. Being tracked at https://tickets.puppetlabs.com/browse...

edit flag offensive delete link more
0

answered 2014-05-27 10:48:40 -0500

On puppet 3.6.0 updated any use of the modulepath, manifest, and config_version settings in puppet.conf is deprecated. This also means that using no environments is deprecated , you can check this out on release notes.

http://docs.puppetlabs.com/puppet/3.6...

and here is how to enable directory environments.

http://docs.puppetlabs.com/puppet/3.6...

edit flag offensive delete link more

Comments

I am getting the same error message with 3.6.1 on RHEL 6.5. At your suggestion, I moved to an environments setting and have the same problem. Immediately after restarting the puppet master service, it works for every node. Shortly afterwards, every client gets the same environment errors.

diastelo gravatar imagediastelo ( 2014-05-27 12:51:48 -0500 )edit

Are you using same module to manager puppet? if yes try pass the parameter environment to specify one to the nodes and check if the directory environments configurations still on master.

Renan Vicente gravatar imageRenan Vicente ( 2014-05-27 15:03:55 -0500 )edit

It's happening to me too. "Attempted to pop, but already at root of the context stack.". I have to say I am surprised by the level of brokenness that appear in supposedly "minor" releases. Can't imagine what this must be like in real production environments...or do they never upgrade?

sguiggly gravatar imagesguiggly ( 2014-05-27 23:21:36 -0500 )edit

Oh we upgrade. And this hurts.

8None1 gravatar image8None1 ( 2014-05-28 16:05:12 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

2 followers

Stats

Asked: 2014-05-27 10:22:38 -0500

Seen: 803 times

Last updated: May 27 '14