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

Fri Jan 9 14:46:09 EST 2004

If you want to check out what mod_perl is doing in more detail:
Make sure Apache::Status, Devel::Symdump, and B::Size perl modules are
installed and then put this in your httpd.conf:

PerlModule Devel::Symdump
PerlModule B::TerseSize
PerlModule Apache::Status
<Location /perl-status>
       SetHandler perl-script
       PerlHandler Apache::Status
       PerlSetVar StatusOptionsAll On
</Location>

I question whether the issue is actually the number of processes
(mnysqld/httpd) or perhaps something lower level.

What type of system are you running this on? CPU, Memory

Have you looked in /var/log/messages (or it could be /var/log/syslog) and
see if there are any actual system errors.

Also, do a top on the box and watch it.  Is it swapping a lot, using all
available memory/shared memory?

When RT crashes try logging into the db from the command line.  With the
rt_user and not the root user.  If it really is a mysqld problem, it
shouldn't let you log in.

I have attached two sample my.cnf files from the mysql distribution

-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Ben Goodwin
Sent: Friday, January 09, 2004 8:22 AM
To: rt-users at lists.bestpractical.com; Frank Saxton
Subject: Re: [rt-users] RT3 is spawning 2 additional processes every
timesomething is done

Nothing unusual in your apache status.  Same type of thing I see.  I do
notice that my RT requests 'round robin' between 2 sets of apache processes
like yours do.  I'm not sure why it does that (perhaps it's by design, but I
thought HTTP keepalive would keep you hitting the same servers).  You should
have 7 or 8 MySQL processes in 'sleep' for that apache status you  sent.
The MySQL timeout should help, as would the apache config changes others
have emailed about.
When you say 'the RT web connection dies' (when you hit 14 mysql procs),
what does that mean, exactly?  What message do you get and/or what happens?
Perhaps we're barking up the wrong tree...

    -=| Ben

----- Original Message ----- 
From: "Frank Saxton" <frankie at easyrider.com>
To: <rt-users at lists.bestpractical.com>
Sent: Thursday, January 08, 2004 8:36 PM
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
>

_______________________________________________
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: my-small.cnf.sample
Type: application/octet-stream
Size: 2418 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20040109/844b45de/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: my-medium.cnf.sample
Type: application/octet-stream
Size: 4833 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20040109/844b45de/attachment-0001.obj>