Skip to main content

Repeated Apache (httpd) Crashes

Section
  • Edited

Since April 24th, 2025, we’ve been experiencing repeated Apache (httpd) crashes—occurring approximately twice per day—which are significantly affecting our server's stability and causing ongoing issues.

We have taken the following steps based on recommendations found in community forums and your support documentation:

Verified Apache configuration using apachectl configtest (returned Syntax OK)
Restarted Apache multiple times using /scripts/restartsrv_httpd

Followed guidance from this article:

https://mail.google.com/mail/u/1/?pli=1#sent/FMfcgzQbdrSjWNDLTCZzmRKtbFRJLcXq

Despite these efforts, the issue persists.

OS: CloudLinux 8.10
cPanel Version: 126.0.16

We would greatly appreciate your assistance in diagnosing and resolving this matter.

Latest log:

Startup Log
Apr 29 05:20:23 systemd[1]: Starting Apache web server managed by cPanel EasyApache...
Apr 29 05:20:23 systemd[1]: httpd.service: Can't open PID file /run/apache2/httpd.pid (yet?) after start: No such file or directory
Apr 29 05:20:24 systemd[1]: Started Apache web server managed by cPanel EasyApache.
Apr 29 20:46:39 systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 20:46:40 systemd[1]: httpd.service: Failed with result 'exit-code'

Log Messages     [Tue Apr 29 20:46:39.985598 2025] [log_config:warn] [pid 943669:tid 943669] (32)Broken pipe: [client 54.36.148.42:18639] AH00646: Error writing to |/usr/local/cpanel/bin/splitlogs --dir=/etc/apache2/logs/domlogs  --mainout=/etc/apache2/logs/access_log
[Tue Apr 29 20:46:39.985591 2025] [log_config:warn] [pid 943669:tid 943669] (32)Broken pipe: [client 54.36.148.42:18639] AH00646: Error writing to |/usr/local/cpanel/bin/splitlogs --main=apache-traffic.log --mainout=/var/log/cpanel-server-traffic/web/traffic-apache.log
[Tue Apr 29 20:46:39.985568 2025] [log_config:warn] [pid 943669:tid 943669] (32)Broken pipe: [client 54.36.148.42:18639] AH00646: Error writing to |/usr/local/cpanel/bin/splitlogs --dir=/etc/apache2/logs/domlogs  --suffix=-bytes_log
[Tue Apr 29 20:46:39.814472 2025] [core:alert] [pid 8564:tid 8564] AH00050: Child 929502 returned a Fatal error... Apache is exiting! writing to |/usr/local/cpanel/bin/splitlogs --dir=/etc/apache2/logs/domlogs --suffix=-bytes_log

 

Comments

10 comments

