[Puppet Users] PSON error?
Can anyone shed any light to this error message? We're getting a number of them. Tue May 04 08:18:35 -0400 2010 ///File[/usr/local//] (err): Failed to generate additional resources using 'eval_generate': Could not intern_multiple from pson: source did not contain any PSON! Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] "Failed to retrieve current state of resource" messages
I've made no changes, so I'm assuming that it's webrick. Would this
impact that?
On Tue, Mar 23, 2010 at 8:22 PM, Christopher Johnston
wrote:
> Are you using webrick, mongrel, or passenger?
>
> Sent from my iPhone
>
> On Mar 23, 2010, at 5:32 PM, Kent Rankin wrote:
>
>> I've sent one in for this... we're running the client every 30 minutes
>> via cron, and we probably get ten reports a day (per node) just like
>> this one. It started once we went from EPEL's v0.24 to v0.25. I've
>> sent one message like this to the group, but didn't get a response.
>>
>> Tue Mar 23 12:06:43 -0400 2010 ///File[/etc/init.d/] (err):
>> Failed to retrieve current state of resource: end of file reached
>> Could not retrieve file metadata for puppet:///modules//: end
>> of file reached at /etc/puppet/modules//manifests/init.pp:45
>>
>> The stanza that it's referencing is:
>>
>> file { "/etc/init.d/":
>> owner => root,
>> group => root,
>> mode => 700,
>> source => "puppet:///modules//",
>> }
>>
>> Any ideas?
>>
>> Thanks for the help.
>>
>> -- You received this message because you are subscribed to the Google
>> Groups "Puppet Users" group.
>> To post to this group, send email to puppet-us...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] "Failed to retrieve current state of resource" messages
I've sent one in for this... we're running the client every 30 minutes
via cron, and we probably get ten reports a day (per node) just like
this one. It started once we went from EPEL's v0.24 to v0.25. I've
sent one message like this to the group, but didn't get a response.
Tue Mar 23 12:06:43 -0400 2010 ///File[/etc/init.d/] (err):
Failed to retrieve current state of resource: end of file reached
Could not retrieve file metadata for puppet:///modules//: end
of file reached at /etc/puppet/modules//manifests/init.pp:45
The stanza that it's referencing is:
file { "/etc/init.d/":
owner => root,
group => root,
mode=> 700,
source => "puppet:///modules//",
}
Any ideas?
Thanks for the help.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Tons of "configuration version" reports
I nearly forgot to write in that we removed the puppet client (EPEL) and reinstalled, and the --verbose went away. We never did figure out where it was coming from, though. Thanks for everyone's help. On Tue, Mar 9, 2010 at 5:34 PM, Todd Zullinger wrote: > Kent Rankin wrote: >> [r...@ ~]# rpm -V puppet >> S.5T c /etc/puppet/puppet.conf >> [r...@ ~]# grep verbose /etc/init.d/puppet >> [r...@ ~]# grep verbose /etc/sysconfig/puppet >> [r...@ ~]# cat /etc/sysconfig/puppet >> # The puppetmaster server >> #PUPPET_SERVER=puppet >> >> # If you wish to specify the port to connect to do so here >> #PUPPET_PORT=8140 >> >> # Where to log to. Specify syslog to send log messages to the system log. >> #PUPPET_LOG=/var/log/puppet/puppet.log >> >> # You may specify other parameters to the puppet client here >> #PUPPET_EXTRA_OPTS=--waitforcert=500 >> >> I'm not really seeing anything giving it the verbose option... >> nothing's been modified from EPEL other than the >> /etc/puppet/puppetd.conf line: >> >> report = true > > I don't know where this would be coming from then. I can't reproduce > it on a stock CentOS-5.4 system with the EPEL packages. You might > want to try running the init script via sh -x /etc/init.d/puppet start > and see if you see where it picks up the --verbose option. > > If anyone sees this with the EPEL packages, I'd be interested to know > about it. > > -- > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp > ~~ > I always wanted to be a procrastinator, never got around to it. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Failed to generate additional resources using 'eval_generate': end of file reached
We keep getting a variety of these from a random set during each Puppet run: Sat Mar 13 23:46:42 -0500 2010 //cups/File[/etc/cups] (err): Failed to generate additional resources using 'eval_generate': end of file reached It seems like there is a 30% chance of a host providing this on any given manifest that distributes files. It's only started since we went from 0.24 to 0.25 of the EPEL puppet distribution. Things "seem" to be working, but it's producing a maddening string of reports every 30 minutes. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Tons of "configuration version" reports
[r...@ ~]# rpm -V puppet S.5T c /etc/puppet/puppet.conf [r...@ ~]# grep verbose /etc/init.d/puppet [r...@ ~]# grep verbose /etc/sysconfig/puppet [r...@ ~]# cat /etc/sysconfig/puppet # The puppetmaster server #PUPPET_SERVER=puppet # If you wish to specify the port to connect to do so here #PUPPET_PORT=8140 # Where to log to. Specify syslog to send log messages to the system log. #PUPPET_LOG=/var/log/puppet/puppet.log # You may specify other parameters to the puppet client here #PUPPET_EXTRA_OPTS=--waitforcert=500 I'm not really seeing anything giving it the verbose option... nothing's been modified from EPEL other than the /etc/puppet/puppetd.conf line: report = true Thanks. On Tue, Mar 9, 2010 at 4:57 PM, Todd Zullinger wrote: > Kent Rankin wrote: >> Installed the EPEL package... it runs it as a daemon without options. >> Here's the output from ps -ef|grep puppet: >> >> root 10249 1 0 Mar08 ? 00:02:17 /usr/bin/ruby >> /usr/sbin/puppetd --verbose > > That --verbose is what's causing this I think. That's not part of the > default EPEL setup AFAIK. What is the output of rpm -V puppet ? If > /etc/sysconfig/puppet is modified, check if verbose is added to the > puppet options there. > > Also check in /etc/puppet/puppet.conf for verbose = true (though that > wouldn't manifest itself in the command line options). > > -- > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp > ~~ > The chains of habit are too weak to be felt until they are too strong > to be broken > -- Samuel Johnson (1709-1784) > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Tons of "configuration version" reports
Installed the EPEL package... it runs it as a daemon without options. Here's the output from ps -ef|grep puppet: root 10249 1 0 Mar08 ?00:02:17 /usr/bin/ruby /usr/sbin/puppetd --verbose Thanks. On Tue, Mar 9, 2010 at 4:07 PM, Todd Zullinger wrote: > I wrote: >> James Turnbull wrote: >>> Do you get a report each time without a value specified in >>> config_version? >> >> Yes. With config_version commented out in puppet.conf, I get a report >> using the timestamp even if nothing has changed. With a command set >> for config_version, I also get a report when nothing has changed. > > Though perhaps I should have tested more patiently. That was with > puppetd -t, which implies --verbose. Waiting for a normal puppet run > or using the equivalent options to --test, less --verbose, e.g.: > > puppetd --onetime --ignorecache --no-daemonize --no-usecacheonfailure > > I don't get a report in either case when nothing changes. > > Sorry for the false report. > > Ken, are you running puppet as a daemon or via cron? Is the verbose > option set in your configuration or on the command line? > > -- > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp > ~~ > Let us think the unthinkable, let us do the undoable. Let us prepare > to grapple with the ineffable itself, and see if we may not eff it > after all. > -- Douglas Adams > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Tons of "configuration version" reports
When is 0.25.5 scheduled to be fixed? If it's not very soon, we're going to have to jump on the CFEngine bandwagon. Thanks. On Tue, Mar 9, 2010 at 3:04 PM, James Turnbull wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/03/10 3:40 AM, R.I.Pienaar wrote: >> >> - "Kent Rankin" wrote: >> >>> This started about three days after I upgraded to 0.25 on EPEL. That >>> time delay confused me a great deal. >>> >>> Is this the standard behavior on 0.25? Is there a configuration >>> option to have it only show when changes are made? >>> >> >> There's a configuration option, its broken. >> >> The feature in 25 lets you tag a manifest with a version and the version is >> supposed to show up in reports and logs and so forth. you can specify a >> different way than the default (current timestamp) with config_version >> option on the master but its broken. You'd want to make it log your SVN >> revision for example >> >> alas its broken and the ticket is unloved. >> > > Now, now http://projects.reductivelabs.com/issues/3043 isn't > unloved :) > > It's assigned to the next stable release - 0.25.5. I've even now > assigned it to an actual person - who may mind you tell me to sod > off - but it's on track to be fixed. > > James > > - -- > Author of: > * Pro Linux System Administration (http://tinyurl.com/linuxadmin) > * Pulling Strings with Puppet (http://tinyurl.com/pupbook) > * Pro Nagios 2.0 (http://tinyurl.com/pronagios) > * Hardening Linux (http://tinyurl.com/hardeninglinux) > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEVAwUBS5ap2SFa/lDkFHAyAQKDgQgA5XHiWPi3gE5/DF75Qf5QxWy6fVex8T6T > UWUGd5OzJ9xTrshKHktZl/ZGK+dL1lmz0oCvFp05lJwy9C1fI6vtBryCM35ZwZOI > UUP/Q4+Ud5Am4so12EXG9cAY+B0CP2mLWPCglqJ0uMBrrHw0/uAt4RdFrz0uLOhT > hlrHe2nGejivYffLeM0zJvyOAOc6j1UjXZmTHHXXzasNdSPqom/KlB4ukfNsioUE > yM8zZ9xyHJBWgtQoUXiA0kvuoY5wdIPPkuhjvRpicr9ersoLYhqGxxtIuTFFq98c > LjovLS2S3Z01fMNemzq7gscpyj8fJx37q8NC0DEkiP9PrEEZahMZ1A== > =hxpH > -END PGP SIGNATURE- > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Tons of "configuration version" reports
Here's what I'm seeing in syslog: Mar 9 12:23:52 puppetd[10249]: Caching catalog for Mar 9 12:23:52 puppetd[10249]: Applying configuration version '1268079838' Mar 9 12:23:56 puppetd[10249]: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (marshal) Mar 9 12:23:57 puppetd[10249]: Reporting failed: end of file reached Mar 9 12:23:57 puppetd[10249]: Finished catalog run in 4.60 seconds Mar 9 12:53:57 puppetd[10249]: Caching catalog for Here's the emailed report: Tue Mar 09 13:24:03 -0500 2010 Puppet (info): Applying configuration version '1268079838' The emailed report comes in every 30 minutes, just like that, without making any changes on the client. This doesn't seem like how it should function. Thanks for your help. On Tue, Mar 9, 2010 at 1:36 PM, R.I.Pienaar wrote: > hello, > > - "Kent Rankin" wrote: > >> Just a question, though... I'm getting that report on *EVERY* run, >> and by that, I mean to say that no changes have been made. It's just >> throwing the same version over and over again. >> > > with report do you mean a log in syslog? Every run is a new compiled > catalog, and by default the 'version' of that compiled catelog is compile > time. > >> Is that normal? > > it's default yes, had the config option worked you could have made a static > thing - it will still log that line though the line just wont change between > runs till your manifests change. This is assuming you're just talking about > the syslog lines here > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Tons of "configuration version" reports
Just a question, though... I'm getting that report on *EVERY* run, and by that, I mean to say that no changes have been made. It's just throwing the same version over and over again. Is that normal? Thanks. On Tue, Mar 9, 2010 at 11:40 AM, R.I.Pienaar wrote: > > ----- "Kent Rankin" wrote: > >> This started about three days after I upgraded to 0.25 on EPEL. That >> time delay confused me a great deal. >> >> Is this the standard behavior on 0.25? Is there a configuration >> option to have it only show when changes are made? >> > > There's a configuration option, its broken. > > The feature in 25 lets you tag a manifest with a version and the version is > supposed to show up in reports and logs and so forth. you can specify a > different way than the default (current timestamp) with config_version option > on the master but its broken. You'd want to make it log your SVN revision > for example > > alas its broken and the ticket is unloved. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Tons of "configuration version" reports
This started about three days after I upgraded to 0.25 on EPEL. That time delay confused me a great deal. Is this the standard behavior on 0.25? Is there a configuration option to have it only show when changes are made? Thanks. On Tue, Mar 9, 2010 at 10:01 AM, Michael DeHaan wrote: > On Tue, Mar 9, 2010 at 2:03 AM, Kent Rankin wrote: >> Now, even though no changes have occurred, I'm getting a report like >> this every time it runs: >> >> Tue Mar 09 00:51:25 -0500 2010 Puppet (info): Applying configuration >> version '1268079838' >> >> What am I to do? >> >> >> Thanks. >> > > Are you saying this is new behavior with the reports (judging from the > "now"?) where before it would only report if something changed? > > I know lots of folks will run tmpwatch against the report directory, > but I would generally agree a no-change report should probably > not fill up the directory... though I would also like to know that the > run happened. Complicated :) > > It's come up before that we should keep trending data (last run, when > run, changes made) seperate from some of the detailed information > so that when reports are cleaned up we don't have to get rid of all of > that data. > > --Michael > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Tons of "configuration version" reports
Now, even though no changes have occurred, I'm getting a report like this every time it runs: Tue Mar 09 00:51:25 -0500 2010 Puppet (info): Applying configuration version '1268079838' What am I to do? Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
