The usual IT babble
Lighttpd issues
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!
| Print article | This entry was posted by Christian on Saturday, 11th July, 2009 at 06:39, and is filed under Life. Follow any responses to this post through RSS 2.0. Both comments and pings are currently closed. |
No comments yet.
My neverending lighttpd troubles
about 1 year ago - Comments Off
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
Lighttpd troubles resolved
about 1 year ago - 1 comment
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,
Weird lighttpd troubles
about 1 year ago - 1 comment
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
Firefox: Hosting Xmarks (formerly Foxmarks) on lighttpd
about 1 year ago - Comments Off
Well, I am an enthusiastic user of Xmarks (or Foxmarks) and played with this again and again. So this weekend, I finally decided to do it properly. I sat down, recreated the whole WebDAV stuff (even if I cheated of this HowtoForge article). Always redirect traffic to HTTPS, since transmitting username and passwords via HTTP
Zend Optimizer again
about 2 years ago - Comments Off
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
TYPO3 and MySQL replication
about 3 years ago - Comments Off
Apparently the TYPO3 version we are using, doesn’t play too nice with the MySQL Master< ->Master replication. Sometimes, something like this is going to happen: 070826 0:44:32 [ERROR] Slave: Error ‘Duplicate entry ’75-222419149′ for key 1′ on query. Default database: ‘t3nb’. Query: ‘INSERT INTO cache_pagesection 070826 0:44:32 [ERROR] Error running query, slave SQL thread aborted.
SLES, ZendOptimizer and IBM PowerPC(4)+
about 3 years ago - 2 comments
What would you figure from the above ? Hopefully the rather obvious, that it’s a *really* shitty combination. So we figured it would be a nice thing to test our new setup before going into pre-production testing or production, but we don’t have an extra spare box. So we took one of the power4 boxes
Comments are closed.