Jira (PUP-1371) puppet cannot manage agent or master after update to puppet 3.2
Title: Message Title redmine.exporter created an issue Puppet / PUP-1371 puppet cannot manage agent or master after update to puppet 3.2 Issue Type: Bug Assignee: Unassigned Created: 04/Jan/14 12:45 PM Labels: redmine Priority: Normal Reporter: redmine.exporter When puppet is configured to manage it's own services it fails, due to broken init scripts for EL6 Notice: /Stage[main]/Puppet::Server/Service[puppetmaster]/ensure: ensure changed 'stopped' to 'running' Info: /Stage[main]/Puppet::Server/Service[puppetmaster]: Unscheduling refresh on Service[puppetmaster] Notice: /Stage[main]/Puppet/Service[puppet]/ensure: ensure changed 'stopped' to 'running' Info: /Stage[main]/Puppet/Service[puppet]: Unscheduling refresh on Service[puppet] service puppetmaster status puppet dead but subsys locked service puppet status puppet dead but subsys locked ps auwx |grep puppet puppet 10167 0.3 5.6 207052 109260 ? Ssl 17:52 0:32 /usr/bin/ruby /usr/bin/puppet master root 13385 0.0 3.0 148236 59508 ? Ss 19:37 0:00 /usr/bin/ruby /usr/bin/puppet agent root 15789 0.0 0.0 103236 832 pts/0 S+ 20:08 0:00 grep puppet Looking into the configuration, I fo
Jira (PUP-1371) puppet cannot manage agent or master after update to puppet 3.2
Title: Message Title Jo Rhett commented on an issue Re: puppet cannot manage agent or master after update to puppet 3.2 As none of the history was imported, I'd like to point out that numerous issues identified in the diagnosis of this issue remain outstanding. This was "ready for documentation" almost a year ago, but we've done 3 minor releases since then. So perhaps we should retarget this issue: Revise the comment on rundir in puppet.conf to indicate that changing it will break the CentOS/RHEL init scripts Remove the localconfig and classfile changes which differ from documentation, and break other modules and mcollective, who are expecting those files elsewhere. FWIW, I considered changing rundir, but I couldn’t find any documentation on what else is put in rundir so I made the most minimal change I could by specifying just the pidfiles. The revisions around how statedir and rundir are used are worthy of their own documentation page. #4 UPDATED BY MATTHAUS OWENS 8 MONTHS AGO You’re right about the comments, the comment is wrong about the default values. The default is $statedir/classes.txt and $statedir defaults to $vardir/state. So the easy short term fix is to update the comments to match the correct defaults for those values (and add a comment about rundir and init scripts). I don’t know why the values differ from the defaults though, so I’ll do a little more digging to see if there’s an awesome reason for the variation. Changing or removing that value in the conffile we ship with our packages would probably need to wait for a major version to prevent unexpected breakages. #5 UPDATED BY JO RHETT 8 MONTHS AGO That’s fine. But fixing the comments would be a definite improvement for 3.2.3 to avoid other head-scratching I’d also like to see documentation for everything rundir uses. I fell into this trap being afraid that something else would be put in rundir that some other thing was expecting in vardir, etc <— same problem as happening with classfile. If I had been sure it was only pid files, they would have helped. #7 UPDATED BY CHARLIE SHARPSTEEN 8 MONTHS AGO Category set to settings Status changed from Unreviewed to Ready for Documentation Keywords set to vardir rundir statedir #8 UPDATED BY JO RHETT 3 MONTHS AGO Just a reminder that this is not solved in 3.3.2 and out of the box mcollective cannot see the puppet classes. Add Comment
Jira (PUP-1371) puppet cannot manage agent or master after update to puppet 3.2
Title: Message Title Jo Rhett commented on an issue Re: puppet cannot manage agent or master after update to puppet 3.2 Also please adjust the reporter to be me. Add Comment Puppet / PUP-1371 puppet cannot manage agent or master after update to puppet 3.2 When puppet is configured to manage it's own services it fails, due to broken init scripts for EL6 Notice: /Stage[main]/Puppet::Server/Service[puppetmaster]/ensure: ensure changed 'stopped' to 'running' Info: /Stage[main]/Puppet::Server/Service[puppetmaster]: Unscheduling refresh on Service[puppetmaster] Notice: /Stage[main]/Puppet/Service[pup... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1371) puppet cannot manage agent or master after update to puppet 3.2
Title: Message Title
Jo Rhett commented on an issue
Re: puppet cannot manage agent or master after update to puppet 3.2
I'd like to note that this problem remains. If someone needs to manage the puppet.conf file (e.g. EVERYONE) then you need to put something ridiculous like this in there:
<% if( scope.lookupvar('::osfamily') == 'RedHat' ) then -%>
rundir = /var/run/puppet
<% end -%>
Well, either that or punch a bunch of settings into Hiera based on operating system. This is a workaround that requires the end customer to bridge the gap between the product as shipped and the default init scripts for the operating system. It's pretty much a guaranteed problem for any heterogenous environment at least once.
One would think we can do better.
Add Comment
Puppet / PUP-1371
puppet cannot manage agent or master after update to puppet 3.2
When puppet is configured to manage it's own services it fails, due to broken init scripts for EL6 Notice: /Stage[main]/Puppet::Server/Service[puppetmaster]/ensure: ensure changed 'stopped' to 'running' Info: /Stage[main]/Puppet::Server/Service[puppetmaster]: Unscheduling refresh on Service[puppetmaster] Notice: /Stage[main]/Puppet/Service[pup...
