[rt-users] RT3 is spawning 2 additional processes every time something is done

[AJ]

Actually, perhaps someone out there can help, but I remember SOMEWHERE I
read that having a short refresh can cause bad things to happen...

Okay, here it is:
http://lists.fsck.com/pipermail/rt-devel/2001-March/000953.html

http://lists.fsck.com/pipermail/rt-devel/2001-March/001030.html is later but
same thread 


Its an old one from someone with a similar problem of apache and spawning
two processes.  It might help.


Have you tried
log=<PATH>/mysqld.log in the my.cnf.  Perhaps that will give you more info.

Also, if you are using a binary dist of redhat, there is a 'support-files'
directory in there with sample my.cnf files for small, medium, large, and
huge dbs..

Grab one, copy it to wherever it needs to be and rename it to my.cnf and see
what happens. :)

Back up your existing one. 

Last but not least set MaxClients in the httpd.conf to something low and set
MaxRequestsPerChild to 200 or so..

Don't give apache enough time to run up mysql



-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Frank Saxton
Sent: Thursday, January 08, 2004 8:37 PM
To: rt-users at lists.bestpractical.com
Subject: [rt-users] RT3 is spawning 2 additional processes every time
something is done

Thanks ben!

I am running apache-1.3.27-4

Set the wait timeout to 300.  If that's still too short, I can increase it.

And yes, I am the only one running RT and I have just one session logged 
in.  I have refresh set to very 2 minutes.

Apache appears to be running very well.  I have a couple of other 
applications that use it and I'm not seeing any problems (that's not to say 
that there might not be possible configuration setting improvements)

Server-status follows:

Server Version: Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_python/2.7.8 
Python/1.5.2 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 
mod_perl/1.26 mod_throttle/3.1.2
Server Built: Dec 10 2003 05:05:00

----------
Current Time: Thursday, 08-Jan-2004 17:33:01 PST
Restart Time: Thursday, 08-Jan-2004 17:25:21 PST
Parent Server Generation: 0
Server uptime: 7 minutes 40 seconds
Total accesses: 15 - Total Traffic: 67 kB
CPU Usage: u2.88 s.18 cu0 cs0 - .665% CPU load
.0326 requests/sec - 149 B/second - 4573 B/request
1 requests currently being processed, 7 idle servers
_______W........................................................


Srv PID Acc M CPU SS Req Conn Child Slot Client VHost Request
0-0 10525 0/2/2 _ 0.50 458 489 0.0 0.00 0.00 216.99.212.113 
rt.vigilancemonitoring.com GET /rt/ HTTP/1.1
1-0 10526 0/2/2 _ 0.50 141 21 0.0 0.01 0.01 216.99.212.113 
rt.vigilancemonitoring.com GET /rt/NoAuth/webrt.css HTTP/1.1
2-0 10527 0/2/2 _ 0.11 458 0 0.0 0.01 0.01 216.99.212.113 
rt.vigilancemonitoring.com GET /server-status HTTP/1.1
3-0 10528 0/2/2 _ 0.85 8 1566 0.0 0.02 0.02 216.99.212.113 
rt.vigilancemonitoring.com GET /rt/Ticket/Display.html?id=8 HTTP/1.1
4-0 10529 0/2/2 _ 0.50 7 21 0.0 0.01 0.01 216.99.212.113 
rt.vigilancemonitoring.com GET /rt/NoAuth/webrt.css HTTP/1.1
5-0 10530 0/2/2 _ 0.49 4 397 0.0 0.01 0.01 216.99.212.113 
rt.vigilancemonitoring.com GET /rt/ HTTP/1.1
6-0 10531 0/2/2 _ 0.11 268 112 0.0 0.01 0.01 216.99.212.113 
rt.vigilancemonitoring.com GET /rt/NoAuth/webrt.css HTTP/1.1
7-0 10532 0/1/1 W 0.00 233 0 0.0 0.00 0.00 216.99.212.113 
rt.vigilancemonitoring.com GET /server-status HTTP/1.1

cache type: DBM, maximum size: unlimited
current sessions: 1, current size: 152 bytes
average session size: 152 bytes

----------
Apache/1.3.27 Server at rt.vigilancemonitoring.com Port 443

_______________________________________________
rt-users mailing list
rt-users at lists.bestpractical.com
http://lists.bestpractical.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm