Puppet users - Jan 2012 - Error at the end of a puppet agent run...

err: Could not send report: end of file reached

what is that?


-- 
Peter L. Berghold
Owner, Shark River Technical Solutions LLC

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Sun, Jan 22, 2012 at 04:05:47PM -0500, Peter Berghold
wrote:
> err: Could not send report: end of file reached
> 
> what is that?
> 
> 
Do you see this error on the agent side or master side? Is it
reproduceable?

Did your master or agent die during a catalog run?

I searched your error message on redmine and came up with one issue that
may be related to yours
http://projects.puppetlabs.com/issues/4808

But I guess you have to provide a bit more information about when you
actually see this error to be able to help you.

-Stefan

It happens on the agent side. Both ends of the connection stayed up.

On Jan 22, 2012 5:50 PM, "Stefan Schulte"
<stefan.schulte@taunusstein.net>
wrote:

On Sun, Jan 22, 2012 at 04:05:47PM -0500, Peter Berghold
wrote:
> err: Could not send report: end of...
Do you see this error on the agent side or master side? Is it
reproduceable?

Did your master or agent die during a catalog run?

I searched your error message on redmine and came up with one issue that
may be related to yours
http://projects.puppetlabs.com/issues/4808

But I guess you have to provide a bit more information about when you
actually see this error to be able to help you.

-Stefan

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Sun, Jan 22, 2012 at 05:57:50PM -0500, Peter Berghold
wrote:
> It happens on the agent side. Both ends of the connection stayed up.
> 
do get the error message *everytime* you run your agent? Do you get the
error message for all your agents or just some.

-Stefan

It seems to consistantly happen on one host in particular and randomly on
others.

On Jan 22, 2012 6:16 PM, "Stefan Schulte"
<stefan.schulte@taunusstein.net>
wrote:

On Sun, Jan 22, 2012 at 05:57:50PM -0500, Peter Berghold
wrote:
> It happens on the agent side. Both...
do get the error message *everytime* you run your agent? Do you get the
error message for all your agents or just some.

-Stefan

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Sun, Jan 22, 2012 at 07:15:31PM -0500, Peter Berghold
wrote:
> It seems to consistantly happen on one host in particular and randomly on
> others.
> 
What version of puppet are you using on the agent side and for your
puppet master? Do you use mongrel or passenger or how do you run your
puppet master?

-Stefan

On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte <
stefan.schulte@taunusstein.net> wrote:
>
> What version of puppet are you using on the agent side and for your
> puppet master? Do you use mongrel or passenger or how do you run your
> puppet master?
>
>
puppetmasterd    2.7.9
puppet agent       2.7.9

As of right now I am using neither passenger or mongrel.  Considering doing
so in the future.

The puppet master and the puppet agents run as daemons both on the client
side and the master side.


-- 
Peter L. Berghold
Owner, Shark River Technical Solutions LLC

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

If you didn''t specifically configure Puppet to use Passenger then
you''re using Mongrel by default.  Scalability => false.

On Tue, Jan 24, 2012 at 8:24 AM, Peter Berghold <salty.cowdawg@gmail.com>
wrote:
>
>
> On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte
> <stefan.schulte@taunusstein.net> wrote:
>>
>>
>> What version of puppet are you using on the agent side and for your
>> puppet master? Do you use mongrel or passenger or how do you run your
>> puppet master?
>>
>
> puppetmasterd    2.7.9
> puppet agent       2.7.9
>
> As of right now I am using neither passenger or mongrel.  Considering doing
> so in the future.
>
> The puppet master and the puppet agents run as daemons both on the client
> side and the master side.
>
>
> --
> Peter L. Berghold
> Owner, Shark River Technical Solutions LLC
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Aaron,

What does scalability have to do with this case?  There are maybe a dozen
systems being managed in this case (soon will be more, so then scalability
may play into this) and the configs aren''t that complicated.


On Tue, Jan 24, 2012 at 2:21 PM, Aaron Grewell
<aaron.grewell@gmail.com>wrote:
> If you didn''t specifically configure Puppet to use Passenger then
> you''re using Mongrel by default.  Scalability => false.
>
> On Tue, Jan 24, 2012 at 8:24 AM, Peter Berghold
<salty.cowdawg@gmail.com>
> wrote:
> >
> >
> > On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte
> > <stefan.schulte@taunusstein.net> wrote:
> >>
> >>
> >> What version of puppet are you using on the agent side and for
your
> >> puppet master? Do you use mongrel or passenger or how do you run
your
> >> puppet master?
> >>
> >
> > puppetmasterd    2.7.9
> > puppet agent       2.7.9
> >
> > As of right now I am using neither passenger or mongrel.  Considering
> doing
> > so in the future.
> >
> > The puppet master and the puppet agents run as daemons both on the
client
> > side and the master side.
> >
> >
> > --
> > Peter L. Berghold
> > Owner, Shark River Technical Solutions LLC
> >
> > --
> > You received this message because you are subscribed to the Google
Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
Peter L. Berghold
Owner, Shark River Technical Solutions LLC

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Depending on your hardware and ruleset a dozen might be more than
Mongrel will handle.

