It seems that my attempt to update one of my servers (Running Suse 9.1, although that will be coming to a swift end here in the next few hours) with the latest Subversion build required an upgrade to the libapr0 library which in turn required that I upgrade to the Apache 2.54 build. Somewhere in this mix somebody didnt like someone else and I found myself with a dead Apache instance although I could start it, stop it, restart it, and everything seemed just fine. But it definitely wouldn't serve any pages so I've spent the last hour and half frantically downgrading everything which, to much my relief, seemed to work just fine.
None-the-less, the Subversion 1.0 developers build that this server is running is so outdated that I fear incompatibility issues are lurking just around the corner. If I was some sort of Linux guru I'm sure I would happily be able to get things taken care of without resorting to a complete hard drive/database backup to then wipe that drive clean to prepare it for a new installation, this time implementing Fedora Core 4 to compliment the Win2k3 box sitting beside it. What this means to you is that there may be some flickering of the lights over the next few hours but with as much source code as I have foolishly mounted on top of that SVN 1.0 developer build I really can't take any chances. My apologies in advance if you experience difficulties accessing any of the sites hosted on that server over the next few hours (e.g. XSLTWiki, XMLWiki, Kurts UnderstandingXML, my UnderstandingXSLT, weblog.saxondotnet.org, this site, and a few others.)
TrackBack URL for this entry:
http://www.xsltblog.com/xslt-blog-mt/mt-tb.cgi/909