Following a yum update /bin/systemctl start httpd.service times out

Issues related to applications and software problems
czg
Posts: 12
Joined: 2017/01/25 15:04:15

Following a yum update /bin/systemctl start httpd.service times out

Postby czg » 2018/01/24 15:50:08

I have just run yum update -y which successfully installed/upgraded 90 packages, including httpd-2.4.6-67.el7.centos.6.x86_64.rpm on a 1 cpu Centos 7 VM.

Following the upgrade apache fails to restart using the standard mechanism, with the processes starting OK, running for 60 seconds (serving traffic in that time) then being killed.

Code: Select all

[root@hostname ~]# /bin/systemctl start httpd.service
Job for httpd.service failed because a fatal signal was delivered to the control process. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@hostname ~]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Wed 2018-01-24 14:53:11 GMT; 13s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 21226 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=killed, signal=KILL)
 Main PID: 21226 (code=killed, signal=KILL)
   Status: "Total requests: 1; Current requests/sec: 0; Current traffic:   0 B/sec"

Jan 24 14:50:10 <hostname> systemd[1]: Starting The Apache HTTP Server...
Jan 24 14:51:40 <hostname> systemd[1]: httpd.service start operation timed out. Terminating.
Jan 24 14:53:11 <hostname> systemd[1]: httpd.service stop-final-sigterm timed out. Killing.
Jan 24 14:53:11 <hostname> systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL
Jan 24 14:53:11 <hostname> systemd[1]: Failed to start The Apache HTTP Server.
Jan 24 14:53:11 <hostname> systemd[1]: Unit httpd.service entered failed state.
Jan 24 14:53:11 <hostname> systemd[1]: httpd.service failed.
[root@hostname ~]# journalctl -xe
Jan 24 14:53:23 <hostname> sshd[21277]: Accepted publickey for webowner from 172.21.1.6 port 44146 ssh2: DSA SHA256:dHhG7lBu1zLGNRuGhkpMcdMz5KMjNkiro08TNoVqATM
Jan 24 14:53:23 <hostname> sshd[21279]: Accepted publickey for webowner from 172.21.1.6 port 44148 ssh2: DSA SHA256:dHhG7lBu1zLGNRuGhkpMcdMz5KMjNkiro08TNoVqATM
Jan 24 14:53:23 <hostname> systemd[1]: Started Session 59714 of user webowner.
-- Subject: Unit session-59714.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-59714.scope has finished starting up.
--
-- The start-up result is done.
Jan 24 14:53:23 <hostname> sshd[21277]: pam_unix(sshd:session): session opened for user webowner by (uid=0)
Jan 24 14:53:23 <hostname> systemd-logind[603]: New session 59714 of user webowner.
-- Subject: A new session 59714 has been created for user webowner
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 59714 has been created for the user webowner.
--
-- The leading process of the session is 21277.
Jan 24 14:53:23 <hostname> systemd[1]: Starting Session 59714 of user webowner.
-- Subject: Unit session-59714.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-59714.scope has begun starting up.
Jan 24 14:53:23 <hostname> systemd[1]: Started Session 59715 of user webowner.
-- Subject: Unit session-59715.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-59715.scope has finished starting up.
--
-- The start-up result is done.
Jan 24 14:53:23 <hostname> sshd[21279]: pam_unix(sshd:session): session opened for user webowner by (uid=0)
Jan 24 14:53:23 <hostname> systemd-logind[603]: New session 59715 of user webowner.
-- Subject: A new session 59715 has been created for user webowner
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 59715 has been created for the user webowner.
--
-- The leading process of the session is 21279.
Jan 24 14:53:23 <hostname> systemd[1]: Starting Session 59715 of user webowner.
-- Subject: Unit session-59715.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-59715.scope has begun starting up.
Jan 24 14:53:23 <hostname> sshd[21286]: Received disconnect from 172.21.1.6 port 44146:11: disconnected by user
Jan 24 14:53:23 <hostname> sshd[21286]: Disconnected from 172.21.1.6 port 44146
Jan 24 14:53:23 <hostname> sshd[21277]: pam_unix(sshd:session): session closed for user webowner
Jan 24 14:53:23 <hostname> sshd[21287]: Received disconnect from 172.21.1.6 port 44148:11: disconnected by user
Jan 24 14:53:23 <hostname> sshd[21287]: Disconnected from 172.21.1.6 port 44148
Jan 24 14:53:23 <hostname> sshd[21279]: pam_unix(sshd:session): session closed for user webowner


There's noting in the error_log:

Code: Select all

