Howdy Marek, I would suggest using the init script to stop the service, instead of using killall or pkill. Using those tools can be useful in emergencies, but routine use can put your system in an inconsistent state between the process, subsys file, and pid file. Even when the init script with a stop command says FAILED, it does clean up work on the subsys file and pid file.
The file you posted appears to be your /etc/php.ini file. Please post your /etc/php-fpm.conf file and any pool configuration files under /etc /php-fpm.d/ so we can try to assist. -- You received this bug notification because you are a member of IUS Core Development, which is subscribed to IUS Community Project. https://bugs.launchpad.net/bugs/1237617 Title: Unable to start php54-fpm Status in IUS Community Project: New Bug description: /etc/init.d/php-fpm start Starting php-fpm: [09-Oct-2013 19:47:55] ERROR: An another FPM instance seems to already listen on /home/php-fpm/sock/mareklipski.sock [09-Oct-2013 19:47:55] ERROR: FPM initialization failed [FAILED] I have to do killall -9 php-fpm; pkill -o php-fpm; then restart with /etc/init.d/php-fpm restart This happens every 10-30 minutes and all pages display Internal Server Error at this time. I was using remi repo before and it did not happen. It seems remi is using a bit different init.d script: http://files.tinypic.pl/i/00455/h1n609bja2xz.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ius/+bug/1237617/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ius-coredev Post to : [email protected] Unsubscribe : https://launchpad.net/~ius-coredev More help : https://help.launchpad.net/ListHelp
