Puppet

Tried reports = foreman, that works. Trying reports = foreman,tagmail or reports = tagmail get this error. Spoke with our databse admins, they guess that the client sends an unexpected eof. Tried updating active record from version 2.2.3 to 2.3.5 and passenger from 2.2.2 to 2.2.11 no change. Seen this erros under puppet-0.24.8 but they where very sporadic and the connection came always back again.

This also happens to me on Debian Lenny. It happens with both 0.25.4 and 2.6.1. If I turn off tagmail reports (and leave reports=log,store), it goes away.

I can also confirm that this is still the case with 2.6.4. We are currently using 0.25.5 with sqlite in production because of this bug, and I was hoping it would have been fixed by now. 2.6.4 and postgresql works fine in our test environment without tagmail, but the connection broken as soon as tagmail is used.

I am facing this problem too, and it appeared when I enabled tagmail+err. Restarting the puppet master appears to make this go away for a while, but I haven’t detected a pattern yet.

Environment notes:

• OS: debian squeeze, x64
• puppet: 2.6.2-4 (squeeze apt)
• postgres:8.4.7 (squeeze apt)

master config:

[master]
storeconfigs=true
thin_storeconfigs=true
dbadapter=postgresql
dbhost=localhost
dbname=xxxx
dbuser=xxx
dbpassword=xxx
report=true
reports=tagmail,rrdgraph
tagmap=/etc/puppet/tagmail.conf
report_sender_email=puppet-report@xxxxx

/etc/puppet/tagmail.conf (file perms – puppet/puppet/mode 440):

err: root@localhost

James Turnbull wrote:

So it never happens with any other report type set?

We are seeing this issue as well with puppet 2.6.9 Unfortunately we are not using any other report types

I will set up a development environment later this week and enable other reports

The conclusion of that discussion is that we are going to introduce a new method to fork, closing file handles, and encourage use of that through the code base. Given we review all submissions in core, finding the problem being reintroduces is less likely to cause grief than trying to change the behaviour of a core method.