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.

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):

After letting the find run through /etc/ssl/certs and restarting lighttpd in the process, everything is back to working order! Finally!

Hammock

Well, out of boredom I stated on Friday that I’d gonna go look for a hammock, since the beach chair quite isn’t enough. I went through every DIY superstore in Stralsund, but none of them had anything like I wanted (basically I wanted a wooden hammock, which would be able to carry me). Thanks to the Internet though, I was quite fast at a point where I found something (Amazon rules!)

At first I picked only a mat which I canceled right after I got the confirmation mail. After about 10 minutes I finally found a hammock with frame, which actually suited what I had in mind. Now, the excerpt on the Web page tells something about “Usually ready for dispatch in 6 till 10 days“. On Tuesday the hauler’s office called me at work (I completely forgot, that I supplied my work phone number as number during the day — which completely surprised me), they would like to deliver the hammock on Wednesday.

On Wednesday, they delivered the ~70 kg heavy crate, which we ferried with the wheel barrow to the rear part of the lot. Yesterday, my dad and I put the thing together and I had a first sun bath test.

 

Hammock with frame
Hammock with frame

Updating a Linux VM from Virtual Infrastructure to vSphere

Well, if you’re gonna update a SLES10 (or even a SLES11) VM, you created with Virtual Infrastructure, you’re gonna run into a snag (like I do). Grub (or rather the kernel itself) is gonna barf.

Now, I searched for a while and didn’t find anything specific on the net, so I’m gonna write it down. Up till 3.5U4 the maximal resolution you’d be able to enter within a virtual machine was vga=0x32d (at least for my 19″ TFT’s at work). But now, after the upgrade to vSphere that isn’t working anymore.

Popped in a SLES10 install-cd selected the maximal resolution from the menu and switched to a terminal soon after it entered the graphical installer. A short cat /proc/cmdline revealed this: vga=0x334.

After switching these parameters in grub’s menu.lst, everything is back in working order and not waiting 30 seconds on boot …