135 reputation
13
bio website
location Munich, Germany
age
visits member for 3 years, 4 months
seen Mar 25 at 19:11

Mar
25
accepted PHP-FPM - problems with the pre-start process
Mar
25
comment PHP-FPM - problems with the pre-start process
Ah! That was the hint, I needed: /etc/init/php5-fpm.conf refered to a file /usr/lib/php5/php5-fpm-checkconfthat did not exist. And I was unable to reinstall php5-fpm... The reason was a modification in the /etc/apt/sources.list (no universe...) that apparently caused a removal of the PHP-FPM package. plonk -- and thanks a lot! Please post the hint as answer, if you don't mind.
Mar
25
asked PHP-FPM - problems with the pre-start process
Mar
11
awarded  Popular Question
Jan
1
revised Monit: How to optimally monitor an URL
Added new experience
Dec
25
comment Monit: How to optimally monitor an URL
Thanks for the idea. Actually, monit checks the availability every 2 minutes. That would be enough time to let a load peak pass (alert if PHP/webserver does not respond within 20 seconds) and to restart the webserver (if there is no response after 20 seconds a second time, 2 minutes later). If neithing waiting (2 min.) nor restartig PHP/nginx did help (third fail in three tries), the server shall reboot. So, the original monit script what I like it to. Yet, the test script is a bit hungry for ressources, therefore I'f like to do the request only once.
Dec
23
revised Monit: How to optimally monitor an URL
typo
Dec
23
revised Monit: How to optimally monitor an URL
Added firs step towards a solution
Dec
23
comment Monit: How to optimally monitor an URL
Thanks, the CHECK HOST is a good idea. Yet, I do not see how the EXECshall solve the problem that multiple HTTPS requests are necessary to perform different actions after 1, 2, and 4 fails?!
Dec
18
awarded  Curious
Dec
17
asked Monit: How to optimally monitor an URL
Dec
3
revised How do you restart php-fpm?
Better solution
Aug
8
answered How do you restart php-fpm?
Jun
19
awarded  Popular Question
May
4
comment Emails from web site sometimes blank or gibberish
I encountered (and still encounter) the same problem - no matter if using mail() directly or PHPmailer. About 1 in 1000 mail adresses receives a seemingly empty email (but only one, not another...). Actually, the source code of the mail is still contained, but the MIME structure was changed, making the content invisible in mail clients. My best guess is that some process on the mail's way reads the structure wrong and creates a new structure. Although, there is no systematical correlation with the receiving mail server, mail client, the mail's content or such...
Aug
16
accepted Apache mpm-worker + mod_fcgid + php5_cgi partially and sporadically down
Aug
15
comment Apache mpm-worker + mod_fcgid + php5_cgi partially and sporadically down
Ah - got it. I thought, you'd refered to the apache setting MaxRequestsPerProcess, not the fcgid setting FcgidMaxRequestsPerProcess... I'll still have to be careful, as most requests want PHP scripts (images are well cached), but I shall give this a try. Thanks!
Aug
14
comment Apache mpm-worker + mod_fcgid + php5_cgi partially and sporadically down
I do not use non-default packages/modules in PHP and I hope, that the default packages have few memory leaks. However, you never know... Now I understand the issue of leaks and deadloops much better. Thank you very much for the explanation.
Aug
14
comment Apache mpm-worker + mod_fcgid + php5_cgi partially and sporadically down
I am afraid, my understanding of memory leaks if limited. As I working with PHP, I have put a memory limit (128 M) n each script. Only in rare occasions, a script will actually need this limit. However, if the limit is exceeded or the script hangs in a deadloop, I usually see a "memory exceeded" or "execution time exceeded" error in my PHP logs. But those I once had, have long been bugfixes - there have not been such errors for a while. So: Am I really looking for memory leaks and deadlocks?
Aug
14
comment Apache mpm-worker + mod_fcgid + php5_cgi partially and sporadically down
Could be go further regarding the 1000 requests before killing the worker process? In my understanding, it takes some time to start the process, so a higher value should be more efficient (given everything works). If I set the value to 50, that would just be enough to server the homepage 10 times (1 HTML + 4 images). Having about 30 requests per second, wouldn't the server spend a lot of time on starting new processes?