Hi,
We're running 3.6.1 in production (the same applies to 3.6.3 in test), and Pg
version 8.1.8, and FastCGI (mod_fcgi-2.4.2), and Perl 5.8.7.
Sometimes we experience tickets that only shows ticket metadata, and not the
whole ticket including history. Everything looks 'ok' in the database:
Hi,
We have checked the problem more closesly, and the reason why our
RT/Apache server stops is due to different variants of mail loops.
We still have problems with other loop variants consuming all resources.
Extended mailgate errors leading to loops, spam going into loop. How can
we make
-- Forwarded message --
Date: Wed, 7 Feb 2007 11:38:33 +0100 (CET)
From: Tomas Olaj [EMAIL PROTECTED]
Reply-To: Tomas Olaj [EMAIL PROTECTED]
To: rt-users@lists.bestpractical.com
Subject: mail loop problems: was: Re: [rt-users] RT/Apache suddenly hangs
Hi,
We have checked
On the marvelous Fri, 2 Feb 2007, Torsten Brumm wrote kindly to me ...
The only thing i found sometimes are messages: Mysql server has gone away,
but this is causing not in all cases the problems. Nightly, without RT
usage, the connections from FastCGI are timing out and don't connect
System:
===
Red Hat Enterprise Linux WS release 3 (Taroon Update 8)
RT 3.6.1
Apache v2.0.59
Perl 5.8.7
mod_fcgi-2.4.2
Postgres 8.1.4
Approximately 80.000 tickets.
Problem:
RT/Apache suddenly becomes unavailable/hangs (normaly once a day), and
requires Apache restart so RT can
On the marvelous Wed, 6 Dec 2006, Jesse Vincent wrote kindly to me ...
We are entering production phase next week on 3.6.1, but we noticed a
problem among Internet Explorer version 6 users (yes, there are some of
these at our university), ;), where they are getting an Error on page
Hello,
We are entering production phase next week on 3.6.1, but we noticed a
problem among Internet Explorer version 6 users (yes, there are some of
these at our university), ;), where they are getting an Error on page
error-message in browser trying to _open_ a ticket in RT 3.6.1.
This
Hi,
Sometimes we encounter tickets with empty content, e.g. no history
displayed by RT/Apache. But, looking into the database it seems like
everything is stored of replies, updates, etc...
Any tip or hint what we should look into to find out why RT won't display
those tickets? I cannot see
This test performance was done by our Postgres DBA Rafael Martinez. I am
translating this so You can agree or disagree if this makes sense or not.
Adding indexes can for sure improve performance.
--
Tomas A. P. Olaj,