[root@hostname ~]# tail /var/log/httpd/error_log
[Wed Jan 24 13:51:31.154005 2018] [core:warn] [pid 19958] AH00098: pid file /run/httpd/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Wed Jan 24 13:51:31.160877 2018] [mpm_prefork:notice] [pid 19958] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Wed Jan 24 13:51:31.160921 2018] [core:notice] [pid 19958] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Wed Jan 24 13:55:58.270028 2018] [core:notice] [pid 20119] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Wed Jan 24 13:55:58.271974 2018] [suexec:notice] [pid 20119] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Jan 24 13:56:58.376700 2018] [auth_digest:notice] [pid 20119] AH01757: generating secret for digest authentication ...
[Wed Jan 24 13:56:58.378816 2018] [lbmethod_heartbeat:notice] [pid 20119] AH02282: No slotmem from mod_heartmonitor
[Wed Jan 24 13:56:58.393354 2018] [core:warn] [pid 20119] AH00098: pid file /run/httpd/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Wed Jan 24 13:56:58.402410 2018] [mpm_prefork:notice] [pid 20119] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Wed Jan 24 13:56:58.402458 2018] [core:notice] [pid 20119] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'


The httpd conf is OK:

Code: Select all

[root@hostname ~]# service httpd configtest
Syntax OK


I have tried the alternative service file mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=907579 but that didn't help.

I've currently got apache running via a direct call:

Code: Select all

[root@hostname ~]# nohup /usr/sbin/httpd -k start -DFOREGROUND &
[1] 21655


I have not rebooted the server since the upgrade and would rather not as I have a higher profile server next in the queue.

Any suggestions on what I might try next?

hunter86_bg
Posts: 902
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby hunter86_bg » 2018/01/25 05:08:49

Copy your systemd service to '/etc/systemd/system' and change the TimeoutStartSec, TimeoutStopSec or TimeoutSec to something bigger (they might be missing ,if so add any of them /as per your needs/ to the [service] stanza).
Also you can add the 'Environment=SYSTEMD_LOG_LEVEL=debug' (again in [service] stanza), to debug the service.

czg
Posts: 12
Joined: 2017/01/25 15:04:15

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby czg » 2018/01/25 10:57:04

I've got a vanilla /etc/systemd/system directory tree and apache setup:

Code: Select all

[root@hostname ~]# ls -l /etc/systemd/system
total 4
drwxr-xr-x. 2 root root   56 Jul  6  2017 basic.target.wants
lrwxrwxrwx. 1 root root   41 Jul  6  2017 dbus-org.fedoraproject.FirewallD1.service -> /usr/lib/systemd/system/firewalld.service
lrwxrwxrwx. 1 root root   46 Jul  6  2017 dbus-org.freedesktop.NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx. 1 root root   57 Jul  6  2017 dbus-org.freedesktop.nm-dispatcher.service -> /usr/lib/systemd/system/NetworkManager-dispatcher.service
lrwxrwxrwx. 1 root root   37 Jul  6  2017 default.target -> /lib/systemd/system/multi-user.target
drwxr-xr-x. 2 root root   87 Jul  6  2017 default.target.wants
drwxr-xr-x. 2 root root   32 Jul  6  2017 getty.target.wants
drwxr-xr-x. 2 root root 4096 Jul 11  2017 multi-user.target.wants
drwxr-xr-x. 2 root root   29 Jul  6  2017 sockets.target.wants
drwxr-xr-x. 2 root root   89 Jul  6  2017 sysinit.target.wants
drwxr-xr-x. 2 root root   44 Jul  6  2017 system-update.target.wants

[root@hostname ~]# ls -l /etc/systemd/system/multi-user.target.wants
total 0
lrwxrwxrwx. 1 root root 38 Jul  6  2017 auditd.service -> /usr/lib/systemd/system/auditd.service
lrwxrwxrwx. 1 root root 39 Jul  6  2017 chronyd.service -> /usr/lib/systemd/system/chronyd.service
lrwxrwxrwx. 1 root root 37 Jul  6  2017 crond.service -> /usr/lib/systemd/system/crond.service
lrwxrwxrwx. 1 root root 37 Jul 11  2017 httpd.service -> /usr/lib/systemd/system/httpd.service
lrwxrwxrwx. 1 root root 42 Jul  6  2017 irqbalance.service -> /usr/lib/systemd/system/irqbalance.service
lrwxrwxrwx. 1 root root 37 Jul  6  2017 kdump.service -> /usr/lib/systemd/system/kdump.service
lrwxrwxrwx. 1 root root 46 Jul  6  2017 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx. 1 root root 39 Jul  6  2017 postfix.service -> /usr/lib/systemd/system/postfix.service
lrwxrwxrwx. 1 root root 40 Jul  6  2017 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx. 1 root root 39 Jul  6  2017 rsyslog.service -> /usr/lib/systemd/system/rsyslog.service
lrwxrwxrwx. 1 root root 36 Jul  6  2017 sshd.service -> /usr/lib/systemd/system/sshd.service
lrwxrwxrwx. 1 root root 37 Jul  6  2017 tuned.service -> /usr/lib/systemd/system/tuned.service
lrwxrwxrwx. 1 root root 40 Jul  6  2017 vmtoolsd.service -> /usr/lib/systemd/system/vmtoolsd.service

