httpd.service FAILED to start

General support questions
Post Reply
Evil_Hunter
Posts: 4
Joined: 2024/02/16 12:44:24

httpd.service FAILED to start

Post by Evil_Hunter » 2024/02/16 13:08:30

First of all my server was running smoothly, but suddenly HTTPD.SERVICE failed, I've looked for a solution, but it still failed

Running: "systemctl -l status httpd.service" gives me:

Code: Select all

● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2024-02-16 19:46:17 WIB; 5min ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 128632 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 128632 (code=exited, status=1/FAILURE)

Feb 16 19:46:16 bppa.server systemd[1]: Starting The Apache HTTP Server...
Feb 16 19:46:17 bppa.server systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Feb 16 19:46:17 bppa.server systemd[1]: Failed to start The Apache HTTP Server.
Feb 16 19:46:17 bppa.server systemd[1]: Unit httpd.service entered failed state.
Feb 16 19:46:17 bppa.server systemd[1]: httpd.service failed.
"journalctl -xe"

Code: Select all

Feb 16 19:44:07 bppa.server setroubleshoot[128484]: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock. For complete SELinux messages run
Feb 16 19:44:07 bppa.server python[128484]: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock.

                                            *****  Plugin catchall (100. confidence) suggests   **************************

                                            If you believe that smbd should be allowed read access on the cups.sock sock_file by default.
                                            Then you should report this as a bug.
                                            You can generate a local policy module to allow this access.
                                            Do
                                            allow this access for now by executing:
                                            # ausearch -c 'lpqd' --raw | audit2allow -M my-lpqd
                                            # semodule -i my-lpqd.pp

Feb 16 19:46:16 bppa.server polkitd[1110]: Registered Authentication Agent for unix-process:128624:9467270 (system bus name :1.1061 [/usr/bin/pkttyagent --notify-fd 5
Feb 16 19:46:16 bppa.server systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Feb 16 19:46:17 bppa.server systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Feb 16 19:46:17 bppa.server 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 16 19:46:17 bppa.server systemd[1]: Unit httpd.service entered failed state.
Feb 16 19:46:17 bppa.server systemd[1]: httpd.service failed.
Feb 16 19:46:17 bppa.server polkitd[1110]: Unregistered Authentication Agent for unix-process:128624:9467270 (system bus name :1.1061, object path /org/freedesktop/Pol
Feb 16 19:46:25 bppa.server sshd[128669]: Connection closed by 175.20.20.3 port 49316 [preauth]
Feb 16 19:50:01 bppa.server systemd[1]: Started Session 313 of user root.
-- Subject: Unit session-313.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-313.scope has finished starting up.
--
-- The start-up result is done.
Feb 16 19:50:01 bppa.server CROND[128882]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Feb 16 19:51:25 bppa.server sshd[129013]: Connection closed by 175.20.20.3 port 49320 [preauth]
"error_log"

Code: Select all

[Fri Feb 16 16:51:43.566478 2024] [core:notice] [pid 114555:tid 140548661491840] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 16 16:51:43.572171 2024] [suexec:notice] [pid 114555:tid 140548661491840] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 16 16:51:43.574423 2024] [core:emerg] [pid 114555:tid 140548661491840] (28)No space left on device: AH00023: Couldn't create the ssl-cache mutex
AH00016: Configuration Failed
[Fri Feb 16 17:03:37.578782 2024] [core:notice] [pid 116169:tid 139761475971200] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 16 17:03:37.584722 2024] [suexec:notice] [pid 116169:tid 139761475971200] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 16 17:03:37.586955 2024] [core:emerg] [pid 116169:tid 139761475971200] (28)No space left on device: AH00023: Couldn't create the ssl-cache mutex
AH00016: Configuration Failed
[Fri Feb 16 17:03:44.496660 2024] [core:notice] [pid 116200:tid 140477974063232] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 16 17:03:44.504307 2024] [suexec:notice] [pid 116200:tid 140477974063232] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 16 17:03:44.508091 2024] [core:emerg] [pid 116200:tid 140477974063232] (28)No space left on device: AH00023: Couldn't create the ssl-cache mutex
AH00016: Configuration Failed
[Fri Feb 16 17:03:52.022211 2024] [core:notice] [pid 116236:tid 140509610100864] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 16 17:03:52.029843 2024] [suexec:notice] [pid 116236:tid 140509610100864] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 16 17:03:52.032447 2024] [core:emerg] [pid 116236:tid 140509610100864] (28)No space left on device: AH00023: Couldn't create the ssl-cache mutex
AH00016: Configuration Failed
[Fri Feb 16 17:04:35.650704 2024] [core:notice] [pid 116324:tid 139785049585792] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri Feb 16 17:04:35.656027 2024] [suexec:notice] [pid 116324:tid 139785049585792] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 16 17:04:35.658429 2024] [core:emerg] [pid 116324:tid 139785049585792] (28)No space left on device: AH00023: Couldn't create the ssl-cache mutex
AH00016: Configuration Failed
I am stuck as to what to try next, any help would be much appreciated!
Top
User avatar
TrevorH
Site Admin
Posts: 33222
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: httpd.service FAILED to start

