On Monday 30 March 2009 21:03:57 you wrote: > I cannot reproduce the bug with 0.24.7-1~bpo50~madduck+2. Please > confirm that's the version you are using.
$ apt-cache policy puppet
puppet:
Installed: 0.24.7-1~bpo50~madduck+2
Candidate: 0.24.7-1~bpo50~madduck+2
Version table:
*** 0.24.7-1~bpo50~madduck+2 0
100 /var/lib/dpkg/status
0.24.5-3 0
500 http://ftp.nz.debian.org lenny/main Packages
I'd test more, but I'm working on the puppet config at the moment, and
switching between cron and daemon too much becomes problematic when I'm doing
that. But I did see a huge number of CLOSE_WAITs that I'm confident were with
this version. Note that it doesn't always seem to come up. For example, I see
it on a set of openvz servers that are on the same hardware node as the
master, but I didn't see any when configuring an EC2 server talking to the
same puppetmaster, but over the internet (via vpn). However, the EC2 server
only had a generic configuration, so it's not conclusive.
--
Robin <ro...@kallisti.net.nz> JabberID: <eyth...@jabber.kallisti.net.nz>
http://www.kallisti.net.nz/blog ||| http://identi.ca/eythian
PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
signature.asc
Description: This is a digitally signed message part.