[root@hostname ~]# cat /usr/lib/systemd/system/httpd.service
[Unit]
Description=The Apache HTTP Server
After=network.target remote-fs.target nss-lookup.target
Documentation=man:httpd(8)
Documentation=man:apachectl(8)

[Service]
Type=notify
EnvironmentFile=/etc/sysconfig/httpd
ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
ExecReload=/usr/sbin/httpd $OPTIONS -k graceful
ExecStop=/bin/kill -WINCH ${MAINPID}
# 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
PrivateTmp=true

[Install]
WantedBy=multi-user.target

[webowner@hostname ~]$ egrep -v '^ *(#|$)' /etc/sysconfig/httpd
LANG=C

[webowner@hostname ~]$ egrep -v '^ *(#|$)' /etc/httpd/conf.modules.d/00-mpm.conf
LoadModule mpm_prefork_module modules/mod_mpm_prefork.so


hunter86_bg wrote:Copy your systemd service to '/etc/systemd/system' and change the TimeoutStartSec, TimeoutStopSec or TimeoutSec to something bigger (they might be missing ,if so add any of them /as per your needs/ to the [service] stanza).
Also you can add the 'Environment=SYSTEMD_LOG_LEVEL=debug' (again in [service] stanza), to debug the service.


Thanks for the suggestions, I'm not sure about increasing the timeouts as the service is working fine at the point the current timeout kicks in but enabling debug logging is a good next step.

Is everything where you expect it to be?

Are you recommending I add those entries to /usr/lib/systemd/system/httpd.service?

hunter86_bg
Posts: 902
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby hunter86_bg » 2018/01/25 17:08:02

The idea was to copy the "/usr/lib/systemd/system/httpd.service" to "/etc/systemd/system" ,as the latter is the place for custom services.
Once you copy it , edit the service and add the debug line I have provided in the previous post.I hope that this will provide vital data to find out why the start is timing out.

User avatar
TrevorH
Forum Moderator
Posts: 21771
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby TrevorH » 2018/01/25 17:20:04

Also check your httpd logs in /var/log/httpd and see if it tells you why it went wrong...
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

czg
Posts: 12
Joined: 2017/01/25 15:04:15

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby czg » 2018/02/02 12:10:19

I've tried again with similar results, there isn't much in the /var/log/httpd logs

Code: Select all

[root@hostname ~]# ls -lrt /var/log/httpd | tail
-rw-r--r--. 1 root root     0 Jan 28 03:30 ssl_request_log
-rw-r--r--. 1 root root     0 Jan 28 03:30 ssl_access_log
-rw-r--r--. 1 root root     0 Jan 28 03:30 access_log
-rw-r--r--. 1 root root     0 Feb  1 03:25 ssl_error_log
-rw-r--r--. 1 root root  2108 Feb  1 10:39 ssl_error_log-20180201
-rw-r--r--. 1 root root  9676 Feb  1 10:41 ssl_request_log-20180128
-rw-r--r--. 1 root root  9082 Feb  1 10:41 ssl_access_log-20180128
-rw-r--r--. 1 root root 48679 Feb  1 17:11 access_log-20180128
-rw-r--r--. 1 root root 10039 Feb  2 10:43 error_log-20180128
-rw-r--r--. 1 root root  2907 Feb  2 11:11 error_log
[root@hostname ~]# cat /var/log/httpd/error_log
[Fri Feb 02 10:44:50.458764 2018] [core:notice] [pid 5819] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 10:44:50.460656 2018] [suexec:notice] [pid 5819] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 10:45:50.565947 2018] [auth_digest:notice] [pid 5819] AH01757: generating secret for digest authentication ...
[Fri Feb 02 10:45:50.567748 2018] [lbmethod_heartbeat:notice] [pid 5819] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 02 10:45:50.591777 2018] [mpm_prefork:notice] [pid 5819] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Fri Feb 02 10:45:50.591823 2018] [core:notice] [pid 5819] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Feb 02 10:58:24.418814 2018] [core:notice] [pid 6075] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 10:58:24.421609 2018] [suexec:notice] [pid 6075] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 10:59:24.524339 2018] [auth_digest:notice] [pid 6075] AH01757: generating secret for digest authentication ...
[Fri Feb 02 10:59:24.525948 2018] [lbmethod_heartbeat:notice] [pid 6075] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 02 10:59:24.540125 2018] [core:warn] [pid 6075] AH00098: pid file /run/httpd/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Fri Feb 02 10:59:24.545451 2018] [mpm_prefork:notice] [pid 6075] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Fri Feb 02 10:59:24.545501 2018] [core:notice] [pid 6075] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Feb 02 11:03:24.307932 2018] [core:notice] [pid 6192] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 11:03:24.309941 2018] [suexec:notice] [pid 6192] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 11:10:39.505034 2018] [core:notice] [pid 6411] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 11:10:39.506931 2018] [suexec:notice] [pid 6411] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 11:11:39.608416 2018] [auth_digest:notice] [pid 6411] AH01757: generating secret for digest authentication ...
[Fri Feb 02 11:11:39.610019 2018] [lbmethod_heartbeat:notice] [pid 6411] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 02 11:11:39.624233 2018] [core:warn] [pid 6411] AH00098: pid file /run/httpd/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Fri Feb 02 11:11:39.629192 2018] [mpm_prefork:notice] [pid 6411] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Fri Feb 02 11:11:39.630341 2018] [core:notice] [pid 6411] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[root@hostname ~]# cat /var/log/httpd/error_log-20180128
[Fri Feb 02 10:43:31.263463 2018] [mpm_prefork:notice] [pid 21655] AH00169: caught SIGTERM, shutting down