Date Votes
  • Uniserve Team

    Hi, I just wanted to note that I have observed these same Apache2 crashes on one of our cPanel hosts starting April 24th.  I don't have a fix, but you aren't alone.  Hoping for help from cPanel team.

    OS: CloudLinux 8.10

    cPanel version: 126.0.16

     

    I was noticing the same error from splitlogs, this seems to be a red herring though:  upon creating the path /var/log/cpanel-server-traffic/web/ the splitlogs tool seems to be able to successfully complete its job, and the splitlogs errors showing in the httpd.service output have gone away.   However, I've still now seen two more httpd.service crashes since yesterday afternoon.

    $ ls /var/log/cpanel-server-traffic/web/
    2025-04-24-traffic-apache.log     2025-04-26-traffic-apache.log     2025-04-28-traffic-apache.log.gz  
    2025-04-25-traffic-apache.log     2025-04-27-traffic-apache.log     traffic-apache.log  

     

     

    -- Logs begin at Tue 2025-04-22 14:12:12 PDT, end at Tue 2025-04-29 11:55:16 PDT. --
    Apr 23 05:30:44  systemd[1]: Reloading Apache web server managed by cPanel EasyApache.
    Apr 23 05:30:45  systemd[1]: Reloaded Apache web server managed by cPanel EasyApache.
    Apr 23 23:57:54  systemd[1]: Reloading Apache web server managed by cPanel EasyApache.
    Apr 23 23:57:55  systemd[1]: Reloaded Apache web server managed by cPanel EasyApache.
    Apr 23 23:59:33  systemd-coredump[2078846]: Process 2077691 (splitlogs) of user 0 dumped core.
    Apr 24 00:04:33  systemd-coredump[2094086]: Process 2078842 (splitlogs) of user 0 dumped core.
    Apr 24 00:06:26  systemd-coredump[2094968]: Process 2094084 (splitlogs) of user 0 dumped core.
    Apr 24 00:14:59  systemd-coredump[2098599]: Process 2094981 (splitlogs) of user 0 dumped core.
    Apr 24 00:31:41  systemd-coredump[2105954]: Process 2098600 (splitlogs) of user 0 dumped core.
    Apr 24 00:48:23  systemd-coredump[2113468]: Process 2105962 (splitlogs) of user 0 dumped core.
    Apr 24 01:05:05  systemd-coredump[2120859]: Process 2113480 (splitlogs) of user 0 dumped core.
    Apr 24 01:21:47  systemd-coredump[2127931]: Process 2120868 (splitlogs) of user 0 dumped core.
    Apr 24 01:38:29  systemd-coredump[2134948]: Process 2127940 (splitlogs) of user 0 dumped core.
    Apr 24 01:55:11  systemd-coredump[2143813]: Process 2134958 (splitlogs) of user 0 dumped core.
    Apr 24 02:03:34  systemd-coredump[2147075]: Process 2143821 (splitlogs) of user 0 dumped core.
    Apr 24 02:12:07  systemd-coredump[2150764]: Process 2147085 (splitlogs) of user 0 dumped core.
    Apr 24 02:28:49  systemd-coredump[2157749]: Process 2150773 (splitlogs) of user 0 dumped core.
    Apr 24 02:45:31  systemd-coredump[2165242]: Process 2157758 (splitlogs) of user 0 dumped core.
    Apr 24 03:02:13  systemd-coredump[2172213]: Process 2165254 (splitlogs) of user 0 dumped core.
    Apr 24 03:18:54  systemd-coredump[2179236]: Process 2172219 (splitlogs) of user 0 dumped core.
    Apr 24 03:35:36  systemd-coredump[2187120]: Process 2179246 (splitlogs) of user 0 dumped core.
    Apr 24 03:52:18  systemd-coredump[2194495]: Process 2187136 (splitlogs) of user 0 dumped core.
    Apr 24 04:00:41  systemd-coredump[2198558]: Process 2194501 (splitlogs) of user 0 dumped core.
    Apr 24 04:09:14  systemd-coredump[2202095]: Process 2198564 (splitlogs) of user 0 dumped core.
    Apr 24 04:25:56  systemd-coredump[2209831]: Process 2202111 (splitlogs) of user 0 dumped core.
    Apr 24 04:42:38  systemd-coredump[2218258]: Process 2209837 (splitlogs) of user 0 dumped core.
    Apr 24 04:59:20  systemd-coredump[2237243]: Process 2218269 (splitlogs) of user 0 dumped core.
    Apr 24 05:16:02  systemd-coredump[2249523]: Process 2237261 (splitlogs) of user 0 dumped core.
    Apr 24 05:16:03  systemd-coredump[2249537]: Process 2249532 (splitlogs) of user 0 dumped core.
    Apr 24 05:49:13  systemd-coredump[2270849]: Process 2249543 (splitlogs) of user 0 dumped core.
    Apr 24 06:05:55  systemd-coredump[2279443]: Process 2270865 (splitlogs) of user 0 dumped core.
    Apr 24 06:14:18  systemd-coredump[2283165]: Process 2279454 (splitlogs) of user 0 dumped core.
    Apr 24 06:22:52  systemd-coredump[2287354]: Process 2283175 (splitlogs) of user 0 dumped core.
    Apr 24 06:39:34  systemd-coredump[2296051]: Process 2287367 (splitlogs) of user 0 dumped core.
    Apr 24 06:56:15  systemd-coredump[2304520]: Process 2296063 (splitlogs) of user 0 dumped core.
    Apr 24 07:12:57  systemd-coredump[2313910]: Process 2304529 (splitlogs) of user 0 dumped core.
    Apr 24 07:29:39  systemd-coredump[2322489]: Process 2313921 (splitlogs) of user 0 dumped core.
    Apr 24 07:46:21  systemd-coredump[2335759]: Process 2322506 (splitlogs) of user 0 dumped core.
    Apr 24 08:03:03  systemd-coredump[2344918]: Process 2335771 (splitlogs) of user 0 dumped core.
    Apr 24 08:11:26  systemd-coredump[2349839]: Process 2344927 (splitlogs) of user 0 dumped core.
    Apr 24 08:20:00  systemd-coredump[2354236]: Process 2349857 (splitlogs) of user 0 dumped core.
    Apr 24 08:36:42  systemd-coredump[2363937]: Process 2354254 (splitlogs) of user 0 dumped core.
    Apr 24 08:53:24  systemd-coredump[2372615]: Process 2363947 (splitlogs) of user 0 dumped core.
    Apr 24 09:10:05  systemd-coredump[2382120]: Process 2372625 (splitlogs) of user 0 dumped core.
    Apr 24 09:26:47  systemd-coredump[2391531]: Process 2382129 (splitlogs) of user 0 dumped core.
    Apr 24 09:43:29  systemd-coredump[2400831]: Process 2391538 (splitlogs) of user 0 dumped core.
    Apr 24 10:00:11  systemd-coredump[2409451]: Process 2400832 (splitlogs) of user 0 dumped core.
    Apr 24 10:08:34  systemd-coredump[2414479]: Process 2409474 (splitlogs) of user 0 dumped core.
    Apr 24 10:17:08  systemd-coredump[2419396]: Process 2414496 (splitlogs) of user 0 dumped core.
    Apr 24 10:33:49  systemd-coredump[2428183]: Process 2419413 (splitlogs) of user 0 dumped core.
    Apr 24 10:50:31  systemd-coredump[2438674]: Process 2428196 (splitlogs) of user 0 dumped core.
    Apr 24 11:07:13  systemd-coredump[2447410]: Process 2438684 (splitlogs) of user 0 dumped core.
    Apr 24 11:23:55  systemd-coredump[2455994]: Process 2447421 (splitlogs) of user 0 dumped core.
    Apr 24 11:40:37  systemd-coredump[2464437]: Process 2456006 (splitlogs) of user 0 dumped core.
    Apr 24 11:57:19  systemd-coredump[2473063]: Process 2464447 (splitlogs) of user 0 dumped core.
    Apr 24 12:05:42  systemd-coredump[2477699]: Process 2473075 (splitlogs) of user 0 dumped core.
    Apr 24 12:14:16  systemd-coredump[2482182]: Process 2477706 (splitlogs) of user 0 dumped core.
    Apr 24 12:30:58  systemd-coredump[2490391]: Process 2482192 (splitlogs) of user 0 dumped core.
    Apr 24 12:47:40  systemd-coredump[2499030]: Process 2490397 (splitlogs) of user 0 dumped core.
    Apr 24 13:04:21  systemd-coredump[2507935]: Process 2499046 (splitlogs) of user 0 dumped core.
    Apr 24 13:21:03  systemd-coredump[2516563]: Process 2507944 (splitlogs) of user 0 dumped core.
    Apr 24 13:37:45  systemd-coredump[2525291]: Process 2516574 (splitlogs) of user 0 dumped core.
    Apr 24 13:54:27  systemd-coredump[2535683]: Process 2525304 (splitlogs) of user 0 dumped core.
    Apr 24 14:02:50  systemd-coredump[2539929]: Process 2535689 (splitlogs) of user 0 dumped core.
    Apr 24 14:11:24  systemd-coredump[2544681]: Process 2539939 (splitlogs) of user 0 dumped core.
    Apr 24 14:28:06  systemd-coredump[2553553]: Process 2544699 (splitlogs) of user 0 dumped core.
    Apr 24 14:44:48  systemd-coredump[2562157]: Process 2553562 (splitlogs) of user 0 dumped core.
    Apr 24 15:01:30  systemd-coredump[2570942]: Process 2562168 (splitlogs) of user 0 dumped core.
    Apr 24 15:09:14  systemd-coredump[2575116]: Process 2570952 (splitlogs) of user 0 dumped core.
    Apr 24 15:09:15  systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
    Apr 24 15:09:15  systemd[1]: httpd.service: Failed with result 'exit-code'.
    Apr 24 15:21:40  systemd[1]: Starting Apache web server managed by cPanel EasyApache...
    Apr 24 15:21:41  systemd[1]: httpd.service: Can't open PID file /run/apache2/httpd.pid (yet?) after start: No such file or directory
    Apr 24 15:21:42  systemd[1]: Started Apache web server managed by cPanel EasyApache.
    Apr 24 15:34:54  systemd-coredump[2587381]: Process 2580862 (splitlogs) of user 0 dumped core.
    Apr 24 15:51:35  systemd-coredump[2595056]: Process 2587391 (splitlogs) of user 0 dumped core.
    Apr 28 14:49:23  systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
    Apr 28 14:49:23  systemd[1]: httpd.service: Failed with result 'exit-code'.
    Apr 28 15:00:10  systemd[1]: Starting Apache web server managed by cPanel EasyApache...
    Apr 28 15:00:11  systemd[1]: httpd.service: Can't open PID file /run/apache2/httpd.pid (yet?) after start: No such file or directory
    Apr 28 15:00:12  systemd[1]: Started Apache web server managed by cPanel EasyApache.
    Apr 28 18:36:32  systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
    Apr 28 18:36:32  systemd[1]: httpd.service: Failed with result 'exit-code'.
    Apr 28 18:47:22  systemd[1]: Starting Apache web server managed by cPanel EasyApache...
    Apr 28 18:47:23  systemd[1]: httpd.service: Can't open PID file /run/apache2/httpd.pid (yet?) after start: No such file or directory
    Apr 28 18:47:23  systemd[1]: Started Apache web server managed by cPanel EasyApache.

    0
  • Section

    I just received a reply from the CL team regarding the issue. They confirmed that the problem still persists even after installing the latest ea-cpanel-tools package:
    ea-cpanel-tools-1.0-107.el8.cloudlinux.x86_64

    Since the nature of the error lies in the cPanel splitting utility, we are currently waiting for the cPanel team to provide a fix.

    0
  • cPRex Jurassic Moderator

    Hey there - were you able to submit a ticket on this if it's still happening after the ea-cpanel-tools reinstall?

    0
  • Section
    • Edited

    Hello, yes it is still happening as i mentioned above. CL team also verified that and point me to cpanel. I will try to open a support ticket but since my license is through a cpanel partner maybe i am not able to do.

    0
  • cPRex Jurassic Moderator

    You would need to open a ticket through your provider, and then they would escalate the issue to us if they can't resolve the problem.

    0
  • Section

    The provider cannot escalate the issue.  As previously mentioned, the problem began with cPanel version 126.0.16. The issue with the split logs has been reported by many users across multiple threads, and it is becoming increasingly frustrating. We are awaiting an update by cpanel team to resolve this matter.

    0
  • cPRex Jurassic Moderator

    I've never heard of a provider not being able to escalate an issue before.

    If the issue was the same as the other splitlogs problem then I would expect the same workaround to work as well.  I recommended creating a ticket because other users are having success with the workaround.

    0
  • Section

    Even the cloudlinux team investigated and confirmed all actions performed well and pointed me to cpanel as i mentioned above. I dont agree other users having success we read other threads and even on this thread there is another user having the same issue. We hope cpanel team to soon update their product and resolve this issue.

    0
  • cPRex Jurassic Moderator

    The team is working on a fix right now and we'll get that released as soon as we can.

    0
  • dexter2323

    ?? old problem
    https://support.cpanel.net/hc/en-us/community/posts/19653479863703-splitlog-error



    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post