Friday, August 21, 2009

Switched to Zine

Update: Since writing this post, I've moved the blog to Blogger. Turns out, I'm not fond of system administration. Besides, Blogger has shiny gadgets, widgets and whatnots.

I’ve moved the blog to Zine and to a different server. Zine is quite nice. I’d like to see a plugin that implements one of the common APIs so that I can use a blogging client like ScribeFire. After installing this ReST plugin I was able to migrate the (little) content from my semi-homegrown blog into Zine. The import from an atom feed didn’t work for me for some reason.
The old blog was down quite a bit. When I noticed that the other day I had a look and found out what the problem was. There was a cron job, running imapfilter to filter my mails directly on the mail servers, so they would be filed correctly in all clients on all machines I use. Among those mail servers are those from Google. Apparently Google had some problems with their SSL certificates, since running imapfilter from the shell produced the following output:
Server certificate subject: /C=US/ST=California/L=Mountain View/O=Google Inc/
Server certificate issuer: /C=US/O=Google Inc/CN=Google Internet Authority
Server key fingerprint: 35:D1:0A:42:F3:FE:61:4E:CD:0C:02:05:D1:CC:D9:52
ATTENTION: SSL/TLS certificate fingerprint mismatch.
Proceed with the connection (y/n)?
Sigh. So there were hundreds of imapfilter processes sitting there, waiting for input. The CPU was maxed out, but sorting by CPU load in top didn’t identify the culprit. No process was using much CPU time by itself. Death by scheduling. So, Google: Fix your SSL certificates. Or was it a mitm attack…? Of course, it couldn't possibly be my fault, right? ;)

No comments:

Post a Comment