Thanks for this. Turns out MySQL wasn't accepting connections. Our monitoring system wasn't picking it up as MySQL was still running.
I havent used the Ubuntu package for RT in a long time. I have been happy to install RT manually into the defult location along with RTFM and RTIR, and figure if a new update comes out that would be handy it's a lot easier to just upgrade RT as needed, rather than relying on a package maintainer to update it. -----Original Message----- From: Konstantin Khomoutov [mailto:flatw...@users.sourceforge.net] Sent: 03 December 2010 12:47 To: rt-users@lists.bestpractical.com Cc: Alex Young Subject: Re: [rt-users] webmux.pl causing Apache to fail On Fri, 3 Dec 2010 10:40:49 -0000 "Alex Young" <alexyo...@housingpartners.co.uk> wrote: [...] > I'm receiving an odd error with RT 3.8.8 on Ubuntu 10.4 and 10.10 x64. > Seems to be some kind of update that doesn't play well with webmux.pl. [...] > I removed the link to /opt/rt3/etc/apache2-modperl2.conf and Apache > ran fine. [...] First, is there any reason not to use the stock request-tracker3.8 package available in Ubuntu? Does it have the same error? Otherwise the only idea I have is that the DB backend configured for your RT instance is unavailable at the time apache starts because what webmux.pl does, among other things, is connecting to the specified DBMS. We had a bug with similar symptoms in Debian [1]. In my case, apache failed to start after waiting for a timeout due to inaccessible MySQL server; may be your case is similar just the timeout is not triggered for some reason. 1. http://bugs.debian.org/595054