Skip to main content

debian - systemd does not notice apache starts

itemprop="text">

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

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able