On Tue, Jan 24, 2012 at 11:32 AM, Peter Berghold
<salty.cowdawg@gmail.com> wrote:
> Aaron,
>
> What does scalability have to do with this case?  There are maybe a dozen
> systems being managed in this case (soon will be more, so then scalability
> may play into this) and the configs aren''t that complicated.
>
>
>
> On Tue, Jan 24, 2012 at 2:21 PM, Aaron Grewell
<aaron.grewell@gmail.com>
> wrote:
>>
>> If you didn''t specifically configure Puppet to use Passenger
then
>> you''re using Mongrel by default.  Scalability => false.
>>
>> On Tue, Jan 24, 2012 at 8:24 AM, Peter Berghold
<salty.cowdawg@gmail.com>
>> wrote:
>> >
>> >
>> > On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte
>> > <stefan.schulte@taunusstein.net> wrote:
>> >>
>> >>
>> >> What version of puppet are you using on the agent side and for
your
>> >> puppet master? Do you use mongrel or passenger or how do you
run your
>> >> puppet master?
>> >>
>> >
>> > puppetmasterd    2.7.9
>> > puppet agent       2.7.9
>> >
>> > As of right now I am using neither passenger or mongrel. 
Considering
>> > doing
>> > so in the future.
>> >
>> > The puppet master and the puppet agents run as daemons both on the
>> > client
>> > side and the master side.
>> >
>> >
>> > --
>> > Peter L. Berghold
>> > Owner, Shark River Technical Solutions LLC
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Puppet Users" group.
>> > To post to this group, send email to
puppet-users@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > puppet-users+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/puppet-users?hl=en.
>>
>> --
>> You received this message because you are subscribed to the Google
Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
>
>
> --
> Peter L. Berghold
> Owner, Shark River Technical Solutions LLC
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Tue, Jan 24, 2012 at 11:24:58AM -0500, Peter Berghold
wrote:
> On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte <
> stefan.schulte@taunusstein.net> wrote:
> 
> >
> > What version of puppet are you using on the agent side and for your
> > puppet master? Do you use mongrel or passenger or how do you run your
> > puppet master?
> >
> >
> puppetmasterd    2.7.9
> puppet agent       2.7.9
> 
> As of right now I am using neither passenger or mongrel.  Considering doing
> so in the future.
> 
> The puppet master and the puppet agents run as daemons both on the client
> side and the master side.
> 
You can run your agent with the command line option --trace. This way
you should see a backtrace when the exception happens so we hopefully
know exactly where the error is happening.

But I''m not sure if the output will go to the logfiles so you might
have
to run your agent in foreground mode

    puppet agent --verbose --trace --no-daemonize

As far as I know Puppet itself (when not run behind passenger or similar)
is not really capable of handling concurrent request. If multiple agents
query your master at the same they might run into timeouts.

-Stefan

On 01/26/2012 12:15 PM, Felix Frank wrote:
> On 01/24/2012 08:21 PM, Aaron Grewell wrote:
>> If you didn''t specifically configure Puppet to use Passenger
then
>> you''re using Mongrel by default.  Scalability => false.
> 
> Isn''t that webrick?
> 
> AFAIK mongrel would be fine, webrick is indeed a problem, and passenger
> is known to be a good alternative.
> 
> Cheers,
> Felix
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I think the problem happens when you configure agents to send reports. 

In this case when you run the agent in the console the output is not cached 
just showed and the log is empty so the report is also empty.

# puppet agent --verbose --trace --no-daemonize

My output is...

