Issue #2774 has been updated by Florian Wagner.
I've digged a bit deeper. It's not that the [puppetmasterd] section from puppet.conf doesn't get read, but my node_termius = exec in the config is ignored. My config.ru is now: <pre> $0 = "puppetmasterd" ARGV << "--rack" ARGV << "--node_terminus" << "exec" require 'puppet/application/puppetmasterd' run Puppet::Application[:puppetmasterd].run </pre> and my puppet.conf: <pre> [main] logdir = /var/log/puppet vardir = /var/lib/puppet ssldir = /var/lib/puppet/ssl rundir = /var/run/puppet factpath = $vardir/lib/facter pluginsync = true [puppetd] certname = aurepo1.syscomp.de server = puppet.syscomp.de report = true listen = true [puppetmasterd] manifestdir = /var/syscomp/puppet.deploy/manifests templatedir = /var/syscomp/puppet.deploy/templates modulepath = /var/syscomp/puppet.deploy/modules certname = puppet.syscomp.de reports = tagmail,store external_nodes = /var/syscomp/pino.deploy/manage.py classify node_terminus = exec </pre> If I comment out the ARGV << "--node_terminus" << "exec" line the puppet clients produce errors as if they can't find any modules: <pre> info: Loading fact raidctrl notice: Ignoring --listen on onetime run info: Retrieving plugins err: /File[/var/lib/puppet/lib]: Failed to generate additional resources during transaction: None of the provided sources exist err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of resource: No specified source was found from puppet://puppet.syscomp.de/plugins info: Loading fact raidctrl err: Could not retrieve catalog: Could not parse for environment production: No file(s) found for import of 'apt' at /var/syscomp/puppet.deploy/manifests/modules.pp:2 warning: Not using cache on failed catalog </pre> With the line everything works as expected. ---------------------------------------- Bug #2774: puppetmasterd with Passenger doesn't read puppet.conf correctly http://projects.reductivelabs.com/issues/2774 Author: Florian Wagner Status: Investigating Priority: Normal Assigned to: Christian Hofstaedtler Category: passenger Target version: 0.25.2 Affected version: 0.25.1 Keywords: Branch: After switching to puppet 0.25.1 and modifying my Apache/Passenger/puppetmasterd config according to http://github.com/reductivelabs/puppet/tree/master/ext/rack the resulting puppetmasterd setup doesn't seem to read the [puppetmasterd] section of the config. At least it doesn't use my custom modulepath, manifestdir and external_nodes config. As a workaround I had to migrate these settings to my config.ru (ARGV << "--manifestdir" << "..." and so on). -- 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://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
