Abnormaliti
2007-Mar-26 00:34 UTC
"Could not run Puppet::Network::Client::Master" after 0.22.2 upgrade
After upgrading my puppetmaster server to 0.22.2 using David''s src
RPM''s
for RHEL4 rebuilt for x86_64 i am getting the following error when puppetd
attempts a configuration run.
Mon Mar 26 10:05:43 EST 2007 Puppet (err): Could not run
Puppet::[1]Network::Client::Master: Invalid value ''nil''
for noop
When puppetd is started the initial run is successful but any subsequent
runs produce this error.
Other clients have been upgraded with the same RPMs and are running
perfectly.
Running
puppetd --debug
only produces the following when sent a USR1 after the first successful
run
notice: Caught USR1; triggering client run
debug: Loaded state in 0.19 seconds
info: Loading fact home
info: Loading fact vmware
info: Loading fact network
err: Could not run Puppet::[2]Network::Client::Master: Invalid value
''nil'' for noop
Any idea where to start looking?
Ben
References
Visible links
1. network::Client::Master:
2. network::Client::Master:
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Luke Kanies
2007-Mar-26 16:14 UTC
Re: "Could not run Puppet::Network::Client::Master" after 0.22.2 upgrade
On Mar 25, 2007, at 7:34 PM, Abnormaliti wrote:> After upgrading my puppetmaster server to 0.22.2 using David''s src > RPM''s for RHEL4 rebuilt for x86_64 i am getting the following error > when puppetd attempts a configuration run. > Mon Mar 26 10:05:43 EST 2007 Puppet (err): Could not run > Puppet::Network::Client::Master: Invalid value ''nil'' for noop > When puppetd is started the initial run is successful but any > subsequent runs produce this error. > > Other clients have been upgraded with the same RPMs and are running > perfectly. > > Running > puppetd --debug > only produces the following when sent a USR1 after the first > successful run > notice: Caught USR1; triggering client run > debug: Loaded state in 0.19 seconds > info: Loading fact home > info: Loading fact vmware > info: Loading fact network > err: Could not run Puppet::Network::Client::Master: Invalid value > ''nil'' for noop > Any idea where to start looking?Can you run that with --trace enabled, so I can get a stack trace? It looks like you''ve got ''nil'' in your configuration somewhere, which shouldn''t be possible. -- Once...in the wilds of Afghanistan, I lost my corkscrew, and we were forced to live on nothing but food and water for days. -- W. C. Fields --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Abnormaliti
2007-Mar-26 23:26 UTC
Re: "Could not run Puppet::Network::Client::Master" after 0.22.2 upgrade
Luke Kanies wrote:
On Mar 25, 2007, at 7:34 PM, Abnormaliti wrote:
After upgrading my puppetmaster server to 0.22.2 using David''s src
RPM''s for RHEL4 rebuilt for x86_64 i am getting the following error
when puppetd attempts a configuration run.
Mon Mar 26 10:05:43 EST 2007 Puppet (err): Could not run
Puppet::[1]Network::Client::Master: Invalid value ''nil'' for
noop
When puppetd is started the initial run is successful but any
subsequent runs produce this error.
Other clients have been upgraded with the same RPMs and are running
perfectly.
Running
puppetd --debug
only produces the following when sent a USR1 after the first
successful run
notice: Caught USR1; triggering client run
debug: Loaded state in 0.19 seconds
info: Loading fact home
info: Loading fact vmware
info: Loading fact network
err: Could not run Puppet::[2]Network::Client::Master: Invalid value
''nil'' for noop
Any idea where to start looking?
Can you run that with --trace enabled, so I can get a stack trace?
It looks like you''ve got ''nil'' in your configuration
somewhere, which
shouldn''t be possible.
--
Once...in the wilds of Afghanistan, I lost my corkscrew, and we were
forced to live on nothing but food and water for days. -- W. C.
Fields
---------------------------------------------------------------------
Luke Kanies | [3]http://reductivelabs.com | [4]http://madstop.com
_______________________________________________
Puppet-users mailing list
[5]Puppet-users@madstop.com
[6]https://mail.madstop.com/mailman/listinfo/puppet-users
Thanks for your help.
notice: Finished configuration run in 21.89 seconds
notice: Caught USR1; triggering client run
debug: Loaded state in 0.08 seconds
info: Loading fact home
info: Loading fact vmware
info: Loading fact network
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:960:in `munge''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:833:in `value=''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:47:in `[]=''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `synchronize''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `[]=''
/usr/lib64/site_ruby/1.8/puppet.rb:89:in `[]=''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:401:in
`download''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:413:in
`getfacts''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:23:in
`facts''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:173:in
`getconfig''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:298:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:297:in
`thinmark''
/usr/lib64/site_ruby/1.8/puppet/util.rb:396:in `measure''
/usr/lib64/ruby/1.8/benchmark.rb:342:in `realtime''
/usr/lib64/site_ruby/1.8/puppet/util.rb:396:in `thinmark''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:299:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:291:in
`synchronize''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:291:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client.rb:119:in `runnow''
/usr/lib64/site_ruby/1.8/puppet.rb:225:in `settraps''
/usr/lib64/site_ruby/1.8/puppet.rb:218:in `each''
/usr/lib64/site_ruby/1.8/puppet.rb:218:in `settraps''
/usr/lib64/site_ruby/1.8/puppet.rb:215:in `call''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:123:in
`select''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:123:in
`select''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:112:in
`iterate''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:103:in
`run''
/usr/lib64/site_ruby/1.8/puppet.rb:323:in `start''
/usr/sbin/puppetd:443
err: Could not run Puppet::[7]Network::Client::Master: Invalid value
''nil'' for noop
References
Visible links
1. network::Client::Master:
2. network::Client::Master:
3. http://reductivelabs.com/
4. http://madstop.com/
5. mailto:Puppet-users@madstop.com
6. https://mail.madstop.com/mailman/listinfo/puppet-users
7. network::Client::Master:
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Luke Kanies
2007-Mar-27 17:40 UTC
Re: "Could not run Puppet::Network::Client::Master" after 0.22.2 upgrade
On Mar 26, 2007, at 6:26 PM, Abnormaliti wrote:> Thanks for your help. > > notice: Finished configuration run in 21.89 seconds > notice: Caught USR1; triggering client run > debug: Loaded state in 0.08 seconds > info: Loading fact home > info: Loading fact vmware > info: Loading fact network > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:960:in `munge'' > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:833:in `value='' > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:47:in `[]='' > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `synchronize'' > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `[]='' > /usr/lib64/site_ruby/1.8/puppet.rb:89:in `[]='' > /usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:401:in > `download'' > /usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:413:in > `getfacts''Thanks. That points me to where it is. -- Ninety-eight percent of the adults in this country are decent, hard-working, honest Americans. It''s the other lousy two percent that get all the publicity. But then--we elected them. --Lily Tomlin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Luke Kanies
2007-Mar-27 22:17 UTC
Re: "Could not run Puppet::Network::Client::Master" after 0.22.2 upgrade
On Mar 26, 2007, at 6:26 PM, Abnormaliti wrote:> Thanks for your help. > > notice: Finished configuration run in 21.89 seconds > notice: Caught USR1; triggering client run > debug: Loaded state in 0.08 seconds > info: Loading fact home > info: Loading fact vmware > info: Loading fact network > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:960:in `munge'' > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:833:in `value='' > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:47:in `[]='' > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `synchronize'' > /usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `[]='' > /usr/lib64/site_ruby/1.8/puppet.rb:89:in `[]='' > /usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:401:in > `download'' > /usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:413:in > `getfacts''I can''t imagine how this happened, but I added an explicit check to make sure I set it to ''false'' if somehow the value is ''nil''. -- Tobacco stocks have taken a big tumble," says Jay Leno. "Phillip Morris fell 6 points. They lost so much money they may have to lay off two senators." --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Abnormaliti
2007-Mar-30 00:20 UTC
Re: "Could not run Puppet::Network::Client::Master" after 0.22.2 upgrade
Luke Kanies wrote:
On Mar 26, 2007, at 6:26 PM, Abnormaliti wrote:
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:960:in `munge''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:833:in `value=''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:47:in `[]=''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `synchronize''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `[]=''
/usr/lib64/site_ruby/1.8/puppet.rb:89:in `[]=''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:401:in
`download''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:413:in
`getfacts''
I can''t imagine how this happened, but I added an explicit check to
make sure I set it to ''false'' if somehow the value is
''nil''.
Luke,
Thankyou for your prompt response but after updating puppetmaster and
puppet to 0.22.3 i now get the following error from the trace on that same
system, other clients work fine after the update.
notice: Caught USR1; triggering client run
debug: Loaded state in 0.09 seconds
info: Loading fact home
info: Loading fact vmware
info: Loading fact network
/usr/lib64/site_ruby/1.8/puppet/metatype/closure.rb:77:in `merge''
/usr/lib64/site_ruby/1.8/puppet/metatype/closure.rb:65:in `each''
/usr/lib64/site_ruby/1.8/puppet/transportable.rb:22:in `each''
/usr/lib64/site_ruby/1.8/puppet/transportable.rb:22:in `each''
/usr/lib64/site_ruby/1.8/puppet/metatype/closure.rb:65:in `merge''
/usr/lib64/site_ruby/1.8/puppet/metatype/instances.rb:148:in
`create''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:368:in
`download''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:419:in
`getfacts''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:23:in
`facts''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:173:in
`getconfig''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:298:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:297:in
`thinmark''
/usr/lib64/site_ruby/1.8/puppet/util.rb:396:in `measure''
/usr/lib64/ruby/1.8/benchmark.rb:342:in `realtime''
/usr/lib64/site_ruby/1.8/puppet/util.rb:396:in `thinmark''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:299:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:291:in
`synchronize''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:291:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client.rb:119:in `runnow''
/usr/lib64/site_ruby/1.8/puppet.rb:225:in `settraps''
/usr/lib64/site_ruby/1.8/puppet.rb:218:in `each''
/usr/lib64/site_ruby/1.8/puppet.rb:218:in `settraps''
/usr/lib64/site_ruby/1.8/puppet.rb:215:in `call''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:123:in
`select''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:123:in
`select''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:112:in
`iterate''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:103:in
`run''
/usr/lib64/site_ruby/1.8/puppet.rb:323:in `start''
/usr/sbin/puppetd:443
err: Could not run Puppet::[1]Network::Client::Master: undefined method
`shouldorig'' for Parameter(ignore = nil, @parent
File[/var/lib/puppet/facts]):Puppet::Type::File::ParameterIgnore
Any ideas?
Ben
References
Visible links
1. network::Client::Master:
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Abnormaliti
2007-Mar-30 05:33 UTC
Re: "Could not run Puppet::Network::Client::Master" after 0.22.2 upgrade
Abnormaliti wrote:
Luke Kanies wrote:
On Mar 26, 2007, at 6:26 PM, Abnormaliti wrote:
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:960:in `munge''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:833:in `value=''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:47:in `[]=''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `synchronize''
/usr/lib64/site_ruby/1.8/puppet/util/config.rb:38:in `[]=''
/usr/lib64/site_ruby/1.8/puppet.rb:89:in `[]=''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:401:in
`download''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:413:in
`getfacts''
I can''t imagine how this happened, but I added an explicit check to
make sure I set it to ''false'' if somehow the value is
''nil''.
Luke,
Thankyou for your prompt response but after updating puppetmaster and
puppet to 0.22.3 i now get the following error from the trace on that
same system, other clients work fine after the update.
notice: Caught USR1; triggering client run
debug: Loaded state in 0.09 seconds
info: Loading fact home
info: Loading fact vmware
info: Loading fact network
/usr/lib64/site_ruby/1.8/puppet/metatype/closure.rb:77:in
`merge''
/usr/lib64/site_ruby/1.8/puppet/metatype/closure.rb:65:in `each''
/usr/lib64/site_ruby/1.8/puppet/transportable.rb:22:in `each''
/usr/lib64/site_ruby/1.8/puppet/transportable.rb:22:in `each''
/usr/lib64/site_ruby/1.8/puppet/metatype/closure.rb:65:in
`merge''
/usr/lib64/site_ruby/1.8/puppet/metatype/instances.rb:148:in
`create''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:368:in
`download''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:419:in
`getfacts''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:23:in
`facts''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:173:in
`getconfig''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:298:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:297:in
`thinmark''
/usr/lib64/site_ruby/1.8/puppet/util.rb:396:in `measure''
/usr/lib64/ruby/1.8/benchmark.rb:342:in `realtime''
/usr/lib64/site_ruby/1.8/puppet/util.rb:396:in `thinmark''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:299:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:291:in
`synchronize''
/usr/lib64/site_ruby/1.8/puppet/network/client/master.rb:291:in
`run''
/usr/lib64/site_ruby/1.8/puppet/network/client.rb:119:in
`runnow''
/usr/lib64/site_ruby/1.8/puppet.rb:225:in `settraps''
/usr/lib64/site_ruby/1.8/puppet.rb:218:in `each''
/usr/lib64/site_ruby/1.8/puppet.rb:218:in `settraps''
/usr/lib64/site_ruby/1.8/puppet.rb:215:in `call''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:123:in
`select''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:123:in
`select''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:112:in
`iterate''
/usr/lib64/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:103:in
`run''
/usr/lib64/site_ruby/1.8/puppet.rb:323:in `start''
/usr/sbin/puppetd:443
err: Could not run Puppet::[1]Network::Client::Master: undefined
method `shouldorig'' for Parameter(ignore = nil, @parent
File[/var/lib/puppet/facts]):Puppet::Type::File::ParameterIgnore
I was able to workaround the problem by commenting out the following from
the servers manifest.
file { "/var/lib/puppet/facts":
loglevel => "debug",
backup => "false"
}
This manifest has not changed since 0.22.1, so changes in 0.22.2 have
introduced this bug?
Ben.
References
Visible links
1. network::Client::Master:
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Luke Kanies
2007-Mar-30 21:03 UTC
Re: "Could not run Puppet::Network::Client::Master" after 0.22.2 upgrade
On Mar 30, 2007, at 12:33 AM, Abnormaliti wrote:> I was able to workaround the problem by commenting out the > following from the servers manifest. > > file { "/var/lib/puppet/facts": > loglevel => "debug", > backup => "false" > } > > This manifest has not changed since 0.22.1, so changes in 0.22.2 > have introduced this bug?Seems possible, but Puppet manages that directory for you, so you shouldn''t need to. That doesn''t explain the bug, but at least it makes it go away. I''m planning on refactoring this part of the system anyway, but I''ll see if I can figure it out. -- Criminal: A person with predatory instincts who has not sufficient capital to form a corporation. --Howard Scott --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com