Hi all,
As promised, 0.24.1 is out. Here''s the changelog:
Updated vim filetype detection. (#900 and #963)
Default resources like schedules no longer conflict with
managed resources. (#965)
Removing the ability to disable http keep-alive, since
it didn''t really work anyway and it should no longer
be necessary.
Refactored http keep-alive so it actually works again.
This should be sufficient enough that we no longer need the
ability to disable keep-alive. There is now a central
module responsible for managing HTTP instances, along with
all certificates in those instances.
Fixed a backward compatibility issue when running 0.23.x
clients against 0.24.0 servers -- relationships would
consistently not work. (#967)
Closing existing http connections when opening a new one,
and closing all connections after each run. (#961)
Removed warning about deprecated explicit plugins mounts.
The main fixes are that http keep-alive works now (meaning you should
only have one connection open to your server, not tens or hundreds),
the backward compatibility problem is fixed, and default schedules
work again.
--
As a general rule, don''t solve puzzles that open portals to Hell.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
Hi, I just built and uploaded packages for 0.24.1 to my yum repo[1] and to the official Fedora/EPEL repos. As always, my repo should be considered experimental, and you should get updates from the official Fedora/EPEL repos. Besides all the good things that Luke mentioned fixed, this update also fixes a problem with erasing packages on Fedora/RHEL/CentOS (trac #964) David [1] http://people.redhat.com/dlutter/yum
I still can''t get puppet 0.24.x to start with the --listen option on a RHEL5 system. Can anyone else reproduce this problem? Luke Kanies wrote:> Hi all, > > As promised, 0.24.1 is out. Here''s the changelog: > > Updated vim filetype detection. (#900 and #963) > > Default resources like schedules no longer conflict with > managed resources. (#965) > > Removing the ability to disable http keep-alive, since > it didn''t really work anyway and it should no longer > be necessary. > > Refactored http keep-alive so it actually works again. > This should be sufficient enough that we no longer need the > ability to disable keep-alive. There is now a central > module responsible for managing HTTP instances, along with > all certificates in those instances. > > Fixed a backward compatibility issue when running 0.23.x > clients against 0.24.0 servers -- relationships would > consistently not work. (#967) > > Closing existing http connections when opening a new one, > and closing all connections after each run. (#961) > > Removed warning about deprecated explicit plugins mounts. > > The main fixes are that http keep-alive works now (meaning you should > only have one connection open to your server, not tens or hundreds), > the backward compatibility problem is fixed, and default schedules > work again. > > -- > As a general rule, don''t solve puzzles that open portals to Hell. > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users-- Iain Pople Systems Interface Technical Lead University of Melbourne
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Iain Pople wrote:> I still can''t get puppet 0.24.x to start with the --listen option on a > RHEL5 system. Can anyone else reproduce this problem?Iain Do you have any logs or output from the problem? Can you try to start puppetd with --trace --debug --verbose option? What exact 0.24.x version? .0 or .1? Regards James Turnbull - -- James Turnbull (james@lovedthanlost.net) - -- Author of: - - Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) - - Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) - - Hardening Linux (http://www.amazon.com/gp/product/1590594444/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHeuVG9hTGvAxC30ARAtLdAKCkuFZVCrUSyt8tAXS+SFTu/s1tEQCeLeme uknd4hlqAawFjxyDqdTPu6c=roAI -----END PGP SIGNATURE-----
running: puppetd --trace --debug --verbose --listen --server \ puppet.unimelb.edu.au gives no output and gives the following in /var/log/messages Jan 2 14:29:19 fidel puppetd[15137]: Reopening log files Jan 2 14:29:19 fidel puppetd[15137]: Starting handler for Runner Jan 2 14:29:20 fidel puppetd[15137]: Starting server for Puppet version 0.24.1 however puppet is not running: # ps -Af | grep puppet root 15145 14213 0 14:30 pts/1 00:00:00 grep puppet James Turnbull wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Iain Pople wrote: >> I still can''t get puppet 0.24.x to start with the --listen option on a >> RHEL5 system. Can anyone else reproduce this problem? > > Iain > > Do you have any logs or output from the problem? Can you try to start > puppetd with --trace --debug --verbose option? What exact 0.24.x > version? .0 or .1? > > Regards > > James Turnbull > > - -- > James Turnbull (james@lovedthanlost.net) > - -- > Author of: > - - Pulling Strings with Puppet > (http://www.amazon.com/gp/product/1590599780/) > - - Pro Nagios 2.0 > (http://www.amazon.com/gp/product/1590596099/) > - - Hardening Linux > (http://www.amazon.com/gp/product/1590594444/) > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHeuVG9hTGvAxC30ARAtLdAKCkuFZVCrUSyt8tAXS+SFTu/s1tEQCeLeme > uknd4hlqAawFjxyDqdTPu6c> =roAI > -----END PGP SIGNATURE----- > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users-- Iain Pople Systems Interface Technical Lead University of Melbourne
I''m having the same problem on Debian Etch, see this ticket for details: http://reductivelabs.com/trac/puppet/ticket/969 Iain Pople wrote:> running: > > puppetd --trace --debug --verbose --listen --server \ > puppet.unimelb.edu.au > > gives no output and gives the following in /var/log/messages > > Jan 2 14:29:19 fidel puppetd[15137]: Reopening log files > Jan 2 14:29:19 fidel puppetd[15137]: Starting handler for Runner > Jan 2 14:29:20 fidel puppetd[15137]: Starting server for Puppet version > 0.24.1 > > however puppet is not running: > > # ps -Af | grep puppet > root 15145 14213 0 14:30 pts/1 00:00:00 grep puppet > > > James Turnbull wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Iain Pople wrote: >>> I still can''t get puppet 0.24.x to start with the --listen option on a >>> RHEL5 system. Can anyone else reproduce this problem? >> Iain >> >> Do you have any logs or output from the problem? Can you try to start >> puppetd with --trace --debug --verbose option? What exact 0.24.x >> version? .0 or .1? >> >> Regards >> >> James Turnbull >> >> - -- >> James Turnbull (james@lovedthanlost.net) >> - -- >> Author of: >> - - Pulling Strings with Puppet >> (http://www.amazon.com/gp/product/1590599780/) >> - - Pro Nagios 2.0 >> (http://www.amazon.com/gp/product/1590596099/) >> - - Hardening Linux >> (http://www.amazon.com/gp/product/1590594444/) >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.7 (MingW32) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iD8DBQFHeuVG9hTGvAxC30ARAtLdAKCkuFZVCrUSyt8tAXS+SFTu/s1tEQCeLeme >> uknd4hlqAawFjxyDqdTPu6c>> =roAI >> -----END PGP SIGNATURE----- >> _______________________________________________ >> Puppet-users mailing list >> Puppet-users@madstop.com >> https://mail.madstop.com/mailman/listinfo/puppet-users > >
On Jan 1, 2008, at 7:02 PM, Iain Pople wrote:> I still can''t get puppet 0.24.x to start with the --listen option on a > RHEL5 system. Can anyone else reproduce this problem?I assume this is the same problem that Martha is having on Debian Etch. Neither I nor any of the other Puppet developers have been able to reproduce this problem, which means we can''t fix it. Is there anyone having this problem who knows Puppet, Ruby, or debuggin well enough that they can diagnose it? Alternatively, can someone who''s having the problem provide me with root access on a failing machine (or making a failing VM available for download by me) so I can debug it myself? -- Health is merely the slowest possible rate at which one can die. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com