On Wed, Sep 26, 2007 at 11:19:16AM -0400, Micah Anderson wrote: > Package: puppetmaster > Version: 0.23.2-7 > Severity: normal > > This intermittant error started showing up when I upgraded my clients > and master to 0.23.2-6, and is still there in -7: > > Sep 26 06:02:10 petrel puppetd[17101]: Could not retrieve configuration: > Certificates were not trusted: SSL_write:: bad write retry > > If I login and run puppetd --test everything works out fine, but if I > watch the logs after several runs I start getting those errors. My logs > are filled with them now.
Can you provide a traceback (running puppetd with --trace) when the error occurs? I know it's a pest to get it, but that error could be coming from a number of places, and it's quite important to know where. > Something changed in the debian package between -3 and -6 that caused > this as I was running -3 without error, and if I downgrade to -3 the > error ceases. There have been changes to SSL stuff between -3 and -6, to support keep-alive, and that would be my first suspect. However, there has been a report on IRC of troubles with near-stock 0.23.2 on CentOS. I'm yet to ascertain exactly what has changed, but it looks like it might not be caused by the keep-alive patch after all. I'll keep you posted. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
