Errors with php-fpm.

bdacus01 said:
Calling @scriptkitty oh great guru of documentation at DA.. Please come forth and wave the wand...
Click to expand...
@bdacus01 How did you know I was working on the docs!?! Some of your recommended changes have been pushed this morning to the docs (thanks again!). ;) I think we can add a How To for this to my TODO list if it isn't noted in the docs already! Thanks @Richard G and @bdacus01 !
 
Now we're fed up. Out of the blue again exit error 70 and suddenly white screens server wide again.
I don't know what's causing this, still having the idea that it's the MediaCP causing issues or something. We're going to set this server backup to mod_php with mod_ruid2.
 
Richard G said:
Now we're fed up. Out of the blue again exit error 70 and suddenly white screens server wide again.
I don't know what's causing this, still having the idea that it's the MediaCP causing issues or something. We're going to set this server backup to mod_php with mod_ruid2.
Click to expand...
Have you fixed the issue in the end?
 
Nope I didn't. For the time being I went backup to mod_php with mod_ruid and then the issue did not occur anymore.
Then I went back to php-fpm and tried to see what is causing the issue. Seems to me it might be wordpress installations, because the hobby forum now works at php-fpm73 and no error 70's again.
Other sites (mostly Wordpress) work on php-fpm74 and fairly regularly I see the errors again, on different accountnames, but it seems the service does not go down again anymore.

But so no... error is not fixed yet in fact.
 
We are having the exact same issues with PHP 7.4. Empty pages and opcache enabled. Running 4 php versions on this server, only php-fpm74 is having this issue. Restarting the service manually helps but randomly happening again. We tried updating the whole server but it is not providing any solution yet.
 
It is happening occasionally. I reviewed the following logs files but none of them provided any clue:
  1. /var/log/httpd/error_log
  2. /var/log/httpd/access_log
  3. reviewed the /var/log/httpd/domains/$domainname$/access_log and error_log
  4. /var/log/messages
From 13:51 it started happening and the log is full of events with error code 70 after that moment. At 13:53 I rebooted the php-fpm
I found the following logging in /usr/local/php74/var/log/php-fpm.log:

[14-Sep-2023 13:52:52] WARNING: [pool danteck] child 29782 exited with code 70 after 0.007122 seconds from start
[14-Sep-2023 13:52:52] NOTICE: [pool danteck] child 29783 started
[14-Sep-2023 13:52:53] WARNING: [pool id00046] child 29784 exited with code 70 after 0.007221 seconds from start
[14-Sep-2023 13:52:53] NOTICE: [pool id00046] child 29785 started
[14-Sep-2023 13:53:06] NOTICE: Terminating ...
[14-Sep-2023 13:53:06] NOTICE: exiting, bye-bye!
[14-Sep-2023 13:53:06] NOTICE: fpm is running, pid 30786
[14-Sep-2023 13:53:06] NOTICE: ready to handle connections
[14-Sep-2023 13:53:06] NOTICE: systemd monitor interval set to 10000ms

We are monitoring this server with PRTG but no report of memory shortage has been reported, around 30% available/30% cached/40% in use when this started happening. We upgraded the server this evening from 16GB RAM to 32GB RAM and 6 cores to 12 cores. Hopefully this will solve it.
Also made a sensor that is monitoring the received bytes from this webserver. Fingers crossed.
 
Last edited:
No should be php-fpm74 indeed. Everything is running stable since the upgrade of cores, memory and reboot of the server.
 
You must log in or register to reply here.
Back
Top