You are not logged in.

#1 2012-12-16 17:12:58

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

[SOLVED] systemd switchover - httpd.service always fails

I have finally moved my home server over to systemd (last night) and spent today enabling all relevant daemons and services and rebooting.
I'm now faced with a number of issues, including a slowdown of the system and SSH login (gone from 1-2 seconds login to ~15 seconds to login)

I will created separate threads for each issue / service.

httpd.service always fails to start

httpd.service - Apache Web Server
	  Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
	  Active: failed (Result: timeout) since Sun, 2012-12-16 16:23:18 GMT; 12s ago
	 Process: 2089 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/httpd.service

Dec 16 16:23:18 kphmsrv systemd[1]: Failed to start Apache Web Server.
Dec 16 16:23:18 kphmsrv systemd[1]: Unit httpd.service entered failed state

When I manually start the service (using sudo) the terminal halts for about 30 seconds, httpd does work (navigating to web page successfully), then everything fails and I get:

sudo systemctl start httpd.service
[sudo] password for kaipee: 
Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.

Now what I find astonishing is that if I manually start httpd everything works perfectly (including SSL) and the httpd.service shows as failed:

[kaipee@kphmsrv ~]$ sudo httpd
[sudo] password for kaipee: 
[kaipee@kphmsrv ~]$ sudo systemctl status httpd.service
httpd.service - Apache Web Server
	  Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
	  Active: failed (Result: timeout) since Sun, 2012-12-16 16:40:04 GMT; 37min ago
	 Process: 533 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/httpd.service

Dec 16 16:40:04 kphmsrv systemd[1]: Failed to start Apache Web Server.
Dec 16 16:40:04 kphmsrv systemd[1]: Unit httpd.service entered failed state

Last edited by kaipee (2012-12-18 16:04:41)

Offline

#2 2012-12-16 22:23:58

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

Re: [SOLVED] systemd switchover - httpd.service always fails

Can anybody please post the contents of their /usr/lib/systemd/system/httpd.service file so I can check

[Unit]
Description=Apache Web Server
After=network.target remote-fs.target nss-lookup.target

[Service]
Type=forking
PIDFile=/run/httpd/httpd.pid
ExecStart=/usr/sbin/apachectl start
ExecStop=/usr/sbin/apachectl graceful-stop
ExecReload=/usr/sbin/apachectl graceful
PrivateTmp=true
LimitNOFILE=infinity

[Install]
WantedBy=multi-user.target

Offline

#3 2012-12-16 22:37:09

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

Re: [SOLVED] systemd switchover - httpd.service always fails

As you can see here, the service does seem to run upon initial boot up but only lasts for around 1 minute:

[kaipee@kphmsrv ~]$ sudo systemctl status httpd.service
[sudo] password for kaipee: 
httpd.service - Apache Web Server
	  Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
	  Active: activating (start) since Sun, 2012-12-16 22:34:02 GMT; 43s ago
	 Process: 624 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/httpd.service
		  ├─734 /usr/sbin/httpd -k start
		  ├─743 /usr/sbin/httpd -k start
		  ├─744 /usr/sbin/httpd -k start
		  ├─745 /usr/sbin/httpd -k start
		  ├─746 /usr/sbin/httpd -k start
		  ├─747 /usr/sbin/httpd -k start
		  ├─748 /usr/sbin/httpd -k start
		  └─759 /usr/sbin/httpd -k start

[kaipee@kphmsrv ~]$ sudo systemctl status httpd.service
httpd.service - Apache Web Server
	  Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
	  Active: failed (Result: timeout) since Sun, 2012-12-16 22:35:32 GMT; 2s ago
	 Process: 624 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/httpd.service

Dec 16 22:35:32 kphmsrv systemd[1]: Failed to start Apache Web Server.
Dec 16 22:35:32 kphmsrv systemd[1]: Unit httpd.service entered failed state

Offline

#4 2012-12-17 00:28:30

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: [SOLVED] systemd switchover - httpd.service always fails

It does sound the background is routed in something else wrong with your systemd migration, but I can't give you a hint. Maybe start troubleshooting like this after a fresh reboot

sudo systemctl --failed 

As you ask in post #2, I have made a diff of your httpd.service file against the one in ABS (pacman -S abs) and they are the same.

Offline

#5 2012-12-17 10:38:59

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