When I copied the httpd.service file into /etc/stsyemd I got a failure:

Code: Select all

[root@hostname ~]# systemctl status httpd.service
Failed to get properties: Access denied


With StartTimeoutSec=infinity it still timed out, with TimeoutSec=infinity it failed to load.

I had Environment=SYSTEMD_LOG_LEVEL=debug on for a while, but I'm not sure where that would log stuff.

Here's my session:

Code: Select all

[root@hostname ~]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Fri 2018-02-02 10:46:50 GMT; 13s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 5819 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=killed, signal=KILL)
 Main PID: 5819 (code=killed, signal=KILL)
   Status: "Total requests: 0; Current requests/sec: 0; Current traffic:   0 B/sec"

Feb 02 10:43:50 hostname systemd[1]: Starting The Apache HTTP Server...
Feb 02 10:45:20 hostname systemd[1]: httpd.service start operation timed out. Terminating.
Feb 02 10:46:50 hostname systemd[1]: httpd.service stop-final-sigterm timed out. Killing.
Feb 02 10:46:50 hostname systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL
Feb 02 10:46:50 hostname systemd[1]: Failed to start The Apache HTTP Server.
Feb 02 10:46:50 hostname systemd[1]: Unit httpd.service entered failed state.
Feb 02 10:46:50 hostname systemd[1]: httpd.service failed.
[root@hostname ~]# journalctl -xe
-- Subject: A new session 73960 has been created for user webowner
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 73960 has been created for the user webowner.
--
-- The leading process of the session is 5848.
Feb 02 10:45:55 hostname systemd[1]: Starting Session 73960 of user webowner.
-- Subject: Unit session-73960.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73960.scope has begun starting up.
Feb 02 10:45:55 hostname sshd[5848]: pam_unix(sshd:session): session opened for user webowner by (uid=0)
Feb 02 10:46:39 hostname sshd[5878]: Accepted publickey for webowner from 172.21.1.6 port 47330 ssh2: DSA SHA256:dHhG7lBu1zLGNRuGhkpMcdMz5KMjNkiro08TNoVqATM
Feb 02 10:46:40 hostname systemd[1]: Started Session 73961 of user webowner.
-- Subject: Unit session-73961.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73961.scope has finished starting up.
--
-- The start-up result is done.
Feb 02 10:46:40 hostname systemd-logind[603]: New session 73961 of user webowner.
-- Subject: A new session 73961 has been created for user webowner
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 73961 has been created for the user webowner.
--
-- The leading process of the session is 5878.
Feb 02 10:46:40 hostname systemd[1]: Starting Session 73961 of user webowner.
-- Subject: Unit session-73961.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73961.scope has begun starting up.
Feb 02 10:46:40 hostname sshd[5878]: pam_unix(sshd:session): session opened for user webowner by (uid=0)
Feb 02 10:46:40 hostname sshd[5882]: Received disconnect from 172.21.1.6 port 47330:11: disconnected by user
Feb 02 10:46:40 hostname sshd[5882]: Disconnected from 172.21.1.6 port 47330
Feb 02 10:46:40 hostname sshd[5878]: pam_unix(sshd:session): session closed for user webowner
Feb 02 10:46:50 hostname systemd[1]: httpd.service stop-final-sigterm timed out. Killing.
Feb 02 10:46:50 hostname systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL
Feb 02 10:46:50 hostname systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Feb 02 10:46:50 hostname systemd[1]: Unit httpd.service entered failed state.
Feb 02 10:46:50 hostname systemd[1]: httpd.service failed.
Feb 02 10:46:50 hostname polkitd[604]: Unregistered Authentication Agent for unix-process:5813:396312781 (system bus name :1.148140, object path /org/freedesktop/PolicyKit1/Authenticatio
[root@hostname ~]# ls -lrt /var/log/httpd | tail
-rw-r--r--. 1 root root     0 Jan 28 03:30 ssl_request_log
-rw-r--r--. 1 root root     0 Jan 28 03:30 ssl_access_log
-rw-r--r--. 1 root root     0 Jan 28 03:30 access_log
-rw-r--r--. 1 root root     0 Feb  1 03:25 ssl_error_log
-rw-r--r--. 1 root root  2108 Feb  1 10:39 ssl_error_log-20180201
-rw-r--r--. 1 root root  9676 Feb  1 10:41 ssl_request_log-20180128
-rw-r--r--. 1 root root  9082 Feb  1 10:41 ssl_access_log-20180128
-rw-r--r--. 1 root root 48679 Feb  1 17:11 access_log-20180128
-rw-r--r--. 1 root root 10039 Feb  2 10:43 error_log-20180128
-rw-r--r--. 1 root root   781 Feb  2 10:45 error_log
[root@hostname ~]# cat /var/log/httpd/error_log
[Fri Feb 02 10:44:50.458764 2018] [core:notice] [pid 5819] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 10:44:50.460656 2018] [suexec:notice] [pid 5819] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 10:45:50.565947 2018] [auth_digest:notice] [pid 5819] AH01757: generating secret for digest authentication ...
[Fri Feb 02 10:45:50.567748 2018] [lbmethod_heartbeat:notice] [pid 5819] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 02 10:45:50.591777 2018] [mpm_prefork:notice] [pid 5819] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Fri Feb 02 10:45:50.591823 2018] [core:notice] [pid 5819] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[root@hostname ~]# tail /var/log/httpd/error_log-20180128
[Fri Feb 02 10:43:31.263463 2018] [mpm_prefork:notice] [pid 21655] AH00169: caught SIGTERM, shutting down
[root@hostname ~]# vi /etc/systemd/system/httpd.service
[root@hostname ~]# /bin/systemctl start httpd.service
Job for httpd.service failed because a fatal signal was delivered to the control process. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@hostname ~]# mv /usr/lib/systemd/system/httpd.service /usr/lib/systemd/system/httpd.service.nowinsystemd
[root@hostname ~]# /bin/systemctl start httpd.service
Failed to start httpd.service: Access denied
See system logs and 'systemctl status httpd.service' for details.
[root@hostname ~]# systemctl status httpd.service
Failed to get properties: Access denied
[root@hostname ~]# mv /etc/systemd/system/httpd.service /usr/lib/systemd/system/httpd.service
[root@hostname ~]# systemctl daemon-reload
[root@hostname ~]# /bin/systemctl start httpd.service
date
Job for httpd.service failed because a fatal signal was delivered to the control process. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@hostname ~]# date
Fri  2 Feb 11:04:04 GMT 2018
[root@hostname ~]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Fri 2018-02-02 11:04:04 GMT; 1min 8s ago
     Docs: man:httpd(8)
           man:apachectl(8)
 Main PID: 6192 (code=killed, signal=KILL)

