Posted by Christian in Life
Well, after a day or so my lighttpd troubles reappeared. But this time, the lighttpd process would simply put out this:
(mod_fastcgi.c.2913) backend is overloaded; we'll disable it for 2 seconds and send the request to another backend instead: reconnects: 0 load: 131
(mod_fastcgi.c.2668) fcgi-server re-enabled: 0 /var/run/lighttpd/lighttpd-fastcgi-php-17242.socket
(mod_fastcgi.c.2913) backend is overloaded; we'll disable it for 2 seconds and send the request to another backend instead: reconnects: 0 load: 131
(mod_fastcgi.c.2668) fcgi-server re-enabled: 0 /var/run/lighttpd/lighttpd-fastcgi-php-17242.socket
And as the message says, PHP (or rather mod_fastcgi?) would simply stop to process requests. In the end, I tuned some of the lighttpd/mod_fastcgi parameters.
"max-procs" => 2
"idle-timeout" => 20,
"socket" => "/tmp/php.socket-" + var.PID,
"bin-path" => "/usr/bin/php-cgi",
"bin-environment" => ( "PHP_FCGI_CHILDREN" => "6",
"PHP_FCGI_MAX_REQUESTS" => "7000" )
Up till now (I made the change on July 14th), these changes seem to have fixed the issue, guess I’m still hoping (with the saying “Hope dies last” in mind) it’s gonna fix my problems once and for all.
Posted by Christian in Life
At first, it seemed that my lighttpd issues were resolved by updating PHP/remerging lighttpd. But apparently not. After putting in a crontab entry, that restarts lighttpd every 15 minutes (which completely sucks), the issue was minimized in it’s impact but not really solved.
*/15 * * * * root /etc/init.d/lighttpd restart &>/dev/null
Thanks to Michél (I guess, again) — who helped me looking at the strace logs, and of course Christian (aka hoffie — one of my old Gentoo buddies), the issue seems finally resolved. It turns out it was neither a PHP nor lighttpd issue. It was a simple matter of (stale) symlinks in /etc/ssl/certs if you can imagine that. Apparently a stale symlink forced PHP into a loop or something, from which it couldn’t recover on it’s own.
So the thank you is probably to the one, who introduced those lines to the ca-certificates ebuild (guess, that would be vapier, the old code monkey):
if [[ $badcerts -eq 1 ]]; then
ewarn "You MUST remove the above broken symlinks"
ewarn "Otherwise any SSL validation that use the directory may fail!"
ewarn "To batch-remove them, run:"
ewarn "find -L ${ROOT}etc/ssl/certs/ -type l -exec rm {} +"
fi
After letting the find run through /etc/ssl/certs and restarting lighttpd in the process, everything is back to working order! Finally!
Posted by Christian in Life
Well, after last weeks lighttpd troubles with PHP (or was it without ?), they finally seem resolved. First thing I did, was upgrade to the new php-version (5.2.10). After that, I ran revdep-rebuild, which apparently found issues with lighttpd being linked to a wrong pcre-version. After remerging lighttpd the issues seem to be gone!
Well, guess I was to quick in saying the problem was resolved .. it’s still there, just not happening as fast as it would in the past ….
Posted by Christian in Life
Well, since about a week or so I keep having troubles with my vHost and lighttpd. The point being, after some time (up till now it’s been something between days and minutes) lighttpd completely freezes and doesn’t serve no content anymore. I don’t know if this is related to PHP (might be, I did perform an update to dev-lang/php-5.2.9-r2 on Thu May 28 12:18:57 2009), but I have to figure this out since the restart cron-job is getting annoying.
Well, it seems like lighttpd is getting stuck in mod_fastcgi …
2009-06-23 21:34:40: (mod_access.c.135) -- mod_access_uri_handler called
2009-06-23 21:34:40: (mod_fastcgi.c.3675) handling it in mod_fastcgi
2009-06-23 21:34:40: (mod_fastcgi.c.3005) got proc: pid: 11151 socket: unix:/var/run/lighttpd/lighttpd-fastcgi-php-11147.socket-0 load: 85
Usually the last line is followed by a line telling that it released the proc, but not always.
Posted by Christian in Life
Well, I happen to be back at my favorite application. Today I stumbled upon a “nice” thing. If you turn on the Zend Optimizer (doesn’t matter whether it is 2.6.2 or 3.3.0), one of the TYPO3 back ends ain’t showing *any* content in the preview pane. Once you turn the Zend Optimizer stuff off, it works without a problem.
O RLY ?
And as Zend stated on their “Support Forum“, they don’t really support the Zend Optimizer stuff in the first place. Which is nice, what for do you need the Zend Guard shit in the first place ??
Well, so I do have two options now:
- Disable the one plug-in, which really needs the Zend Optimizer (as it also features the Zend De Guard engine – or whatever you want to call it)
- or risk some other things breaking due to the Zend Optimizer engine not working (correctly) with php-5.1.2 (which is rather old considering 5.3.0 is in development right now)
But I will see about that tomorrow …
YA RLY!