Re: [SOLVED] systemd switchover - httpd.service always fails

I'll have to look into this later when I get home.

I just logged in via SSH (from work) and rebooted the machine - now I cannot get SSH access again hmm

Offline

#6 2012-12-17 17:40:08

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

Re: [SOLVED] systemd switchover - httpd.service always fails

Ugh wtf is going on with this machine?

Apparently nothing has failed even though httpd,service failed to load

[kaipee@kphmsrv ~]$ sudo systemctl --failed --all
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
[kaipee@kphmsrv ~]$ sudo systemctl status httpd.service
httpd.service - Apache Web Server
	  Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
	  Active: failed (Result: timeout) since Mon, 2012-12-17 17:38:49 GMT; 16s ago
	 Process: 622 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/httpd.service

Dec 17 17:38:49 kphmsrv systemd[1]: Unit httpd.service entered failed state

Offline

#7 2012-12-18 12:38:18

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

Re: [SOLVED] systemd switchover - httpd.service always fails

IGNORE THIS  ( /var/run/httpd had been removed somehow - recreating directory means I can manually start httpd again )

Just logged in to try to do some debugging and now I'm getting all sorts of weird issues. apachectl and httpd will not even start manually now (yes after a reboot) and nothing is using ports 80 8080

[kaipee@kphmsrv ~]$ apachectl start
(13)Permission denied: make_sock: could not bind to address [::]:80
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
[kaipee@kphmsrv ~]$ sudo systemctl status httpd.service
httpd.service - Apache Web Server
	  Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
	  Active: failed (Result: exit-code) since Tue, 2012-12-18 12:22:49 GMT; 13min ago
	 Process: 550 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/httpd.service

Dec 18 12:22:49 kphmsrv systemd[1]: Failed to start Apache Web Server.
Dec 18 12:22:49 kphmsrv systemd[1]: Unit httpd.service entered failed state
[kaipee@kphmsrv ~]$ sudo netstat -tulpn | grep :80
tcp        0      0 0.0.0.0:8085            0.0.0.0:*               LISTEN      552/python2         
tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      716/python2         
[kaipee@kphmsrv ~]$ sudo netstat -tulpn | grep :8080
[kaipee@kphmsrv ~]$

Last edited by kaipee (2012-12-18 13:24:24)

Offline

#8 2012-12-18 13:04:56

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

Re: [SOLVED] systemd switchover - httpd.service always fails

IGNORE THIS  ( /var/run/httpd had been removed somehow - recreating directory means I can manually start httpd again )

Have just tried to reinstall apache, which also installed a new httpd.service file. Still having the same issue

[kaipee@kphmsrv ~]$ sudo pacman -Syu apache
:: Synchronising package databases...
 core is up to date
 extra is up to date
 community is up to date
warning: apache-2.2.23-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (1): apache-2.2.23-1

Total Installed Size:   4.85 MiB
Net Upgrade Size:       0.00 MiB

