Reposting to see if some light can be shed. I am very curious…
Performing queries using ‘Requestor = X OR Cc = X OR AdminCc =X’ in 3.6.3
yielded very fast results - a few seconds. However, doing the same search
in 3.6.4 resulted in a timeout after four minutes.
Using ‘Watcher = X’ is the preferred solution, faster, etc (and what I am
using now), yes, but I would expect Requestor or AdminCc queries in 3.6.4
to be just as fast in 3.6.3 not 100x slower. 
If anyone has an explanation, I’d appreciate it.
James Moseley
James
Moseley/BTV/PEGAS
US To
rt-users@lists.bestpractical.com
07/12/2007 04:31 cc
PM
Subject
Re: RT 3.6.4 problems - Fixed
(Document link: James Moseley)
Here was my problem, which was addressed in the announcement for 3.6.4:
Use ‘Watcher =
X’ inestead of
‘Requestor = X
OR Cc = X OR
AdminCc =
X’ in the
SelfService
interface. Both
queries do quite
the same job,
but
the former is
significantly
faster.
I had added a
search to my ‘RT
at a Glance’
that searched
for tickets I
was either CC’d
or AdminCC’d on.
I have now
modified it to
use ‘Watcher’
instead. My
question,
though, what
changed between
3.6.3 and 3.6.4
to actually slow
down searches
that use CC or
AdminCC? It
slowed down so
much that my RT
home page was
timing out…
James Moseley
James
Moseley/BTV/PEGAS
US To
rt-users@lists.bestpractical.com
07/11/2007 11:02 cc
PM
Subject
RT 3.6.4 problems(Document link:
James Moseley)
I am running RT 3.6.3 on two systems: An older Linux system using Apache 2
and Apache’s mod_fastcgi module and an FC6 system with Apache 2 and
mod_fcgid (an alternative to the Apache mod_fastcgi module). Both
installations work just fine.
Prior to installing 4.6.4, I upgraded the few Perl modules on each system
that needed it. My RT upgrade process simply consists of installing RT
from scratch then creating softlinks to the new installation - this way I
don’t write over the working, older installation directory.
However, after switching over to 3.6.4 and restarting Apache, I get ‘500
internal server failure’ errors on both machines. On the older system with
Apache’s fast cgi module, I get:
[Wed Jul 11 20:55:58 2007] [error] [client xxx.xxx.xxx.xxx] FastCGI: comm
with server “/opt/rt3/bin/mason_handler.fcgi” aborted: idle timeout (360
sec)
[Wed Jul 11 20:55:58 2007] [error] [client xxx.xxx.xxx.xxx] FastCGI:
incomplete headers (0 bytes) received from server
“/opt/rt3/bin/mason_handler.fcgi”
On the FC6 system with the alternative mod_fcgid module, I get:
[Wed Jul 11
21:54:26 2007]
[warn]
mod_fcgid: read
data timeout in
40 seconds
[Wed Jul 11
21:54:26 2007]
[error] [client
xxx.xxx.xxx.xxx]
Premature end of
script headers:
mason_handler.fc
gi
[Wed Jul 11
21:54:35 2007]
[notice]
mod_fcgid:
process
/opt/rt3/bin/mas
on_handler.fcgi(
20631)
exit(communicati
on error), get
stop signal 15
[Wed Jul 11
21:55:12 2007]
[warn]
mod_fcgid: read
data timeout in
40 seconds
[Wed Jul 11
21:55:12 2007]
[warn]
(110)Connection
timed out:
mod_fcgid:
ap_pass_brigade
failed in
handle_request
function
No MySQL
database changes
have been made.
There is no
mason cache to
clear since I’m
basically
working with new
installations.
Anyone else
encountering
similar
problems?
Swapping back to
3.6.3 works just
fine.
James Moseley