The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #4952

Client errors while master is reparsing puppet.conf

Added by Alan Harder over 3 years ago. Updated over 1 year ago.

Status:AcceptedStart date:10/06/2010
Priority:HighDue date:
Assignee:-% Done:

0%

Category:plumbing
Target version:-
Affected Puppet version:2.6.1 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

Our puppet.conf files are managed by puppet, and the puppetmaster is also a client of itself. Every 6 hours (our run interval) the puppetmaster updates itself, and even when no content changes are made to puppet.conf its timestamp is updated, resulting in a “Reparsing /etc/puppet/puppet.conf” notice in /var/adm/messages.

If other clients are accessing the puppetmaster right at this time, they can get errors.. some examples:

Oct  5 09:40:19 nse-t1000-4 puppet-master[4356]: [ID 702911 daemon.notice] Reparsing /etc/puppet/puppet.conf
Oct  5 09:43:02 nse-t1000-4 puppet-master[4356]: [ID 702911 daemon.error] Could not autoload regsubst: Function regsubst already defined at /etc/puppet/manifests/nodes.pp:1 on node {...}
Oct  5 09:43:02 nse-t1000-4 last message repeated 1 time
Oct  5 09:43:03 nse-t1000-4 puppet-master[4356]: [ID 702911 daemon.error] Could not autoload inline_template: Function inline_template already defined at /etc/puppet/modules/configs/manifests/init.pp:18 on node {...}
Oct  6 15:45:15 nse-t1000-4 puppet-master[4356]: [ID 702911 daemon.notice] Reparsing /etc/puppet/puppet.conf
Oct  6 15:45:28 nse-t1000-4 puppet-master[4356]: [ID 702911 daemon.error] Could not find class configs at /etc/puppet/manifests/site.pp:7 on node {...}
Oct  6 15:45:28 nse-t1000-4 last message repeated 1 time
Oct  6 15:45:28 nse-t1000-4 puppet-master[4356]: [ID 702911 daemon.error] Could not find class configs at /etc/puppet/manifests/site.pp:7 on node {...}
Oct  6 15:45:28 nse-t1000-4 last message repeated 1 time

Related issues

Related to Puppet - Bug #4808: Intermittent "Could not retrieve catalog from remote serv... Accepted 09/21/2010

History

#1 Updated by Alan Harder over 3 years ago

  • Affected Puppet version set to 2.6.1

#2 Updated by Markus Roberts over 3 years ago

  • Status changed from Unreviewed to Accepted

There may be multiple issues here:

  • The timestamp changing when no content changes were made
  • The thread safety issue implied by changes “mid compile” causing errors
  • One or more possible regressions if this is newly observed in 2.6.x

Some of these may be addressed by changes in the queue for 2.7 but I doubt all of them are.

#3 Updated by Markus Roberts over 3 years ago

  • Priority changed from Normal to High
  • Target version set to 69

#4 Updated by Nigel Kersten over 3 years ago

  • Target version changed from 69 to 2.7.x

#5 Updated by Andrew Parker over 1 year ago

  • Target version deleted (2.7.x)

#6 Updated by Andrew Parker over 1 year ago

As the 2.7.x line is winding down, I am removing the target at 2.7.x from tickets in the system. The 2.7 line should only receive fixes for major problems (crashes, for instance) or security problems.

Also available in: Atom PDF