Post by TrevorH » 2024/02/16 14:16:29

[Fri Feb 16 17:04:35.658429 2024] [core:emerg] [pid 116324:tid 139785049585792] (28)No space left on device: AH00023: Couldn't create the ssl-cache mutex
This is the problem. If you are using the default set up then that will be from this line in /etc/httpd/conf.d/ssl.conf

SSLSessionCache shmcb:/run/httpd/sslcache(512000)

So your /run filesystem is full - verify that using `df -m /run`. Since that's a volatile filesystem that contains no permanent data and is emptied out by a reboot, I'd suggest your quickest solution would be to do that. You might want to look at where all the space has gone first using `du -m -x -d1 /run` then repeat that for the largest subdirectory and work out where all the space has gone. If it's under /run/log then you may be able to avoid the reboot by using the journalctl command which has some "vacuum" options to delete old files. Another common way to fil up /run is to have things configured to crash and take coredumps which are written there and take up huge amounts of space. If you find any of those then either move them elsewhere where there is more space or delete them.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Top
Evil_Hunter
Posts: 4
Joined: 2024/02/16 12:44:24

Re: httpd.service FAILED to start

Post by Evil_Hunter » 2024/02/16 14:31:24

First, sorry for my English.. Iam using Google Translate

I tried to run "df -m /run" and this the result

Code: Select all

Filesystem     1M-blocks  Used Available Use% Mounted on
tmpfs               7656    19      7637   1% /run
Top
Evil_Hunter
Posts: 4
Joined: 2024/02/16 12:44:24

Re: httpd.service FAILED to start

Post by Evil_Hunter » 2024/02/19 04:46:49

I do reboot system, but nothing happen
Top
Whoever
Posts: 1361
Joined: 2013/09/06 03:12:10

Re: httpd.service FAILED to start

Post by Whoever » 2024/02/19 18:03:24

You might want to go through this post:
https://serverfault.com/questions/99194 ... ex-when-re
Top
Evil_Hunter
Posts: 4
Joined: 2024/02/16 12:44:24

Re: httpd.service FAILED to start

Post by Evil_Hunter » 2024/02/20 16:54:21

Whoever wrote: ↑
2024/02/19 18:03:24
 You might want to go through this post:
https://serverfault.com/questions/99194 ... ex-when-re
done, thanks..

after "No space left" problem

i have another one

my "error_log" gives me :

Code: Select all

[Tue Feb 20 12:17:32.195777 2024] [:error] [pid 114868] SSL Library Error: -12263 SSL received a record that exceeded the maximum permissible length
[Tue Feb 20 12:19:01.304317 2024] [:error] [pid 103623] SSL Library Error: -12263 SSL received a record that exceeded the maximum permissible length
[Tue Feb 20 13:54:25.320712 2024] [:error] [pid 113160] SSL Library Error: -12263 SSL received a record that exceeded the maximum permissible length
Top
User avatar
TrevorH
Site Admin
Posts: 33222
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: httpd.service FAILED to start

Post by TrevorH » 2024/02/20 17:34:22

Probably someone trying to talk plain text to an https port - e.g. http://1.2.3.4:443/
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Top
Post Reply

Return to “CentOS 7 - General Support”