Feb 02 11:02:24 hostname systemd[1]: Starting The Apache HTTP Server...
Feb 02 11:02:34 hostname systemd[1]: httpd.service start operation timed out. Terminating.
Feb 02 11:04:04 hostname systemd[1]: httpd.service stop-final-sigterm timed out. Killing.
Feb 02 11:04:04 hostname systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL
Feb 02 11:04:04 hostname systemd[1]: Failed to start The Apache HTTP Server.
Feb 02 11:04:04 hostname systemd[1]: Unit httpd.service entered failed state.
Feb 02 11:04:04 hostname systemd[1]: httpd.service failed.
[root@hostname ~]# vi /usr/lib/systemd/system/httpd.service
[root@hostname ~]# systemctl daemon-reload
[root@hostname ~]# date; /bin/systemctl start httpd.service; date
Fri  2 Feb 11:06:44 GMT 2018
Job for httpd.service failed because a fatal signal was delivered to the control process. See "systemctl status httpd.service" and "journalctl -xe" for details.
Fri  2 Feb 11:06:44 GMT 2018
[root@hostname ~]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Fri 2018-02-02 11:06:44 GMT; 16s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 6334 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=killed, signal=KILL)
 Main PID: 6334 (code=killed, signal=KILL)

Feb 02 11:06:44 hostname systemd[1]: Starting The Apache HTTP Server...
Feb 02 11:06:44 hostname systemd[1]: httpd.service start operation timed out. Terminating.
Feb 02 11:06:44 hostname systemd[1]: httpd.service stop-final-sigterm timed out. Killing.
Feb 02 11:06:44 hostname systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL
Feb 02 11:06:44 hostname systemd[1]: Failed to start The Apache HTTP Server.
Feb 02 11:06:44 hostname systemd[1]: Unit httpd.service entered failed state.
Feb 02 11:06:44 hostname systemd[1]: httpd.service failed.
[root@hostname ~]# journalctl -xe
Feb 02 11:08:00 hostname sshd[6340]: Accepted publickey for webowner from 172.21.1.6 port 58396 ssh2: DSA SHA256:dHhG7lBu1zLGNRuGhkpMcdMz5KMjNkiro08TNoVqATM
Feb 02 11:08:01 hostname systemd[1]: Started Session 73985 of user webowner.
-- Subject: Unit session-73985.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73985.scope has finished starting up.
--
-- The start-up result is done.
Feb 02 11:08:01 hostname systemd-logind[603]: New session 73985 of user webowner.
-- Subject: A new session 73985 has been created for user webowner
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 73985 has been created for the user webowner.
--
-- The leading process of the session is 6340.
Feb 02 11:08:01 hostname systemd[1]: Starting Session 73985 of user webowner.
-- Subject: Unit session-73985.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73985.scope has begun starting up.
Feb 02 11:08:01 hostname sshd[6340]: pam_unix(sshd:session): session opened for user webowner by (uid=0)
Feb 02 11:08:01 hostname sshd[6345]: Received disconnect from 172.21.1.6 port 58396:11: disconnected by user
Feb 02 11:08:01 hostname sshd[6345]: Disconnected from 172.21.1.6 port 58396
Feb 02 11:08:01 hostname sshd[6340]: pam_unix(sshd:session): session closed for user webowner
Feb 02 11:08:15 hostname sshd[6342]: Accepted publickey for webowner from 172.21.1.6 port 58422 ssh2: DSA SHA256:dHhG7lBu1zLGNRuGhkpMcdMz5KMjNkiro08TNoVqATM
Feb 02 11:08:15 hostname systemd[1]: Started Session 73986 of user webowner.
-- Subject: Unit session-73986.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73986.scope has finished starting up.
--
-- The start-up result is done.
Feb 02 11:08:15 hostname systemd-logind[603]: New session 73986 of user webowner.
-- Subject: A new session 73986 has been created for user webowner
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 73986 has been created for the user webowner.
--
-- The leading process of the session is 6342.
Feb 02 11:08:15 hostname systemd[1]: Starting Session 73986 of user webowner.
-- Subject: Unit session-73986.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73986.scope has begun starting up.
Feb 02 11:08:15 hostname sshd[6342]: pam_unix(sshd:session): session opened for user webowner by (uid=0)
Feb 02 11:08:15 hostname sshd[6357]: Received disconnect from 172.21.1.6 port 58422:11: disconnected by user
Feb 02 11:08:15 hostname sshd[6357]: Disconnected from 172.21.1.6 port 58422
Feb 02 11:08:15 hostname sshd[6342]: pam_unix(sshd:session): session closed for user webowner
[root@hostname ~]# vi /usr/lib/systemd/system/httpd.service
[root@hostname ~]# systemctl daemon-reload
[root@hostname ~]# date; /bin/systemctl start httpd.service; date
Fri  2 Feb 11:09:39 GMT 2018
Job for httpd.service failed because a fatal signal was delivered to the control process. See "systemctl status httpd.service" and "journalctl -xe" for details.
Fri  2 Feb 11:12:39 GMT 2018
[root@hostname ~]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Fri 2018-02-02 11:12:39 GMT; 12s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 6411 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=killed, signal=KILL)
 Main PID: 6411 (code=killed, signal=KILL)
   Status: "Total requests: 0; Current requests/sec: 0; Current traffic:   0 B/sec"

