Apache gets started automatically after stopping it

Hi,
We noticed that apache gets started automatically, even though it was disabled, stopped and killed beforehand.
Is there any cron job or background process that restarts httpd24-httpd on a regular basis?

[user@host ~]$ sudo systemctl disable httpd24-httpd
Removed symlink /etc/systemd/system/multi-user.target.wants/httpd24-httpd.service.
[user@host ~]$ sudo systemctl stop httpd24-httpd
[user@host ~]$ sudo systemctl kill httpd24-httpd
Failed to kill unit httpd24-httpd.service: Unit httpd24-httpd.service is not loaded.
[user@host ~]$ sudo systemctl status httpd24-httpd
● httpd24-httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/httpd24-httpd.service.d
           └─ood.conf
   Active: inactive (dead)

Apr 07 21:20:24 host systemd[1]: Started The Apache HTTP Server.
Apr 07 21:20:40 host systemd[1]: Stopping The Apache HTTP Server...
Apr 07 21:20:40 host systemd[1]: Stopped The Apache HTTP Server.
Apr 07 21:20:55 host systemd[1]: Starting The Apache HTTP Server...
Apr 07 21:20:55 host systemd[1]: Started The Apache HTTP Server.
Apr 07 21:22:07 host sudo[18608]:   apache : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/opt/ood/nginx_stage/sbin/nginx_stage pun -u ceadejom -...scaped_uri
Apr 07 21:23:02 host sudo[19181]:   apache : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/opt/ood/nginx_stage/sbin/nginx_stage nginx -u ceadejom -s stop
Apr 07 21:23:02 host sudo[19253]:   apache : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/opt/ood/nginx_stage/sbin/nginx_stage pun -u ceadejom -...scaped_uri
Apr 07 21:28:13 host systemd[1]: Stopping The Apache HTTP Server...
Apr 07 21:28:13 host systemd[1]: Stopped The Apache HTTP Server.
Hint: Some lines were ellipsized, use -l to show in full.
[user@host ~]$ sudo systemctl status httpd24-httpd
● httpd24-httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/httpd24-httpd.service.d
           └─ood.conf
   Active: active (running) since Tue 2020-04-07 21:28:27 CEST; 21s ago
 Main PID: 21050 (httpd)
   Status: "Total requests: 0; Idle/Busy workers 100/0;Requests/sec: 0; Bytes served/sec:   0 B/sec"
    Tasks: 47
   CGroup: /system.slice/httpd24-httpd.service
           ├─21050 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
           ├─21055 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
           ├─21056 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
           ├─21057 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
           ├─21063 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
           └─21072 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND

Apr 07 21:28:26 host systemd[1]: Starting The Apache HTTP Server...
Apr 07 21:28:27 host systemd[1]: Started The Apache HTTP Server.

Hi, sorry for the late reply. I don’t believe there’s any cronjob that’ll start httpd. @tdockendorf are you aware of what could be causing this issue?

There is nothing specific to OnDemand that restarts or starts Apache. We go to great lengths to not manage the service state but things like ood-portal-generator will print the systemd commands necessary to manage the service state and leaves the actual command execution up to the admin. The only things that touch service state for OnDemand is the RPM for ondemand will restart httpd24-httpd but only if it’s already running by executing systemctl try-restart. If Apache is stopped during RPM install of OnDemand it will stay stopped.