Skip to main content

debian - systemd does not notice apache starts



My debian-system has been infected with the systemd-virus...



When I issue the "service apache2 start" command to start apache, it thinks it failed, but apache is running just fine.
So "service apache2 stop" does nothing, because system thinks apache has not started. To stop apache, I have to issue "killall apache2" 



# service apache2 start
Job for apache2.service failed. See 'systemctl status apache2.service' 

   and 'journalctl -xn' for details.


# systemctl status apache2.service 
รข apache2.service - LSB: Apache2 web server
   Loaded: loaded (/etc/init.d/apache2)
   Active: failed (Result: exit-code) since Thu 2016-06-09 15:49:43 CEST; 32s ago
  Process: 7513 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)

Jun 09 15:49:43  apache2[7513]: Starting web server: apache2 failed!

Jun 09 15:49:43  apache2[7513]: The apache2 instance did not start within 20 seconds. Please read the log files to discover problems ... (warning).
Jun 09 15:49:43  systemd[1]: apache2.service: control process exited, code=exited status=1
Jun 09 15:49:43  systemd[1]: Failed to start LSB: Apache2 web server.
Jun 09 15:49:43  systemd[1]: Unit apache2.service entered failed state.


The system is debian 8.5; upgraded through many versions.



Why does "system" think it failed, when apache is started just fine?




[Thu Jun 09 16:11:40.945575 2016] [mpm_prefork:notice] [pid 13426] AH00163: Apache/2.4.10 (Debian) mod_python/3.3.1 Python/2.7.9 OpenSSL/1.0.1t configured -- resuming normal operations
[Thu Jun 09 16:11:40.945846 2016] [core:notice] [pid 13426] AH00094: Command line: '/usr/sbin/apache2'


UPDATE
The /etc/init.d/apache2 looks for a pidfile at 

/var/run/apache2/apache2.pid
, but the file actually is at 
/var/run/apache2.pid
, i.e. a subdir less.

Answer



The pidfile was in an unexpected place.
Editing 

/etc/apache2/envvars
the line


export APACHE_PID_FILE=/var/run/apache2$SUFFIX.pid


made the "service apache2 start/stop" work


Comments

Post a Comment

Popular posts from this blog

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)
Post a Comment
Read more

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...
Post a Comment
Read more

linux - How can I get my mediawiki to stop thinking I have cookies disabled?

I've searched half a day for how to resolve this issue, and can't figure it out. Shortly after I made my wiki a simple private wiki according to the instructions at Mediawiki's website, it started giving me this weird login error message: Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. If I remove those private wiki settings, the error disappears, even if I try logging in. But I need it to be a private wiki for only my team. So what do I do? Here's what I've done so far. Just to be safe, after ever change, I try rebooting Apache using: sudo /etc/init.d/apache2 restart In my php.ini file, I have the following set: session.save_path = "/var/lib/php5" session.cookie_secure = secure session.cookie_path = /tmp session.cookie_domain = my server's internal URL (should I even set this? this field was blank before, but not commented out) session.referer_check = Off I ran the following to ensure that the fold...
Post a Comment
Read more