Upgraded RT and Ubuntu and now Apache2 can't find RT::Mason

RT Users
1

I’m a Linux newbie. I’m running Ubuntu 8.04 (I just upgraded from 7.0.4). I
am running RT 3.8.1 (I just upgraded from 3.6). I happen to be running
TikiWiki on this server and it’s working just fine (so, at least I know that
Apache is working - and the server is serving Web pages in general).

My Apache2 error log shows that it can’t find RT::Mason.

I noticed that my old apache config referenced a file ‘webmux.pl’ - which
didn’t exist in /opt/rt3.8/bin/ and did exist in
/etc/request-tracker3.6/bin/. So, I copied the file to /opt/rt3.8/bin and
updated the Apache Config to reference the new file location.

So, if I comment out the webmux.pl line in the Apache config - I get a 404
error. If I leave it in, I get a 500 Internal Server error.

I feel like I’ve been very high maintenance with this upgrade. I can’t tell
you all how extremely helpful you’ve been! Thanks all,
-Chris

2

I’m a Linux newbie. I’m running Ubuntu 8.04 (I just upgraded from 7.0.4). I
am running RT 3.8.1 (I just upgraded from 3.6). I happen to be running
TikiWiki on this server and it’s working just fine (so, at least I know that
Apache is working - and the server is serving Web pages in general).

My Apache2 error log shows that it can’t find RT::Mason.

I noticed that my old apache config referenced a file ‘webmux.pl’ - which
didn’t exist in /opt/rt3.8/bin/ and did exist in
/etc/request-tracker3.6/bin/. So, I copied the file to /opt/rt3.8/bin and
updated the Apache Config to reference the new file location.

This is very strange. If you look into archive of RT 3.8.1 then you’ll
find webmux.pl there. So you missed some error/problem message during
installation of RT 3.8.

Also, don’t copy anything from 3.6 into 3.8, you have archive of 3.8
for that, but you should not copy anything manually in regular
situation.

So, if I comment out the webmux.pl line in the Apache config - I get a 404
error. If I leave it in, I get a 500 Internal Server error.

When you get internal server error then your next step should be
looking into apache error log. 500 itself is useless without info from
logs.

I feel like I’ve been very high maintenance with this upgrade. I can’t tell
you all how extremely helpful you’ve been! Thanks all,
-Chris

Best regards, Ruslan.