This has been driving me nuts. First, it took a while to figure out why my FPM was inexplicably dying every 10 minute after getting FPM installed. Obviously I tracked down your script /etc/cron.d/kill_orphaned_php-cron
Now after php-fpm was happily running for a while, the script reappears after requesting some unrelated support from the datacenter. Turns out they did a forced re-installed of cPanel and followed by the CloudLinux as a shotgun approach to solving the issue.
I can see that having this part of your lve-utils package is going to give me anxiety since whenever new cloudlinux updates are required, or whenever I ask for support from the datacenter, or even if the datacenter asserts their "managed server" prerogative to install any of these updates, my php is going to get killed.
I really think this was a bad idea on your part. Maybe you can rewrite it so that it doesnt kill the php-fpm master process or make installing it optional.
Now after php-fpm was happily running for a while, the script reappears after requesting some unrelated support from the datacenter. Turns out they did a forced re-installed of cPanel and followed by the CloudLinux as a shotgun approach to solving the issue.
I can see that having this part of your lve-utils package is going to give me anxiety since whenever new cloudlinux updates are required, or whenever I ask for support from the datacenter, or even if the datacenter asserts their "managed server" prerogative to install any of these updates, my php is going to get killed.
I really think this was a bad idea on your part. Maybe you can rewrite it so that it doesnt kill the php-fpm master process or make installing it optional.
Comment