puppetlabs / puppetlabs-apache

Puppet module for the Apache httpd server, maintained by Puppet, Inc.
https://forge.puppet.com/modules/puppetlabs/apache
Apache License 2.0
365 stars 1.08k forks source link

Applying module from manifest using mcollective set .load files wrong #179

Closed enorasec closed 2 years ago

enorasec commented 11 years ago

When using the command mco puppet runonce --wi computername from an mcollective server, the .load files do not get set right and apache is unable to start. The error from apache is Starting httpd: httpd: Syntax error on line 139 of /etc/httpd/conf/httpd.conf: Syntax error on line 1 of /etc/httpd/mod.d/actions.load: Cannot load /var/lib/puppet/lib/facter:/var/lib/puppet/facts into server: /var/lib/puppet/lib/facter:/var/lib/puppet/facts: cannot open shared object file: No such file or directory

Actions.load file is as follows: LoadModule actions_module /var/lib/puppet/lib/facter:/var/lib/puppet/facts

BUT when the puppet agent is run on the machine itself with the command puppet agent --no-daemonize --debug the .load files get set right and apache is able to start without issues.

The environment is CentOS 6.2 Final 64-bit with Apache/2.2.15

hunner commented 11 years ago

Interesting. That content would have been created by apache::mod { 'actions': } and line https://github.com/puppetlabs/puppetlabs-apache/blob/master/manifests/mod.pp#L48 though I don't see any way that using mco puppetd runonce would cause the values for that line to be set to what you're seeing.

What version of mco & puppet are you using?

apenney commented 10 years ago

Are you still seeing this problem?

chelnak commented 2 years ago

Hello! We are doing some house keeping and noticed that this issue has been open for a long time.

We're going to close it but please do raise another issue if the issue still persists. 😄