A Little Life Support for Typo

Paul Brown @ 2007-09-13T04:31:00Z

I've been busy, but I haven't been so busy that I couldn't find a little time to blog. I have been busy enough that I couldn't find time to diagnose why Typo would give me an HTTP 500 after a very long pause whenever I tried to post. I finally found the time, and a little poking around was enough to suggest that 250k rows in the sessions table was a bit much for the way I have MySQL configured.

The bloated sessions table was the result of the default configuration that uses the database to manage sessions. Truncating the table plus a switch over to memcached for session management (as per Err) have me back to a usable configuration.

(comment bubbles) 0 comments
(new comment bubble) Add a comment.

Apache2 + mod_fcgid + Rails

Paul Brown @ 2006-11-05T20:39:46Z

With a default Typo configuration running on lighttpd, it was producing more output in the error log than in the access log with something about "missing cleanup", so I finally got around to migrating over to apache2 and mod_fcgid. (The short-term solution was a couple of cron jobs to keep the lighttpd process up.) The usual configuration work (see, e.g., James Duncan Davidson's write-up) was a dead-end, but turning up the logging verbosity on the apache2 instance had the solution:

[Sun Nov 05 18:13:19 2006] [info] mod_fcgid: read data timeout in 5 seconds

Initialization for one of the processes takes way longer than that, so putting some more sane values into the mod_fcgid configuration along the lines of what Spencer Miles used was the solution. At least so far, the apache2 and mod_fcgid combination is much snappier and more stable than the lighttpd configuration.

(comment bubbles) 2 comments
(new comment bubble) Add a comment.