使用Puppet在Ubuntu安装Apache相关问题求助

Hey there, let's walk through some common checks to troubleshoot your Apache Puppet setup since you mentioned hitting issues when verifying the configuration.

1. Validate the Apache Module Installation & Source Config #

First up, confirm that the custom Apache module from your Git repo is properly installed on your Puppet agent/master. Run this command to list installed modules:

puppet module list

Look for the apache module linked to ssh://git.*.*.com:7999/xyz/jira-apache-puppet-module.git in the output. If it's missing, install it manually with:

puppet module install apache --git ssh://git.*.*.com:7999/xyz/jira-apache-puppet-module.git --ref master

Also, double-check your puppet.conf entry: make sure it's placed in the correct section (usually [main] or [master] depending on your setup) and there are no typos in the Git URL or master ref.

2. Dig Into Puppet Run Logs #

Puppet's logs will give you the clearest clues about what's going wrong. On Ubuntu, agent logs live at /var/log/puppetlabs/puppet/puppet-agent.log, and master logs are at /var/log/puppetlabs/puppetserver/puppetserver.log. Look for red flags like:

• Module not found errors
• Permission issues accessing the Git repo
• Syntax or validation errors in your Apache class declaration

Run a manual Puppet agent run to capture real-time output and spot issues immediately:

puppet agent -t

Pay close attention to any error lines or warnings—they'll point you straight to the root problem.

3. Verify Your Apache Class Parameter Compatibility #

Let's break down your class declaration:

class{ 'apache': 
  docroot => '/var/www', # ubu default, ignored
  default_vhost => false,
  default_ssl_vhost => false,
  service_enable => false, # Do not start at boot
  service_ensure => stopped, # Apache should be stopped if puppet runs
}

• Even though you noted docroot is ignored, confirm the custom module actually skips validating this parameter (some modules still enforce parameter checks regardless of comments).
• Check if the module supports service_enable and service_ensure exactly as you've written them. Some Puppet modules use different parameter names (like enable instead of service_enable). You can cross-reference this by checking the module's README or core manifest files.

4. Check System-Level Apache Service State #

Since you set service_ensure => stopped, verify if Apache is in the expected state:

systemctl status apache2

If it's running when it shouldn't be, Puppet might not have applied the change—this could stem from a dependency conflict in the module, a bug in the custom module code, or permission issues preventing Puppet from modifying the service state.

If you can share the specific error message or unexpected behavior you're seeing (like Apache failing to install, service state not matching your config, or Puppet run failures), we can narrow this down even further!

内容的提问来源于stack exchange，提问作者Sarath S