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.
After a few tries I restarted the server to receive this error, despite
Apache saying it isn’t running:
- Starting web server apache2
(98)Address already in use: make_sock: could not bind to address
0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
I removed the link to /opt/rt3/etc/apache2-modperl2.conf and Apache ran
fine.
I edited /opt/rt3/etc/apache2-modperl2.conf and removed this line:
#PerlRequire /opt/rt3/bin/webmux.pl
Apache was able to start normally.
If I enable that line again and attempt to start Apache it just sticks
with this line:
- Starting web server apache2
Nothing is entered into the Apache logs or the rt.log file.
I installed a brand new Ubuntu 10.10 server along with RT and had the
exact same problem.
Does anyone have any ideas what might be going on or how to fix it?
Thanks.
No one have the slightest idea about this?From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Alex
Young
Sent: 02 December 2010 16:49
To: rt-users@lists.bestpractical.com
Subject: [rt-users] webmux.pl causing Apache to fail
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.
After a few tries I restarted the server to receive this error, despite
Apache saying it isn’t running:
- Starting web server apache2
(98)Address already in use: make_sock: could not bind to address
0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
I removed the link to /opt/rt3/etc/apache2-modperl2.conf and Apache ran
fine.
I edited /opt/rt3/etc/apache2-modperl2.conf and removed this line:
#PerlRequire /opt/rt3/bin/webmux.pl
Apache was able to start normally.
If I enable that line again and attempt to start Apache it just sticks
with this line:
- Starting web server apache2
Nothing is entered into the Apache logs or the rt.log file.
I installed a brand new Ubuntu 10.10 server along with RT and had the
exact same problem.
Does anyone have any ideas what might be going on or how to fix it?
Thanks.
[…]
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.
- #595054 - request-tracker3.8: Race condition between RT3.8+apache2 and MySQL when booting by insserv - Debian Bug report logs
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.From: Konstantin Khomoutov [mailto:flatworm@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
[…]
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.
- http://bugs.debian.org/595054