Puppet users - Feb 2013 - Intermittent Erorr 400 on Server messages

Hi Guys,

I am running puppet server version 3.0.2-1 on a RHEL 5.8 virtual machine 
with about 110 clients.  I am seeing intermittent errors with my clients 
that are failing with the following error messages:

--
Could not retrieve catalog from remote server: Error 400 on SERVER: Could 
not find class motd for xxx on node xxx
--

If I login to that host which failed and manually run a "puppet agent
-t"
it finishes without any error messages.  These errors are intermittent but 
have caused corruption of my passwd file since I also manage that via 
puppet.  This message shows up for different servers with different classes 
in the error message.  I have looked at my classes and I don''t see any 
problems with it.  Any idea what might be causing this problem?

Any help would be greatly appreciated.

Thanks!
-J

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

I think that you have the puppet modules, manifest or templates with some 
mistake. 

Try to create a easy hello world with Puppet.

El dilluns 25 de febrer de 2013 22:03:18 UTC+1, Jagga Soorma va
escriure:
>
> Hi Guys,
>
> I am running puppet server version 3.0.2-1 on a RHEL 5.8 virtual machine 
> with about 110 clients.  I am seeing intermittent errors with my clients 
> that are failing with the following error messages:
>
> --
> Could not retrieve catalog from remote server: Error 400 on SERVER: Could 
> not find class motd for xxx on node xxx
> --
>
> If I login to that host which failed and manually run a "puppet agent
-t"
> it finishes without any error messages.  These errors are intermittent but 
> have caused corruption of my passwd file since I also manage that via 
> puppet.  This message shows up for different servers with different classes
> in the error message.  I have looked at my classes and I don''t see
any
> problems with it.  Any idea what might be causing this problem?
>
> Any help would be greatly appreciated.
>
> Thanks!
> -J
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On Mon, Feb 25, 2013 at 9:03 PM, Jagga Soorma <jagga13@gmail.com>
wrote:
> Hi Guys,
>
> I am running puppet server version 3.0.2-1 on a RHEL 5.8 virtual machine
> with about 110 clients.  I am seeing intermittent errors with my clients
> that are failing with the following error messages:
Intermittent errors with a large(ish) number of clients hints to me
straight away that you could be running into issues with Puppet''s HTTP
server, Webrick.  If you''re not running puppet behind Apache with
mod_passenger, or Nginx with Unicorn, I''d suggest you look into those.
 Webrick is single-threaded, so depending on the timing of your
client''s checkins, you can easily overload it, leading to the issues
you''re seeing.

Regards,

Matt.

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

Thanks for your response Matthew.  I will try to enable
apache/mod_passenger with puppet and see if that helps.  Would I need to
change anything on the clients in order to make this change on the puppet
master?

Thanks again.

On Tue, Feb 26, 2013 at 2:18 AM, Matthew Burgess <
matthew.2.burgess@gmail.com> wrote:
> On Mon, Feb 25, 2013 at 9:03 PM, Jagga Soorma <jagga13@gmail.com>
wrote:
> > Hi Guys,
> >
> > I am running puppet server version 3.0.2-1 on a RHEL 5.8 virtual
machine
> > with about 110 clients.  I am seeing intermittent errors with my
clients
> > that are failing with the following error messages:
>
> Intermittent errors with a large(ish) number of clients hints to me
> straight away that you could be running into issues with Puppet''s
HTTP
> server, Webrick.  If you''re not running puppet behind Apache with
> mod_passenger, or Nginx with Unicorn, I''d suggest you look into
those.
>  Webrick is single-threaded, so depending on the timing of your
> client''s checkins, you can easily overload it, leading to the
issues
> you''re seeing.
>
> Regards,
>
> Matt.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscribe@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

The modules are fine because this is just a intermittent problem.  Most of
the times the puppet runs are fine even when things are being changed on
the nodes.  If it was a problem with the modules then I would expect it to
consistently fail.  Let me know if that assumption is not correct.  I am in
the process of enabling apache/mod_passenger with puppet and hopefully that
will help.

Thanks.

On Tue, Feb 26, 2013 at 2:10 AM, Alex Vaqué Brull <memfis@gmail.com>
wrote:
> I think that you have the puppet modules, manifest or templates with some
> mistake.
>
> Try to create a easy hello world with Puppet.
>
> El dilluns 25 de febrer de 2013 22:03:18 UTC+1, Jagga Soorma va escriure:
>
>> Hi Guys,
>>
>> I am running puppet server version 3.0.2-1 on a RHEL 5.8 virtual
machine
>> with about 110 clients.  I am seeing intermittent errors with my
clients
>> that are failing with the following error messages:
>>
>> --
>> Could not retrieve catalog from remote server: Error 400 on SERVER:
Could
>> not find class motd for xxx on node xxx
>> --
>>
>> If I login to that host which failed and manually run a "puppet
agent -t"
>> it finishes without any error messages.  These errors are intermittent
but
>> have caused corruption of my passwd file since I also manage that via
>> puppet.  This message shows up for different servers with different
classes
>> in the error message.  I have looked at my classes and I don''t
see any
>> problems with it.  Any idea what might be causing this problem?
>>
>> Any help would be greatly appreciated.
>>
>> Thanks!
>> -J
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscribe@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On Tue, Feb 26, 2013 at 5:48 PM, Jagga Soorma <jagga13@gmail.com>
wrote:
> Thanks for your response Matthew.  I will try to enable
apache/mod_passenger
> with puppet and see if that helps.  Would I need to change anything on the
> clients in order to make this change on the puppet master?
No, the clients'' configuration doesn''t need to change.

Regards,

Matt.

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

I have been investigating this issue as well, and assuming you are also 
seeing SSL errors with your logs, it is very likely the same cause as over 
here.

I''ve been able to find information about a bug in older Ruby versions 
whowing exactly this sort of SSL (mal)behaviour.

So maybe this can give you some extra hints to search for.

I don''t recall the places I found this information unfortunately, since
we
did not have the option to upgrade our Ruby version at this point.
We''ve
chosen to ignore htese errors if they are due to SSL errors, as subsequent 
puppet runs (about 30 minutes later) will usually be fine.

Not a real solution, sorry.

On Monday, February 25, 2013 10:03:18 PM UTC+1, Jagga Soorma
wrote:
>
> Hi Guys,
>
> I am running puppet server version 3.0.2-1 on a RHEL 5.8 virtual machine 
> with about 110 clients.  I am seeing intermittent errors with my clients 
> that are failing with the following error messages:
>
> --
> Could not retrieve catalog from remote server: Error 400 on SERVER: Could 
> not find class motd for xxx on node xxx
> --
>
> If I login to that host which failed and manually run a "puppet agent
-t"
> it finishes without any error messages.  These errors are intermittent but 
> have caused corruption of my passwd file since I also manage that via 
> puppet.  This message shows up for different servers with different classes
> in the error message.  I have looked at my classes and I don''t see
any
> problems with it.  Any idea what might be causing this problem?
>
> Any help would be greatly appreciated.
>
> Thanks!
> -J
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.