These PSON messages are driving me crazy. It''s not unusual to have to
restart the client 3 times to get past it. Anyone know the cause? This is a
fresh install of the puppetmaster and puppet client on CentOS 5.5 with
puppet 2.6.4.
Apr 1 17:04:14 rcss01 puppet-agent[1058]: Reopening log filesApr 1
17:04:15 rcss01 puppet-agent[1058]: Starting Puppet client version 2.6.4
Apr 1 17:04:16 rcss01 puppet-agent[1058]: Could not retrieve catalog from
remote server: Could not intern from pson: source did not contain any PSON!
Apr 1 17:04:16 rcss01 puppet-agent[1058]: Not using cache on failed catalog
Apr 1 17:04:16 rcss01 puppet-agent[1058]: Could not retrieve catalog;
skipping runApr 1 17:05:15 rcss01 puppet-agent[1058]: Caught TERM; calling
stop
Apr 1 17:05:15 rcss01 puppet-agent[1230]: Reopening log files
Apr 1 17:05:16 rcss01 puppet-agent[1230]: Starting Puppet client version
2.6.4Apr 1 17:05:17 rcss01 puppet-agent[1230]: Could not retrieve catalog
from remote server: Could not intern from pson: source did not contain any
PSON!
Apr 1 17:05:17 rcss01 puppet-agent[1230]: Not using cache on failed catalog
Apr 1 17:05:17 rcss01 puppet-agent[1230]: Could not retrieve catalog;
skipping run
Apr 1 17:05:19 rcss01 puppet-agent[1230]: Caught TERM; calling stopApr 1
17:05:20 rcss01 puppet-agent[1352]: Reopening log files
Apr 1 17:05:20 rcss01 puppet-agent[1352]: Starting Puppet client version
2.6.4Apr 1 17:05:21 rcss01 puppet-agent[1352]: Could not retrieve catalog
from remote server: Could not intern from pson: source did not contain any
PSON!
Apr 1 17:05:21 rcss01 puppet-agent[1352]: Not using cache on failed
catalogApr 1 17:05:21 rcss01 puppet-agent[1352]: Could not retrieve
catalog; skipping run
Apr 1 17:05:24 rcss01 puppet-agent[1352]: Caught TERM; calling stopApr 1
17:05:24 rcss01 puppet-agent[1474]: Reopening log files
Apr 1 17:05:25 rcss01 puppet-agent[1474]: Starting Puppet client version
2.6.4
Apr 1 17:05:26 rcss01 puppet-agent[1474]: Could not retrieve catalog from
remote server: Could not intern from pson: source did not contain any PSON!
Apr 1 17:05:26 rcss01 puppet-agent[1474]: Not using cache on failed catalog
Apr 1 17:05:26 rcss01 puppet-agent[1474]: Could not retrieve catalog;
skipping run
Apr 1 17:05:28 rcss01 puppet-agent[1474]: Caught TERM; calling stop
Apr 1 17:05:29 rcss01 puppet-agent[1596]: Reopening log files
And finally, on the FOURTH attempt!
Apr 1 17:05:29 rcss01 puppet-agent[1596]: Starting Puppet client version
2.6.4
Apr 1 17:05:33 rcss01 puppet-agent[1596]:
(/Stage[network]/Network::Base/Network::Resolv_conf[resolv.conf]/File[/etc/resolv.conf]/content)
content changed ''{md5}bf562bbe04aeff07447f98e3775f3bd9'' to
''{md5}1401f263a98e43d48ed8bfa972ffa87d''
Doug.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
For what its worth, we are running into these PSON errors numerous times as well - preparing for our first puppet rollout and causing some questions internally. Running fresh install 2.6.4 on RHEL 5.5 - would love to help see this debugged. Vince On Fri, Apr 1, 2011 at 11:07 AM, Douglas Garstang <doug.garstang@gmail.com> wrote:> These PSON messages are driving me crazy. It''s not unusual to have to > restart the client 3 times to get past it. Anyone know the cause? This is a > fresh install of the puppetmaster and puppet client on CentOS 5.5 with > puppet 2.6.4. > Apr 1 17:04:14 rcss01 puppet-agent[1058]: Reopening log filesApr 1 > 17:04:15 rcss01 puppet-agent[1058]: Starting Puppet client version 2.6.4 > Apr 1 17:04:16 rcss01 puppet-agent[1058]: Could not retrieve catalog from > remote server: Could not intern from pson: source did not contain any PSON! > Apr 1 17:04:16 rcss01 puppet-agent[1058]: Not using cache on failed catalog > Apr 1 17:04:16 rcss01 puppet-agent[1058]: Could not retrieve catalog; > skipping runApr 1 17:05:15 rcss01 puppet-agent[1058]: Caught TERM; calling > stop > Apr 1 17:05:15 rcss01 puppet-agent[1230]: Reopening log files > Apr 1 17:05:16 rcss01 puppet-agent[1230]: Starting Puppet client version > 2.6.4Apr 1 17:05:17 rcss01 puppet-agent[1230]: Could not retrieve catalog > from remote server: Could not intern from pson: source did not contain any > PSON! > Apr 1 17:05:17 rcss01 puppet-agent[1230]: Not using cache on failed catalog > Apr 1 17:05:17 rcss01 puppet-agent[1230]: Could not retrieve catalog; > skipping run > Apr 1 17:05:19 rcss01 puppet-agent[1230]: Caught TERM; calling stopApr 1 > 17:05:20 rcss01 puppet-agent[1352]: Reopening log files > Apr 1 17:05:20 rcss01 puppet-agent[1352]: Starting Puppet client version > 2.6.4Apr 1 17:05:21 rcss01 puppet-agent[1352]: Could not retrieve catalog > from remote server: Could not intern from pson: source did not contain any > PSON! > Apr 1 17:05:21 rcss01 puppet-agent[1352]: Not using cache on failed > catalogApr 1 17:05:21 rcss01 puppet-agent[1352]: Could not retrieve > catalog; skipping run > Apr 1 17:05:24 rcss01 puppet-agent[1352]: Caught TERM; calling stopApr 1 > 17:05:24 rcss01 puppet-agent[1474]: Reopening log files > Apr 1 17:05:25 rcss01 puppet-agent[1474]: Starting Puppet client version > 2.6.4 > Apr 1 17:05:26 rcss01 puppet-agent[1474]: Could not retrieve catalog from > remote server: Could not intern from pson: source did not contain any PSON! > Apr 1 17:05:26 rcss01 puppet-agent[1474]: Not using cache on failed catalog > Apr 1 17:05:26 rcss01 puppet-agent[1474]: Could not retrieve catalog; > skipping run > Apr 1 17:05:28 rcss01 puppet-agent[1474]: Caught TERM; calling stop > Apr 1 17:05:29 rcss01 puppet-agent[1596]: Reopening log files > And finally, on the FOURTH attempt! > Apr 1 17:05:29 rcss01 puppet-agent[1596]: Starting Puppet client version > 2.6.4 > Apr 1 17:05:33 rcss01 puppet-agent[1596]: > (/Stage[network]/Network::Base/Network::Resolv_conf[resolv.conf]/File[/etc/resolv.conf]/content) > content changed ''{md5}bf562bbe04aeff07447f98e3775f3bd9'' to > ''{md5}1401f263a98e43d48ed8bfa972ffa87d'' > Doug. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> > On Fri, Apr 1, 2011 at 11:07 AM, Douglas Garstang > <doug.garstang@gmail.com> wrote: > > These PSON messages are driving me crazy. It''s not unusual to have to > > restart the client 3 times to get past it. Anyone know the cause? This is > a > > fresh install of the puppetmaster and puppet client on CentOS 5.5 with > > puppet 2.6.4. >I ran puppetmaster with WEBrick managing 300 servers with a 10 minute update interval for months, then last month I began to get these errors very often. I got crazy by this, and actually it was the "push" for implementing nginx+passenger instead of WEBrick. So this week I implemented it and got it working (with a minor drawback which I posted earlier this week on this list). It consumes much less CPU and memory, it''s faster and those errors are gone now. I don''t really know what caused this errors, but I recommend this solution! It''s a bit more work, but it''s worth! -- []''s Hugo www.devin.com.br -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Apr 1, 2011 at 4:24 PM, Hugo Cisneiros (Eitch) < hugo.cisneiros@gmail.com> wrote:> On Fri, Apr 1, 2011 at 11:07 AM, Douglas Garstang >> <doug.garstang@gmail.com> wrote: >> > These PSON messages are driving me crazy. It''s not unusual to have to >> > restart the client 3 times to get past it. Anyone know the cause? This >> is a >> > fresh install of the puppetmaster and puppet client on CentOS 5.5 with >> > puppet 2.6.4. >> > > I ran puppetmaster with WEBrick managing 300 servers with a 10 minute > update interval for months, then last month I began to get these errors very > often. > > I got crazy by this, and actually it was the "push" for implementing > nginx+passenger instead of WEBrick. So this week I implemented it and got it > working (with a minor drawback which I posted earlier this week on this > list). It consumes much less CPU and memory, it''s faster and those errors > are gone now. > > >Ah, Ok. I was using passenger once as well, but wasn''t able to implement it a second time. To get passenger to work with puppet, you need to have exactly the right combination of packages/RPM''s available. To know the exact version combination of these packages, you need to wave a dead chicken around a midnight, while dressed in a pink tu-tu. It''s good to know it''s not just me. It would be nice to see the puppet gods weigh on on this. They''ve been silent about it so far, and a few of us have been asking about it in the mailing list for quite some time now. Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sat, Apr 2, 2011 at 11:13 AM, Douglas Garstang <doug.garstang@gmail.com> wrote:> Ah, Ok. I was using passenger once as well, but wasn''t able to implement it > a second time. To get passenger to work with puppet, you need to have > exactly the right combination of packages/RPM''s available. To know the exact > version combination of these packages, you need to wave a dead chicken > around a midnight, while dressed in a pink tu-tu. > > It''s good to know it''s not just me. It would be nice to see the puppet gods > weigh on on this. They''ve been silent about it so far, and a few of us have > been asking about it in the mailing list for quite some time now.googling for "puppet passenger" brings up this as the first hit: http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger Each time I''ve taken someone through those instructions they''ve got a fully functional Passenger install, and I don''t see any mention of dead chickens there[1] Nigel [1] - It is a wiki though, so I won''t be surprised if dead chickens end up on it by the time you read this. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sat, Apr 2, 2011 at 4:07 PM, Nigel Kersten <nigel@puppetlabs.com> wrote:> On Sat, Apr 2, 2011 at 11:13 AM, Douglas Garstang > <doug.garstang@gmail.com> wrote: > > > Ah, Ok. I was using passenger once as well, but wasn''t able to implement > it > > a second time. To get passenger to work with puppet, you need to have > > exactly the right combination of packages/RPM''s available. To know the > exact > > version combination of these packages, you need to wave a dead chicken > > around a midnight, while dressed in a pink tu-tu. > > > > It''s good to know it''s not just me. It would be nice to see the puppet > gods > > weigh on on this. They''ve been silent about it so far, and a few of us > have > > been asking about it in the mailing list for quite some time now. > > > googling for "puppet passenger" brings up this as the first hit: > > http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger > > Each time I''ve taken someone through those instructions they''ve got a > fully functional Passenger install, and I don''t see any mention of > dead chickens there[1] > > Nigel > > > [1] - It is a wiki though, so I won''t be surprised if dead chickens > end up on it by the time you read this. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >+1 for the wiki. Jeff McCune actually published the correct version combination, which is usually Rack version 1.0.1 and Passenger 2.2.11. I believe there''s even a module in the Forge ( http://forge.puppetlabs.com/puppetlabs/passenger). -- Gary Larizza Director of Technology Huron City Schools http://www.huronhs.com 悟 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Apr 6, 2011 at 3:22 PM, Gary Larizza <ccshots@gmail.com> wrote:> > +1 for the wiki. Jeff McCune actually published the correct version > combination, which is usually Rack version 1.0.1 and Passenger 2.2.11. I > believe there''s even a module in the Forge > (http://forge.puppetlabs.com/puppetlabs/passenger). > >Agreed, I''ve never had any issues when rolling out Passenger and Puppet, it defacto for even our test rig. I don''t understand why anyone would use webbrick. Take a look at the excellent wiki, or http://m.etrono.me (how I do mine) -- $ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe ''s/(.)/chr(ord($1)-1)/ge'' -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Apr 6, 2011 at 8:54 AM, joel.merrick@gmail.com < joel.merrick@gmail.com> wrote:> On Wed, Apr 6, 2011 at 3:22 PM, Gary Larizza <ccshots@gmail.com> wrote: > > > > +1 for the wiki. Jeff McCune actually published the correct version > > combination, which is usually Rack version 1.0.1 and Passenger 2.2.11. I > > believe there''s even a module in the Forge > > (http://forge.puppetlabs.com/puppetlabs/passenger). > > > > > > > Agreed, I''ve never had any issues when rolling out Passenger and > Puppet, it defacto for even our test rig. I don''t understand why > anyone would use webbrick. > > Take a look at the excellent wiki, or http://m.etrono.me (how I do mine) > > >Because the correct combination of packages isn''t always available as RPM''s. This is a production environment. We don''t install anything from gem''s. Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hullo, On 04/06/2011 04:54 PM, Douglas Garstang wrote:> Because the correct combination of packages isn''t always available as > RPM''s. This is a production environment. We don''t install anything > from gem''s.As you mentioned you are using Centos 5.5 this might not be too helpful to you but we have in http://puias.princeton.edu/data/puias/unsupported/6/ repo passenger rpms that do work for RHEL6 or clones (for at least 2 separate apache+passenger installations) - no dead chickens or tu-tus required... While we also have an older passenger for 5 I have no idea if it will run with current puppet (we''ve moved on to 6). Josko P. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.