Skip to main content

PHP-FPM Issue

Comments

11 comments

  • vlee
    Ok... I just tested it with WHMCS and same issue but no error message just will not upload at all. The reason want to use PHP-FPM is because SUPHP is to slow and customers keep complaining the server is too slow. PHP-FPM with Mod_Event is very fast. PHP-FPM is not stable and I have to always have to Restart Apache Web Server and Restart PHP-FPM service for Apache. So I have figure out another solution using Mod_Event without SUPHP.
    0
  • vlee
    I remade 3 new custom EasyApache Profiles based off of the cPanel Default profile. So far the 1st profile allows me to upload files properly 1. Apache 2.4, PHP 7.2, PHP 7.1, OpCache, Mod_Event, PHP-FPM and All PHP Opts, and No suPHP 2. Apache 2.4, PHP 7.2, PHP 7.1, OpCache, Mod_Worker, PHP-FPM and All PHP Opts, and No suPHP 3. Apache 2.4, PHP 7.2, PHP 7.1, OpCache, Mod_Ruid2, PHP-FPM and All PHP Opts, and No suPHP I will give this a few days for each one to see if there is any more issue with uploading files and report my findings here if any. Others feel free to give your own feedback on these builds above. Thank you... :cool:
    0
  • vlee
    Well here is is what I have found out. When cPanel updates and/or other system cronjobs after you have to this happens you always have to this below so this is where the problem is at. Restart Apache Web Server Restart PHP-FPM service for Apache Note: Only happens after cPanel updates and/or other system cronjobs happen. I have my cronjobs happen starting at 9:01 PM starting with cPanel Updates and backups start at 1:01 AM. Something happens during the cPanel updates and/or other system cronjobs to cause this to happen. So have to figure out why this happens and fix it. Other than that I just have to setup a cronjob to Restart Apache Web Server and Restart PHP-FPM service for Apache right after cPanel updates. Doing this will help resolve this issue automatically to keep customers happy and so I do not get a bunch of support tickets for simple restart of 2 services For the performance tests from GTmetrix for my current website for each of the builds below 1. Apache 2.4, PHP 7.2, PHP 7.1, OpCache, Mod_Event, PHP-FPM and All PHP Opts, and No suPHP - Website loads in 2.8 Seconds 2. Apache 2.4, PHP 7.2, PHP 7.1, OpCache, Mod_Worker, PHP-FPM and All PHP Opts, and No suPHP - Website loads in 8.9 Seconds 3. Apache 2.4, PHP 7.2, PHP 7.1, OpCache, Mod_Ruid2, PHP-FPM and All PHP Opts, and No suPHP - Website loads in 7.6 Seconds Mod_Event with PHP-FPM does the best performance then any other builds.
    0
  • vlee
    Now I can confirm that when cPanel updates that have to Restart Apache Web Server Restart PHP-FPM service for Apache and this happens only after cPanel cronjob update and that is if you are running PHP-FPM. So those who run software that has or allows uploading files and experience the same problem then just do the restarts above after the cPanel update gets completed. Which gets to be annoying at times just to allow uploading files. So I hope this helps.
    0
  • cPanelLauren
    Hi @vlee When this issue occurs is anything output in the php-fpm error logs? They're located at: /opt/cpanel/ea-phpXX/root/usr/var/log/php-fpm/error.log
    0
  • vlee
    This is the only error that I see. NOTICE: reloading: execvp("/opt/cpanel/ea-php71/root/usr/sbin/php-fpm", {"/opt/cpanel/ea-php71/root/usr/sbin/php-fpm", "--nodaemonize"}) (11859): Fatal Error Unable to create lock file: Bad file descriptor (9)
    NOTICE: reloading: execvp("/opt/cpanel/ea-php72/root/usr/sbin/php-fpm", {"/opt/cpanel/ea-php71/root/usr/sbin/php-fpm", "--nodaemonize"}) (11859): Fatal Error Unable to create lock file: Bad file descriptor (9)
    0
  • cPanelLauren
    Hi @vlee This error would definitely explain some of the issues you're having but not why specifically, I've seen this occur for a few reasons issues with opcache, lsphp and php-fpm all being factors. With that being said I feel like being able to see the configuration on the server directly would be helpful. Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks!
    0
  • vlee
    I think I found the problem and hopefully fixed it. 1. There was a couple old cronjobs in crontab from back when I was using EasyApache 3 that was still there which I deleted. 2. I also found a couple corrupted Apache and PHP files that showing up in other logs which I am hoping they were fixed after search the errors up and how to fix them. So I will find out find out this resolved my issues by this time tomorrow.
    0
  • cPanelLauren
    Hi @vlee Both of those are good finds, do let us know if the issue persists now that you've fixed those items.
    0
  • vlee
    1. There was a couple old cronjobs in crontab from back when I was using EasyApache 3 that was still there which I deleted. 2. I also found a couple corrupted Apache and PHP files that showing up in other logs which I am hoping they were fixed after search the errors up and how to fix them.

    Well can confirm the issues are fixed now. All because of the items above.
    0
  • cPanelLauren
    Hi @vlee I'm really happy to hear that and thank you very much for letting us know and following up!
    0

Please sign in to leave a comment.