wiredfool

Mood: Calming Down.
Music: Burning Down the House (Talking Heads)

Well now. That was a nice little arc welding experiment in the oven just now. And me with a nicely heated stone and pretty well proofed bread. I was getting ready to stick a couple of loaves in, and I noticed quite a bright light from the bottom of the oven. Closer inspection told me that I didn’t really want to look directly at it. It was slowly spiraling the element fading in and out of view. Lots of sparks too. A couple of minutes after turning off the oven, I decided that I’d really rather have it stop. I wasn’t actually sure if it was an arc or just burning aluminum, but after putting a soaked cloth diaper on it and both not seeing it stop and half of the element still glowing red, I had Rose kill the breaker to the stove. That and the wet cloth stopped it. I was prepared to use the dry fire extinguisher, but I really didn’t want to coat the kitchen in the chemicals if I didn’t have to.

I know that we’ve fried the element, as it’s in a couple pieces. I suspect the controller’s dead, since it didn’t kill power to the element when I turned it off. And the bread is quite interrupted. Grrr. I wanted bread.

I doubt it’s going to be cheap to fix the controller, and I really don’t think that it’s going to be cheap to replace the whole stove.

Update — Replaced the main bake element, and things seem ok. The controller seems to work, the oven seems to heat up faster, and there’s no more scary arcing. For now anyway.

I did most of the structural design of this bridge a little more than 10 years ago now. It still looks pretty good. This is from a Film Photostroll that I did back in January — just got the film back from the developer, along with bits and pieces and tails of rolls, and one roll that was undeveloped for at least a year and a half. That’s not exactly recommended, as the grain is something fierce.

Round about mid-November, email sorta blew up here. It took a good weekend of not so spare spare time to get it sorta back working, including some horrific hacks that really shouldn’t be necessary and turned out to have subtle bugs that would do things like drop paypal emails on the floor. And it all started because spamhaus put the entirety of slicehost into a policy block list. Slicehost is a virtual machine provider where people tend to start up a machine and leave it running, doing long term businessy or useful stuff until the need arises for something bigger. That’s ok, except that mail comes into my slice, then gets forwarded to a place that uses that policy black list. PITA really.

And after all the effort to go through and fix that, now I needed to update that slice from oldstable to current debian stable because clamav (the virus scanner) basically blew up on an update and wouldn’t run in daemon mode. So, it forks a process for each incoming mail, which kills the performance and makes Slicehost send me nasty emails about swapping and heavy disk access. So, I need two things: currentish code and updates and more memory. And the best way to add memory is to use less of it. And the image size of the programs that I’m using is a lot smaller (1/2-1/3) in the 32 bit distribution vs the 64 bit distribution. This is something that other people have noted with Slicehost vs other virtual private server providers.

So, Upgrading Etch (x64) to Lenny (i386). Or shall I say, how to install 32 bit Lenny on a 64 bit slice. The adventurous could likely do this on one slice, I’m building a new one so that I don’t kill services while I twiddle with things. There’s a really useful wiki article that covers the majority of what needs to happen. The only real changes are to use arch=i386 in the debootstrap command, and make sure that lenny is the distribution that you select anywhere there’s an etch in that article. Also, you need to delete the existing lib64 directory when you blow away the initial install.

After that, the important bits of making athe mail server play nice include merging all the old configs, which basically works. The Clamav user needs to be added to the amavisd group and clamav-daemon restarted. I also had to set rw permissions on /dev/null for everyone, I’m not sure if that’s a bug in the udev bits or in the copying of the devs over to the new system.

If I need more memory, I may move the one website off that machine and onto Dreamhost, as I see that they have started doing WSGI now, and that would make it reasonably easy to host this pylons site.

(edit: and then, just to make sure that I was paying attention, Dreamhost decided to deliver additional copies of all email in my pop account every time I checked starting 24 hours after I did this.)