Whats the best way to debug a 500 on BOA. dblog is empty. No errors in /var/log/nginx/error.log, /var/log/php5-fpm.log, /var/log/php5/php53-fpm.log

Comments

omega8cc’s picture

Status: Active » Closed (works as designed)

The best idea is to read the welcome e-mail (it is sent on Octopus install and upgrades) and the docs listed there, including: http://omega8.cc/how-to-disable-all-caching-and-aggregation-115

You can also check various logs in the /var/log/php/* directory.

lsolesen’s picture

Hm. In my particular case, if I go to the dev.* version of the site everything works as expected. Being on the production site:

tail php53-fpm-error.log

gives

[09-Aug-2012 08:38:31] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:40:40] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:43:19] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:44:15] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:45:10] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:48:44] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:49:04] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:50:11] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:52:08] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it
[09-Aug-2012 08:52:46] WARNING: [pool www] server reached pm.max_children setting (2), consider raising it

I tried increasing pm.max_children to 20 in /etc/php/fpm/pool.d/www.conf. I am on a Linode 1024.

lsolesen’s picture

Status: Closed (works as designed) » Active

I is on the registration page for commerce_registration found on admin/commerce/registrations.

lsolesen’s picture

For me only /var/log/php/php53-fpm-error.log has other content than 'rotate'.

omega8cc’s picture

Status: Active » Closed (works as designed)

For Linode 1024 you could try:

process.max = 8
pm.max_children = 4
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 4

This should be more than enough.

Using pm.max_children 20 may kill your server, as it is many times more than you have RAM available - don't do that.