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
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,
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.cowd...@gmail.com wrote:
On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte
stefan.schu...@taunusstein.net wrote:
What
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.grew...@gmail.comwrote:
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.cowd...@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
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.
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
It happens on the agent side. Both ends of the connection stayed up.
On Jan 22, 2012 5:50 PM, Stefan Schulte stefan.schu...@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
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
pgpFvg3oJfILo.pgp
Description:
It seems to consistantly happen on one host in particular and randomly on
others.
On Jan 22, 2012 6:16 PM, Stefan Schulte stefan.schu...@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
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
11 matches
Mail list logo