Feb 02 11:09:39 hostname systemd[1]: Starting The Apache HTTP Server...
Feb 02 11:11:09 hostname systemd[1]: httpd.service start operation timed out. Terminating.
Feb 02 11:12:39 hostname systemd[1]: httpd.service stop-final-sigterm timed out. Killing.
Feb 02 11:12:39 hostname systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL
Feb 02 11:12:39 hostname systemd[1]: Failed to start The Apache HTTP Server.
Feb 02 11:12:39 hostname systemd[1]: Unit httpd.service entered failed state.
Feb 02 11:12:39 hostname systemd[1]: httpd.service failed.
[root@hostname ~]# journalctl -xe
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 73990 has been created for the user webowner.
--
-- The leading process of the session is 6448.
Feb 02 11:12:22 hostname systemd[1]: Starting Session 73990 of user webowner.
-- Subject: Unit session-73990.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73990.scope has begun starting up.
Feb 02 11:12:22 hostname sshd[6448]: pam_unix(sshd:session): session opened for user webowner by (uid=0)
Feb 02 11:12:22 hostname sshd[6453]: Received disconnect from 172.21.1.6 port 60796:11: disconnected by user
Feb 02 11:12:22 hostname sshd[6453]: Disconnected from 172.21.1.6 port 60796
Feb 02 11:12:22 hostname sshd[6448]: pam_unix(sshd:session): session closed for user webowner
Feb 02 11:12:39 hostname systemd[1]: httpd.service stop-final-sigterm timed out. Killing.
Feb 02 11:12:39 hostname systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL
Feb 02 11:12:39 hostname systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Feb 02 11:12:39 hostname systemd[1]: Unit httpd.service entered failed state.
Feb 02 11:12:39 hostname systemd[1]: httpd.service failed.
Feb 02 11:12:39 hostname polkitd[604]: Unregistered Authentication Agent for unix-process:6405:396467682 (system bus name :1.148208, object path /org/freedesktop/PolicyKit1/Authenticatio
Feb 02 11:13:14 hostname sshd[6469]: Accepted publickey for webowner from 172.21.1.6 port 32850 ssh2: DSA SHA256:dHhG7lBu1zLGNRuGhkpMcdMz5KMjNkiro08TNoVqATM
Feb 02 11:13:14 hostname systemd[1]: Started Session 73991 of user webowner.
-- Subject: Unit session-73991.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73991.scope has finished starting up.
--
-- The start-up result is done.
Feb 02 11:13:14 hostname systemd-logind[603]: New session 73991 of user webowner.
-- Subject: A new session 73991 has been created for user webowner
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 73991 has been created for the user webowner.
--
-- The leading process of the session is 6469.
Feb 02 11:13:14 hostname systemd[1]: Starting Session 73991 of user webowner.
-- Subject: Unit session-73991.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-73991.scope has begun starting up.
Feb 02 11:13:14 hostname sshd[6469]: pam_unix(sshd:session): session opened for user webowner by (uid=0)
Feb 02 11:13:14 hostname sshd[6474]: Received disconnect from 172.21.1.6 port 32850:11: disconnected by user
Feb 02 11:13:14 hostname sshd[6474]: Disconnected from 172.21.1.6 port 32850
Feb 02 11:13:14 hostname sshd[6469]: pam_unix(sshd:session): session closed for user webowner
[root@hostname ~]# ls -lrt /var/log/httpd | tail
-rw-r--r--. 1 root root     0 Jan 28 03:30 ssl_request_log
-rw-r--r--. 1 root root     0 Jan 28 03:30 ssl_access_log
-rw-r--r--. 1 root root     0 Jan 28 03:30 access_log
-rw-r--r--. 1 root root     0 Feb  1 03:25 ssl_error_log
-rw-r--r--. 1 root root  2108 Feb  1 10:39 ssl_error_log-20180201
-rw-r--r--. 1 root root  9676 Feb  1 10:41 ssl_request_log-20180128
-rw-r--r--. 1 root root  9082 Feb  1 10:41 ssl_access_log-20180128
-rw-r--r--. 1 root root 48679 Feb  1 17:11 access_log-20180128
-rw-r--r--. 1 root root 10039 Feb  2 10:43 error_log-20180128
-rw-r--r--. 1 root root  2907 Feb  2 11:11 error_log
[root@hostname ~]# cat /var/log/httpd/error_log
[Fri Feb 02 10:44:50.458764 2018] [core:notice] [pid 5819] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 10:44:50.460656 2018] [suexec:notice] [pid 5819] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 10:45:50.565947 2018] [auth_digest:notice] [pid 5819] AH01757: generating secret for digest authentication ...
[Fri Feb 02 10:45:50.567748 2018] [lbmethod_heartbeat:notice] [pid 5819] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 02 10:45:50.591777 2018] [mpm_prefork:notice] [pid 5819] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Fri Feb 02 10:45:50.591823 2018] [core:notice] [pid 5819] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Feb 02 10:58:24.418814 2018] [core:notice] [pid 6075] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 10:58:24.421609 2018] [suexec:notice] [pid 6075] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 10:59:24.524339 2018] [auth_digest:notice] [pid 6075] AH01757: generating secret for digest authentication ...
[Fri Feb 02 10:59:24.525948 2018] [lbmethod_heartbeat:notice] [pid 6075] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 02 10:59:24.540125 2018] [core:warn] [pid 6075] AH00098: pid file /run/httpd/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Fri Feb 02 10:59:24.545451 2018] [mpm_prefork:notice] [pid 6075] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Fri Feb 02 10:59:24.545501 2018] [core:notice] [pid 6075] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Feb 02 11:03:24.307932 2018] [core:notice] [pid 6192] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 11:03:24.309941 2018] [suexec:notice] [pid 6192] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 11:10:39.505034 2018] [core:notice] [pid 6411] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 02 11:10:39.506931 2018] [suexec:notice] [pid 6411] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 02 11:11:39.608416 2018] [auth_digest:notice] [pid 6411] AH01757: generating secret for digest authentication ...
[Fri Feb 02 11:11:39.610019 2018] [lbmethod_heartbeat:notice] [pid 6411] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 02 11:11:39.624233 2018] [core:warn] [pid 6411] AH00098: pid file /run/httpd/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Fri Feb 02 11:11:39.629192 2018] [mpm_prefork:notice] [pid 6411] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured -- resuming normal operations
[Fri Feb 02 11:11:39.630341 2018] [core:notice] [pid 6411] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[root@hostname ~]# cat /var/log/httpd/error_log-20180128
[Fri Feb 02 10:43:31.263463 2018] [mpm_prefork:notice] [pid 21655] AH00169: caught SIGTERM, shutting down
[root@hostname ~]# nohup /usr/sbin/httpd -k start -DFOREGROUND &
[1] 6567
[root@hostname ~]# nohup: ignoring input and appending output to ‘nohup.out’
[root@hostname ~]# cat /usr/lib/systemd/system/httpd.service
[Unit]
Description=The Apache HTTP Server
After=network.target remote-fs.target nss-lookup.target
Documentation=man:httpd(8)
Documentation=man:apachectl(8)

