hello, After some client did a update on his site settings php-fpm stopped working. ERROR: [pool web1703] failed to chown() the socket '/var/lib/php74-fpm/web1703.sock': Disk quota exceeded (122) i know what to do... but isnt there a way to prefent the whole server go offline for this simple quota problem?
php74 isnt restarting because of this error ERROR: [pool web1703] failed to chown() the socket '/var/lib/php74-fpm/web1703.sock': Disk quota exceeded (122) So all sites that uses php74 stops working Apache is starting normaly ( i believe)
Yes tell me abouth it :-( The 0 byte .sock cant be generatie So the config file gives an error on loading
The question is if there is a way to avoid that, for security reasons, the socket must be owned by the user that runs the PHP process so that other websites can't connect to it, so it must be owned by the webID user. Not using a socket is possible, but it's slower and insecure as other applications might connect o the network port to run PHP applications under a different user, so not a good idea. Maybe it's possible to put each socket in a different directory and prevent access to it by setting strict directory permissions while using a global user like www-data as owner for the socket?
Sockets under /run could work on Debian systems; surely centos derivatives use that or /var/run or similar?