Proceed with installation? [Y/n] 
(1/1) checking package integrity                                                      [#################################################] 100%
(1/1) loading package files                                                           [#################################################] 100%
(1/1) checking for file conflicts                                                     [#################################################] 100%
(1/1) checking available disk space                                                   [#################################################] 100%
(1/1) upgrading apache                                                                [#################################################] 100%
[kaipee@kphmsrv ~]$ sudo systemctl start httpd.service
Warning: Unit file of httpd.service changed on disk, 'systemctl --system daemon-reload' recommended.
Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
[kaipee@kphmsrv ~]$ sudo systemctl --system daemon-reload
[kaipee@kphmsrv ~]$ sudo systemctl start httpd.service
Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
[kaipee@kphmsrv ~]$ sudo systemctl status httpd.service
httpd.service - Apache Web Server
	  Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
	  Active: failed (Result: exit-code) since Tue, 2012-12-18 12:59:27 GMT; 19s ago
	 Process: 1423 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/httpd.service

Dec 18 12:59:27 kphmsrv systemd[1]: Failed to start Apache Web Server.
Dec 18 12:59:27 kphmsrv systemd[1]: Unit httpd.service entered failed state

Here is my /etc/httpd/conf/httpd.conf file

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "/etc/httpd"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 192.168.0.10:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
LoadModule substitute_module modules/mod_substitute.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule log_forensic_module modules/mod_log_forensic.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule ssl_module modules/mod_ssl.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule cgid_module modules/mod_cgid.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule php5_module modules/libphp5.so

AddHandler php5-script php

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User http
Group http

</IfModule>
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin {removed}

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName {removed}:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/srv/http"

# Compress all files before sending
#
<Location />
 
     # Insert filter
     SetOutputFilter DEFLATE
 
     # Netscape 4.x has some problems...
     BrowserMatch ^Mozilla/4 gzip-only-text/html
 
     # Netscape 4.06-4.08 have some more problems
     BrowserMatch ^Mozilla/4\.0[678] no-gzip
 
     # MSIE masquerades as Netscape, but it is fine
     BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
 
     # Don't compress images
     SetEnvIfNoCase Request_URI \
       \.(?:gif|jpe?g|png)$ no-gzip dont-vary
 
 
     # Make sure proxies don't deliver the wrong content
     Header append Vary User-Agent env=!dont-vary
 
</Location>

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory />
    Options -Indexes SymLinksIfOwnerMatch IncludesNoExec
    AllowOverride None
    Order deny,allow
    Deny from all

    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/srv/http">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks Includes

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride All

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

    # Allow open_basedir acces from /srv/http
#    php_admin_value open_basedir "/srv/http:/usr/share/webapps:/tmp:/mnt/Files/owncloud"
    php_admin_value open_basedir "none"

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "/var/log/httpd/error_log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "/var/log/httpd/access_log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "/var/log/httpd/access_log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock /var/run/httpd/cgisock
</IfModule>

#
# "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
Include conf/extra/httpd-autoindex.conf

# Language settings
Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#

# Load PHP5 modules
Include conf/extra/php5_module.conf

# phpMyAdmin configuration
Include conf/extra/httpd-phpmyadmin.conf

# MediaWiki configuration
Include /etc/webapps/mediawiki/httpd-mediawiki.conf

<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

# OwnCloud configuration
Include /etc/httpd/conf/extra/owncloud.conf

# Subsonic configuration
Include /etc/webapps/subsonic/http-subsonic.conf

Last edited by kaipee (2012-12-18 13:24:16)

Offline

#9 2012-12-18 13:50:25

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

Re: [SOLVED] systemd switchover - httpd.service always fails

I have now got a fresh reinstall of apache
New (latest) httpd.service file installed
systemctl still does not recognise that httpd is running
manually start sudo httpd or sudo apachectl start works perfectly

/usr/lib/systemd/system/httpd.service

[Unit]
Description=Apache Web Server
After=network.target remote-fs.target nss-lookup.target

[Service]
Type=forking
PIDFile=/run/httpd/httpd.pid
ExecStart=/usr/sbin/apachectl start
ExecStop=/usr/sbin/apachectl graceful-stop
ExecReload=/usr/sbin/apachectl graceful
PrivateTmp=true
LimitNOFILE=infinity

[Install]
WantedBy=multi-user.target

attempting start using systemctl

[kaipee@kphmsrv ~]$ sudo systemctl start httpd.service
Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.

httpd error_log

[Tue Dec 18 13:41:26 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Dec 18 13:41:26 2012] [notice] Digest: generating secret for digest authentication ...
[Tue Dec 18 13:41:26 2012] [notice] Digest: done
[Tue Dec 18 13:41:27 2012] [notice] Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.1c DAV/2 PHP/5.4.9 configured -- resuming normal operatio$
[Tue Dec 18 13:43:12 2012] [notice] caught SIGTERM, shutting down

Offline

#10 2012-12-18 15:19:20

Painless
Member
Registered: 2006-02-06
Posts: 211

Re: [SOLVED] systemd switchover - httpd.service always fails

Please would you display the output of:

journalctl -xn
systemctl list-units --type=target

and

sudo /usr/sbin/apachectl configtest

?

Offline

#11 2012-12-18 16:04:15

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 214

Re: [SOLVED] systemd switchover - httpd.service always fails

I got this sorted myself.
Turns out my systemd migration didn't go well and /var/run wasn't symlinked to /run

(found this out by changing httpd.service file PIDFile=/run/httpd/httpd.pid to PIDFile=/var/run/httpd/httpd.pid)

Followed https://www.archlinux.org/news/filesyst … equired-1/ and httpd is now working fine after a reinstall of apache

Offline

Board footer

Powered by FluxBB