[Service]
Type=notify
EnvironmentFile=/etc/sysconfig/httpd
ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
ExecReload=/usr/sbin/httpd $OPTIONS -k graceful
ExecStop=/bin/kill -WINCH ${MAINPID}
# 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
PrivateTmp=true
#Environment=SYSTEMD_LOG_LEVEL=debug
#TimeoutSec=infinity

[Install]
WantedBy=multi-user.target

User avatar
TrevorH
Forum Moderator
Posts: 21771
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby TrevorH » 2018/02/02 16:22:10

What does systemctl cat httpd.service say?
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

hunter86_bg
Posts: 902
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby hunter86_bg » 2018/02/06 06:10:18

As per the last output , it seems that you didn't

Code: Select all

systemctl daemon-reload
and the changes are not applied.

czg
Posts: 12
Joined: 2017/01/25 15:04:15

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby czg » 2018/02/14 14:50:34

TrevorH wrote:What does systemctl cat httpd.service say?


Code: Select all

[root@hostname ~]# systemctl cat httpd.service
# /usr/lib/systemd/system/httpd.service
[Unit]
Description=The Apache HTTP Server
After=network.target remote-fs.target nss-lookup.target
Documentation=man:httpd(8)
Documentation=man:apachectl(8)

[Service]
Type=notify
EnvironmentFile=/etc/sysconfig/httpd
ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
ExecReload=/usr/sbin/httpd $OPTIONS -k graceful
ExecStop=/bin/kill -WINCH ${MAINPID}
# 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
PrivateTmp=true
#Environment=SYSTEMD_LOG_LEVEL=debug
#TimeoutSec=infinity

[Install]
WantedBy=multi-user.target


I have tried it with the Environment & TimeoutSec settings enabled with the results described earlier.

hunter86_bg wrote:As per the last output , it seems that you didn't

Code: Select all

systemctl daemon-reload
and the changes are not applied.


When I made changes to the /usr/lib/systemd/system/httpd.service file and tried to restart the service I was prompted to run the daemon-reload and did so, it is quite possible the daemon and current config aren't in line because I'm currently running apache via

Code: Select all

nohup /usr/sbin/httpd -k start -DFOREGROUND &


Could all this be caused by the fact I'm running on a 1 cpu core VM?

hunter86_bg
Posts: 902
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: Following a yum update /bin/systemctl start httpd.service times out

Postby hunter86_bg » 2018/02/14 15:38:02

Making changes in systemd services:
1. Copy systemd service to "/etc/systemd/system"
If you fail to do so, once you update the package that provided the service - it will be overwritten.
2. Edit the systemd service (/etc/systemd/system) as you wish
3.Reload systemd daemon