I’m currently evaluating RT3 (3.0.5) on a server running Redhat 9 and am experiencing problems with attachments and occasional Storable.xs errors.
My question is -
What would be the recommended software configuration for running a stable, fully functional RT3 deployment based on Linux?.
I have the opportunity to start afresh so rather than trying to fix the current broken bits, I figure getting some recommendations now will get me going quicker.
Darren
This message has been checked for all known viruses by the
CitC Virus Scanning Service powered by SkyLabs. For further information visit http://www.citc.it
I’m currently evaluating RT3 (3.0.5) on a server running Redhat 9 and
am experiencing problems with attachments and occasional Storable.xs
errors.
My question is -
What would be the recommended software configuration for running a
stable, fully functional RT3 deployment based on Linux?.
RedHat 9 has a recorded history of having the ‘wrong’ versions of some
packages, which have bugs that render RT3 problematic.
People have been running RT3 on RedHat8, tweaked RedHat9, BSD, and
debian boxen, AFAIR. There are also instructions available for
instaling it onto a MacOSX Server.
Basically, the idea is to stay away from mod_perl2, as it is not
released yet, and updating the perl modules needed by RT.
There are RT3 packages available for debian testing/unstable, I can’t
recall from the top of my head if there is also a backport to stable.
We had great success using debian/unstable over here.
Thanks for the info, I will maybe try Debian unstable, anyone else have any recommendations?.
Cheers DarrenFrom: Harald Wagener [mailto:hwagener@hamburg.fcb.com]
Sent: 25 November 2003 09:47
To: Marshall, Darren
Cc: rt-users@lists.fsck.com
Subject: Re: [rt-users] Recommended configuration for a stable working
RT3 deployment
I’m currently evaluating RT3 (3.0.5) on a server running Redhat 9 and
am experiencing problems with attachments and occasional Storable.xs
errors.
My question is -
What would be the recommended software configuration for running a
stable, fully functional RT3 deployment based on Linux?.
RedHat 9 has a recorded history of having the ‘wrong’ versions of some
packages, which have bugs that render RT3 problematic.
Thanks for the info, I will maybe try Debian unstable, anyone else have any recommendations?.
Due to the nit picky dependencies and required compiler options of all
the various components, IMHO the best way to handle this is to download
and compile all the various bits and pieces and installed them in a
local tree (such as /usr/local.) When I say “all the bits and pieces”,
I’m referring to perl, apache, mod_perl, and all the perl modules. You
might get away with the version of MySQL that comes with the OS however.
It seems like a large task (and IS to a certain extent) but it’s well
worth it in the long run. You are creating a stable environment so that
it’s MUCH less likely that OS changes / upgrades will break your RT
environment. If you are creating a production installation, this is what
I would recommend.
Debian unstable changes a LOT. If you keep your system up to date, RT
will eventually break.
HOWEVER, RT is also a debian package. You can just “apt-get install
request-tracker3” and go. This “should” always work, but again: you are
working with an unstable branch.
What would be the recommended software configuration for running a
stable, fully functional RT3 deployment based on Linux?.
RedHat 9 has a recorded history of having the ‘wrong’ versions of
some
packages, which have bugs that render RT3 problematic.
Thanks for the info, I will maybe try Debian unstable, anyone else
have any recommendations?.
[snip]
IMHO the best way to handle this is to download
and compile all the various bits and pieces and installed them in a
local tree (such as /usr/local.)
[snip]
It seems like a large task (and IS to a certain extent) but it’s well
worth it in the long run.
This is how I got RT3 working for RH9, so it is a way to go.
Debian unstable changes a LOT. If you keep your system up to date, RT
will eventually break.
Yes, You have to be careful.
HOWEVER, RT is also a debian package. You can just “apt-get install
request-tracker3” and go. This “should” always work, but again: you are
working with an unstable branch.
You can also go with testing. Again, I don’t remember if there is a
backport to stable.
Thanks for the info, I will maybe try Debian unstable, anyone else have
any recommendations?.
I didn’t reply the first time around because it’s not Linux, however
FreeBSD is a very stable environment for running RT. We are in our fourth
year of using RT (started with v1 now using v3) on FreeBSD and I would do
it all over again.
After spending several weeks (little over a month) trying to get RH8 to
work with RT, I decided to regress to 7.3. I’ve set up many systems
with the older versions of Apache and mod_perl, so I don’t really see a
current need to have the very latest and greatest.
My suggestion would be to install RH 7.3, remove the RPMs for Apache and
mod_perl. Download the source for apache 1.3.29, mod_perl 1.29, MySQL
server client and development (you have to download the MySQL
development package…it’s buried in the docs, but you must have it for
RT).
JohnOn Tue, 2003-11-25 at 10:00, Marshall, Darren wrote:
Harald,
Thanks for the info, I will maybe try Debian unstable, anyone else have any recommendations?.
On Tue, Nov 25, 2003 at 10:59:53AM +0000, John Schubert said:
After spending several weeks (little over a month) trying to get RH8 to
work with RT, I decided to regress to 7.3. I’ve set up many systems
with the older versions of Apache and mod_perl, so I don’t really see a
current need to have the very latest and greatest.
Huh. I’m running it on RH8, but again: I compiled all my own stuff and
did not rely on the redhat binaries.
My suggestion would be to install RH 7.3, remove the RPMs for Apache and
mod_perl. Download the source for apache 1.3.29, mod_perl 1.29, MySQL
server client and development (you have to download the MySQL
development package…it’s buried in the docs, but you must have it for
RT).
If you are going to go through the trouble and compile your own
binaries, you also might as well go with a modern version of the OS.
Remember that all non-enterprise versions of RedHat are EOL at this
point. You may want to consider Suse, Mandrake, Debian, or even
Enterprise RH.
Remember that all non-enterprise versions of RedHat are EOL at this
point. You may want to consider Suse, Mandrake, Debian, or even
Enterprise RH.
I run my test system at Debian Sarge, it’s fine !!
For RH EOL, unfortunately, we run many RH “boxen” (one with RT2) and think
to switch over soon to woody, or next year to sarge, because I searched for
a fedora eol statement of “eratas/bugfixes”, and I couldn’t find?
I didn’t reply the first time around because it’s not Linux, however
FreeBSD is a very stable environment for running RT. We are in our fourth
year of using RT (started with v1 now using v3) on FreeBSD and I would do
it all over again.
I am currently running RT3 on Red Hat 9. While it has been relatively
trouble-free after the initial setup hassle, I will probably move to FreeBSD
for Request Tracker hosting. FreeBSD is less in flux than Red Hat, and less
quirky, at least in terms of RT installation.