systemd issue after upgrade - httpd.service ( systemd service start timeout )

shanti

Verified User
Joined
Apr 8, 2009
Messages
94
Location
Wien / Vienna - Austria
Hi,

I had an issue with httpd.service after upgrading to apache 2.4.23

Code:
-apache2.4:2.4.20:e725c268624737a163dc844e28f720d1
+apache2.4:2.4.23:b711ea7d8b75dc8bfdf5a5d7e5253088

the httpd.service stuck in "activating"-state and failed failed due to a timeout after about 90seconds

i noticed absurd behaviour and in the end even a hang in systemd and had to reboot .. anyway

For anyone find the following useful - i bring the final results:

the httpd.service template changed during the apache-upgrade .. i had to customize the /usr/local/directadmin/custombuild/custom/systemd/httpd.service -file to end the tragedy

Code:
# httpd binary startup for DirectAdmin servers
# To specify environment options, please use 
# environment line in [Service] like:
#	[Service]
#	Environment=OPTIONS=-DMY_DEFINE

# To reload systemd daemon after changes to this file:
# systemctl --system daemon-reload

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

[Service]
Type=[B]forking[/B]
Environment=LANG=C

ExecStartPre=/bin/bash -c "for i in `/usr/bin/ipcs -s | /usr/bin/awk '/apache/ {print     $2}'`; do /usr/bin/ipcrm -s $i; done"
[B]ExecStart=/usr/sbin/apachectl start
ExecReload=/usr/sbin/apachectl graceful
ExecStop=/usr/sbin/apachectl stop[/B]
# We want systemd to give httpd some time to finish gracefully, but still want
# it to kill httpd after TimeoutStopSec if something went wrong during the
# graceful stop. Normally, Systemd sends SIGTERM signal right after the
# ExecStop, which would kill httpd. We are sending useless SIGCONT here to give
# httpd time to finish.
KillSignal=SIGCONT
TimeoutStopSec=7s
PrivateTmp=true

LimitMEMLOCK=infinity
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target



deal:

Code:
systemctl daemon-reload



.p
 
Last edited:
Back
Top