Apache

Well, I use ViMbAdmin for the mail box administration of my users (and aliases) on heimdaheim.de. After I while (well, over half a year I guess), I decided to look at it again. However it didn’t work. Well this was a multi-part problem. ViMbAdmin has been updated to require PHP composer (which populates the vendor/ folder) the application.ini was outdated After I fixed all that, ViMbAdmin was working again. However I decided to replace my mod_rewrite stuff (I had in my apache config from the previous version) with the one from the Documentation and that actually made things worse. So I ended up redigging into mod_rewrite (again sigh) and rewrite the Rewrite Rules… This time I’m documenting it. ...

Well, I just finished my wild-goose chase with Apache and subversion regarding a rather weird error. I recently reinstalled our subversion box, and ever since then I was unable to commit anything new to any of the repositories. Subversion told me this: 1 2 3 svn-client admin-scripts [1] > svn ci -m "Directories for Tivoli Storage Manager Scripts." svn: Commit failed (details follow): svn: MKACTIVITY of '/svn/admin-scripts/!svn/act/someid': 302 Found Apache didn’t say much about it either, besides this particular line: ...

Okay, so I ended up toying with subversion via WebDAV on SLES today (I know, I know .. it’s bloody Sunday). It wasn’t much of a hassle though, after reading this. Sure, I made a few errors at first (simply confused the logic behind " Location" and " Directory"), but after that plain subversion commits via WebDAV (thus utilizing Apache) worked fine. For POC or as a hint to myself, here’s where and what I needed to add/change: ...

We’re finally making some progress with apache-2.2. It left the package.mask on the 8th of May (that’s like 3 weeks from tomorrow), we split some helper scripts into a separate package (app-admin/apache-tools). I already fixed a few screwup I did myself (like apxs missing from either apache and apache-tools, or the compatibility symlinks being missing), so we “just” need to fix all the modules in the tree before apache-2.2 is going to get the new stable version (and of course anything else depending on. What also remains to do, is committing the new-style virtuals for bug 11007. ...

OK, so today was the highlight of the week … We updated apache2 on Tuesday (yeah, that’s still 2.0.49, so if you have some exploits - try them 😛 ) and now out of the sudden we have major performance issues. We looked nearly the whole forenoon for a reason, why the frackin’ apache was using 236% of the CPU’s. In the afternoon, when my co-worker decided to go home (that was ~1500), I decided to revert back to the old patch level. But that isn’t as easy as you think (at least on SLES). The only thing I wanted to do, was something like this: ...