notice: Starting Puppet client version 2.6.2
info: Retrieving plugin
info: Caching catalog for ccsdtfdempup01.dem.int
info: Applying configuration version ''1330364775''
notice: /Stage[main]/Clamav/Service[clamav-freshclam]/ensure: ensure 
changed ''stopped'' to ''running''
notice: Detected operating system major version: 6
notice: /Stage[main]/Local-repository/Notify[Detected operating system 
major version: 6]/message: defined ''message'' as
''Detected operating system
major version: 6''
notice: /Stage[main]/Zabbix-agent/Service[zabbix-agent]/ensure: ensure 
changed ''stopped'' to ''running''
notice: /Stage[main]/Grub/Exec[/root/puppet.grub.sh]/returns: executed 
successfully
notice: No custom file, applying default files/etc/security/limits.conf
notice: /Stage[main]/Limites/Notify[No custom file, applying default 
files/etc/security/limits.conf]/message: defined ''message'' as
''No custom
file, applying default files/etc/security/limits.conf''
notice: /Stage[main]/Tape-backup/Package[sendEmail]/ensure: ensure changed 
''purged'' to ''present''
notice: Finished catalog run in 4.15 seconds
/usr/lib/ruby/1.8/net/protocol.rb:135:in `sysread''
/usr/lib/ruby/1.8/net/protocol.rb:135:in `rbuf_fill''
/usr/lib/ruby/1.8/timeout.rb:67:in `timeout''
/usr/lib/ruby/1.8/timeout.rb:101:in `timeout''
/usr/lib/ruby/1.8/net/protocol.rb:134:in `rbuf_fill''
/usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil''
/usr/lib/ruby/1.8/net/protocol.rb:126:in `readline''
/usr/lib/ruby/1.8/net/http.rb:2028:in `read_status_line''
/usr/lib/ruby/1.8/net/http.rb:2017:in `read_new''
/usr/lib/ruby/1.8/net/http.rb:1051:in `request''
/usr/lib/ruby/1.8/net/http.rb:1037:in `request''
/usr/lib/ruby/1.8/net/http.rb:543:in `start''
/usr/lib/ruby/1.8/net/http.rb:1035:in `request''
/usr/lib/ruby/1.8/net/http.rb:857:in `put''
/usr/lib/ruby/1.8/puppet/indirector/rest.rb:90:in `save''
/usr/lib/ruby/1.8/puppet/indirector/indirection.rb:253:in `save''
/usr/lib/ruby/1.8/puppet/indirector.rb:64:in `save''
/usr/lib/ruby/1.8/puppet/configurer.rb:178:in `send_report''
/usr/lib/ruby/1.8/puppet/configurer.rb:172:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:39:in `run''
/usr/lib/ruby/1.8/puppet/agent/locker.rb:21:in `lock''
/usr/lib/ruby/1.8/puppet/agent.rb:39:in `run''
/usr/lib/ruby/1.8/sync.rb:230:in `synchronize''
/usr/lib/ruby/1.8/puppet/agent.rb:39:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:103:in `with_client''
/usr/lib/ruby/1.8/puppet/agent.rb:37:in `run''
/usr/lib/ruby/1.8/puppet/application.rb:171:in `call''
/usr/lib/ruby/1.8/puppet/application.rb:171:in `controlled_run''
/usr/lib/ruby/1.8/puppet/agent.rb:35:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:78:in `start''
/usr/lib/ruby/1.8/puppet/external/event-loop/signal-system.rb:95:in
`call''
/usr/lib/ruby/1.8/puppet/external/event-loop/signal-system.rb:95:in 
`__signal__''
/usr/lib/ruby/1.8/puppet/external/event-loop/signal-system.rb:95:in
`each''
/usr/lib/ruby/1.8/puppet/external/event-loop/signal-system.rb:95:in 
`__signal__''
(eval):2:in `signal''
/usr/lib/ruby/1.8/puppet/external/event-loop/event-loop.rb:317:in 
`sound_alarm''
/usr/lib/ruby/1.8/puppet/agent.rb:82:in `start''
/usr/lib/ruby/1.8/puppet/daemon.rb:125:in `start''
/usr/lib/ruby/1.8/puppet/application/agent.rb:132:in `main''
/usr/lib/ruby/1.8/puppet/application/agent.rb:89:in `run_command''
/usr/lib/ruby/1.8/puppet/application.rb:287:in `run''
/usr/lib/ruby/1.8/puppet/application.rb:393:in `exit_on_fail''
/usr/lib/ruby/1.8/puppet/application.rb:287:in `run''
/usr/lib/ruby/1.8/puppet/util/command_line.rb:55:in `execute''
/usr/bin/puppet:4
err: Could not send report: end of file reached

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/qVZNPtNfGeQJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

After experiencing the same problem I came to the conclusion that was 
all firewall related.
Things to look at:


1. On puppetmaster server look at your puppet.conf option for reporturl; 

reporturl = http://puppetmaster.mydomain.com:80/reports/upload

2. Web service is running on your puppemaster server
ps aux |grep http
lsof -i :80
netstat -tunl

3. Test conectivity from puppet agent
telnet puppetmaster.mydomain.com "AllPoRTS"

where "AllPoRTS" are your ports defined for puppet

telnet puppetmaster.mydomain.com 3128





On Sunday, January 22, 2012 3:05:47 PM UTC-6, Salty Old Cowdawg
wrote:
>
> err: Could not send report: end of file reached
>
> what is that?
>
>
> -- 
> Peter L. Berghold 
> Owner, Shark River Technical Solutions LLC 
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/16MHgaeKlvEJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.