Error executing action `start` on resource 'service[apache2]' on CentOS7

[sous-chefs]

Error executing action `start` on resource 'service[apache2]' on CentOS7

[drpebcak]

@fletchowns what version of apache is getting installed? Does CentOS 7 try to install apache2.4? If so, try the COOK-3900 branch. While that doesn't specifically support CentOS 7, it does support apache2.4 through the ['apache']['version'] attribute.

[fletchowns]

Yup looks like CentOS 7 installs Apache 2.4.

I tried the COOK-3900 branch (and set ['apache']['version'] to 2.4) and ran into a different issue that I filed as #162.

After working around that one I ran into a slightly different issue:

[2014-07-14T22:07:56-04:00] INFO: template[/etc/sysconfig/httpd] sending restart action to service[apache2] (delayed)

================================================================================
Error executing action `restart` on resource 'service[apache2]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of /sbin/service httpd restart && sleep 1 ----
STDOUT:
STDERR: Redirecting to /bin/systemctl restart  httpd.service
Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
---- End output of /sbin/service httpd restart && sleep 1 ----
Ran /sbin/service httpd restart && sleep 1 returned 1

Resource Declaration:
---------------------
# In /tmp/vagrant-chef-1/chef-solo-1/cookbooks/apache2/recipes/default.rb

[drpebcak]

I'm going to close this one in favor of #162 then.

[drpebcak]

Err.. wait I see this is a different issue. We'll keep them both open for now.

[svanzoest]

As @drpebcak points out it looks like on centos7 it uses the provided mod_systemd to enable tighter integration with systemd service provider. mod_systemd is pulled into to the mainline and would be generally available as part of what looks to be 2.5.0.

[drpebcak]

[2014-07-29T22:40:48+00:00] ERROR: package[mod_python] (apache2::mod_python line 28) had an error: Chef::Exceptions::Package: No version specified, and no candidate version available for mod_python

Recipe: apache2::mod_python
         * package[mod_python] action install[2014-07-29T22:40:37+00:00] INFO: Processing package[mod_python] action install (apache2::mod_python line 28)

           * No version specified, and no candidate version available for mod_python

       ================================================================================
       Error executing action `install` on resource 'package[mod_python]'
       ================================================================================


       Chef::Exceptions::Package
       -------------------------
       No version specified, and no candidate version available for mod_python


       Resource Declaration:
       ---------------------
       # In /tmp/kitchen/cookbooks/apache2/recipes/mod_python.rb

        28:   package 'mod_python' do
        29:     notifies :run, 'execute[generate-module-list]', :immediately
        30:   end
        31: end



       Compiled Resource:
       ------------------
       # Declared in /tmp/kitchen/cookbooks/apache2/recipes/mod_python.rb:28:in `from_file'

       package("mod_python") do
         action :install
         retries 0
         retry_delay 2
         guard_interpreter :default
         package_name "mod_python"
         cookbook_name :apache2
         recipe_name "mod_python"
       end

[drpebcak]

This is actually fixed already in the main cookbook - 02b202c.

The mod_python error comes from our test cookbook - and it doesn't appear that the rhel/fedora platform_family has a package for that with apache2.4. In this case, we simply won't test/support its usage.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.