Puppet users - Feb 2007 - Fwd: devnull-dev.stanford.edu syslog filter results (fwd)

We''re still intermittantly getting these messages in syslog on various
different systems:

Feb 14 17:32:10 server-dev puppetd[20363]: Could not call
puppetreports.report: #<EOFError: end of file reached> Feb 14 17:32:10
server-dev puppetd[20363]: Reporting failed: end of file reached

Anyone else ever see stuff like this?

On Feb 15, 2007, at 3:22 PM, Digant C Kasundra wrote:
> We''re still intermittantly getting these messages in syslog on
various
> different systems:
>
> Feb 14 17:32:10 server-dev puppetd[20363]: Could not call
> puppetreports.report: #<EOFError: end of file reached> Feb 14
17:32:10
> server-dev puppetd[20363]: Reporting failed: end of file reached
>
> Anyone else ever see stuff like this?
I''ve seen it, but I cannot track it down or even get it to happen  
consistently.

I can only think it has something to do with either multiple hosts  
sending reports at a time or some design flaw in how reports are  
received.  I haven''t been able to find a flaw nor get it to happen  
consistently while hitting the reports system with multiple nodes, so  
I dunno.

I''ll file it as a bug, though, to remind me to look at it again.

  --
  There are three kinds of death in this world.  There''s heart death,
  there''s brain death, and there''s being off the network.  --
Guy Almes
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

On 2/15/07, Luke Kanies <luke@madstop.com> wrote:
> On Feb 15, 2007, at 3:22 PM, Digant C Kasundra wrote:
> > Feb 14 17:32:10 server-dev puppetd[20363]: Could not call
> > puppetreports.report: #<EOFError: end of file reached> Feb 14
17:32:10
> > server-dev puppetd[20363]: Reporting failed: end of file reached
> I''ve seen it, but I cannot track it down or even get it to happen
> consistently.
Just like to chime in that we get it very often too, some snippets:

tim@fwlb1:~$ grep puppetreports /var/log/syslog
Feb 15 11:03:00 fwlb1 puppetd[19423]: Could not call
puppetreports.report: #<EOFError: end of file reached>
Feb 15 11:03:15 fwlb1 puppetd[19423]: Could not call
puppetreports.report: #<EOFError: end of file reached>
Feb 15 12:06:54 fwlb1 puppetd[2835]: Could not call
puppetreports.report: #<EOFError: end of file reached>
Feb 15 13:28:03 fwlb1 puppetd[2835]: Could not call
puppetreports.report: #<EOFError: end of file reached>

tim@wa1:~$ grep puppetreports /var/log/syslog
Feb 15 08:05:37 wa1 puppetd[17075]: Could not call
puppetreports.report: #<EOFError: end of file reached>
Feb 15 10:06:13 wa1 puppetd[17075]: Could not call
puppetreports.report: #<EOFError: end of file reached>
Feb 15 12:06:59 wa1 puppetd[17075]: Could not call
puppetreports.report: #<EOFError: end of file reached>

tim@management:~$ grep puppetreports /var/log/syslog
Feb 15 15:13:09 management puppetd[9100]: Could not call
puppetreports.report: #<EOFError: end of file reached>

A clue might be that it only happens on servers that have had some
changes recently in their puppet-managed config.

-- 
Gegroet,
Tim

On Feb 15, 2007, at 3:22 PM, Digant C Kasundra wrote:
> We''re still intermittantly getting these messages in syslog on
various
> different systems:
>
> Feb 14 17:32:10 server-dev puppetd[20363]: Could not call
> puppetreports.report: #<EOFError: end of file reached> Feb 14
17:32:10
> server-dev puppetd[20363]: Reporting failed: end of file reached
As far as I can tell, this doesn''t have any negative affect on the  
reporting.  I still see each report being processed correctly, with  
all of them completing.

I''d still like to track this down, of course, but it seems like a  
harmless error at this point.

  --
  One of the Ten Commandments for Technicians
          (7) Work thou not on energized equipment, for if thou dost,  
thy
              fellow workers will surely buy beers for thy widow and
              console her in other ways.
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com