Issue #21309 has been updated by Justin Dow.
Yes, we make heavy use of virtual resources. Without evaluating each client, I
think *most* are using the same set. We use virtual resources for our users,
and they are the same across most clients.
Lots of stuff like this:
<pre>
@user {
'jdow':
uid => '1299',
shell => '/bin/bash',
managehome => true,
home => '/home/jdow',
groups => 'users',
ensure => 'present';
}
@ssh_authorized_keys {
'jdow_gen_1':
user => 'jdow',
require => User['jdow'],
type => 'ssh-rsa',
key => 'mykey';
}
Then:
define ldap_users::user {
realize(User[$name])
Ssh_Authorized_Key <| user == $name |>
}
@ldap_users::user {
'jdow':;
}
realize(Ldap_users::User['jdow'])
</pre>
And something like 40 of those per node, but the same on both the crashy and
non-crashy masters..
----------------------------------------
Bug #21309: Upgrade to 3.2.2 causes puppet-server backend to crash
https://projects.puppetlabs.com/issues/21309#change-93150
* Author: Justin Dow
* Status: Needs More Information
* Priority: Normal
* Assignee: Justin Dow
* Category:
* Target version:
* Affected Puppet version:
* Keywords:
* Branch:
----------------------------------------
Our setup is an apache/mod_passenger setup. Two independent puppetmasters, set
up identically (same /etc/puppet) using httpd-2.2.15-28.el6_4.x86_64 and
mod_passenger-3.0.11-1.el6.x86_64 . One puppetmaster on RHEL6.3 is fine after
the upgrade to 3.2.2. The other puppetmaster on RHEL6.4 periodically has this
in /var/log/httpd/error_log:
[ pid=32452 thr=140580093937632 file=ext/apache2/Hooks.cpp:817 time=2013-06-19
06:15:55.782 ]: The backend application (process 32586) did not send a valid
HTTP response; instead, it sent nothing at all. It is possible that it has
crashed; please check whether there are crashing bugs in this application.
/usr/lib/ruby/site_ruby/1.8/puppet/parser/collector.rb:163: [BUG] Segmentation
fault
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
[ pid=32450 thr=140580093937632 file=ext/apache2/Hooks.cpp:817 time=2013-06-19
06:22:31.475 ]: The backend application (process 529) did not send a valid HTTP
response; instead, it sent nothing at all. It is possible that it has crashed;
please check whether there are crashing bugs in this application.
/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/collexpr.rb:29: [BUG]
Segmentation fault
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
[ pid=32446 thr=140580093937632 file=ext/apache2/Hooks.cpp:817 time=2013-06-19
06:22:36.598 ]: The backend application (process 542) did not send a valid HTTP
response; instead, it sent nothing at all. It is possible that it has crashed;
please check whether there are crashing bugs in this application.
The only difference I can find between the two servers is that the working one
is on RHEL6.3 and the broken one is on 6.4 and the ruby versions are just a
little different:
6.3: ruby-1.8.7.352-7.el6_2.x86_64
6.4: ruby-1.8.7.352-10.el6_4.x86_64
I don't think it's a package/version. Perhaps the crashy master is serving a
manifest to a client that it is choking on, something the working master isn't
seeing?
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
