Lsapi - Error

Leo Santis

• October 21, 2025 14:04

Occasionally, I’m getting the errors bellow. What is strange, I’m not running on CloudLinux but AlmaLinux v9.6.0 STANDARD kvm

They are always appear in sequence related to same referrer and time.

Request retrieving failed. Reason: unknown, On: request body, Source: client, Where: unknown, referer: https://domain.com

In order to get more info about fail reason try to change LogLevel to Info in httpd.conf and restart Apache, referer: https://domain.com

Client error on sending request(POST /domain HTTP/1.1); uri(/domain) content-length(459): user_get_body(tmpstackbuf, 16384): read from client failed, referer:

Connect to backend failed with CONNECTION_RESET on sending request(GET /domain HTTP/1.1); uri(/domain/index.php): ReceiveAckHdr: backend reset connection: errno 104 (possibly memlimit for LVE ID 1004 with UID 1004 too small), check http://docs.cloudlinux.com/mod_lsapi_troubleshooting.html

Even if I set LogLevel to info, nothing changed when get those errors.

MySQL 8.0.43 – All Databases are InnoDB

WebServer - PHPAdmin

cpsrvd 11.130.0.15

Data Base Client Version: libmysql - mysqlnd 8.4.13

PHP Version: 8.4.13

What is pretty strange, the only PHP version is loaded through EasyApache4 is 8.3.25-1.1.1.cpanel

Such mismatch on PHP versions could be this issue, I believe.

I can’t upgrade PHP version to 8.4 due some known issues with WordPress.

Any ideas ?

• 

  William Del Piero cPanel Staff

  • October 21, 2025 16:17

  Hi,

  The error you reported may also occur if the lsapi_backend_children limit has been reached for the affected user. When LSAPI is in use, additional logs located in /etc/apache2/logs/—such as lsphp-stderr.log and sulsphp_log—can provide further insight into the issue.

  If you need to review or adjust LSAPI-related settings, the following article offers guidance on the configuration file location and commonly modified directives:

  LSAPI Configuration File Location and Most Commonly Modified Configuration Directives

   

  0
• 

  Leo Santis

  • October 21, 2025 17:40

  Hi William Del Piero

  On lsphp-stderr.log file I can see errors like those below:

  Killing runaway process PID: 237040 with SIGTERM

  Child process with pid: 237039 was killed by signal: 15, core dumped: no

  Overall, about 100 lines of those errors.

  On sulsphp.log file all I can see is:

  sulsphp: uid:(1004/cpleo); gid:(1003/cpleo); lveid:1004 with suexec mode; cmd:(/opt/cpanel/ea-php83/root/usr/bin/lsphp)

  What looks strange to me on this case, is that is showing lveid that’s related to CloudLinux and I’m just running on AlmaLinux as I mentioned.

  Now that’s what intrigues me the most: Almost everything at /etc/apache2/conf.d/lsapi.conf are commented

  # lsapi_backend_children 120

  # lsapi_backend_pgrp_max_idle 30

  # lsapi_backend_max_idle 300

  # lsapi_backend_max_reqs 10000

  Again, If I’m not running on CloudLinux but just AlmaLinux, should such configuration would take any effect on that?

  0
• 

  William Del Piero cPanel Staff

  • October 21, 2025 18:22

  Hi,

  If you're using LSAPI as the PHP handler for the domain, the configuration settings in lsapi.conf will apply to the domain. However, since all the settings appear to be commented out, it's likely that the default values are currently in effect.

  Given that the error logs haven’t clearly identified the root cause, I recommend opening a ticket so the issue can be investigated further with direct access to the server.

  This will allow for a more thorough review and help ensure the most accurate resolution.

  0
• 

  Leo Santis

  • October 21, 2025 19:34

  Thanks William Del Piero, I'll have to do that via my host as I'm using a corporate license.

  0

Please sign in to leave a comment.