Re: Apache::SpeedLimit
On Tue, 6 Mar 2001, Daniel wrote: > Hi, I'm having a bit of trouble using Apache::Speedlimit ... > After running for about 5 minutes the handler dies with the following in > the logfile: > > > [Tue Mar 6 17:32:07 2001] [error] [Tue Mar 6 17:32:07 2001] null: > Munged shared memory segment (size exceeded?) I would suggest that you ditch Apache::Speedlimit, since it uses IPC::Shareable which is known to have some performance issues and is giving you grief about memory size. Do a quick search in the list archives for Randal's Stonehenge::Throttle code. It's fairly easy to adapt it to use cookies and to count hits within a time window rather than CPU. It uses files, and doesn't have to lock them. Quite fast under Linux, and even works over NFS if you need a clustered solution. - Perrin
RE: Apache::SpeedLimit and problems with IPC::Shareable
No, I've 5.00502 installed. It is a mess to upgrade to a newew perl (it is a common perl installation across hundreds of machines). I'll ask our software admin team to upgrade, though. Thanks, Christian > -Original Message- > From: Tobias Hoellrich [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 10, 1999 2:51 PM > To: Christian Gilmore > Cc: ModPerl Mailing List (E-mail) > Subject: Re: Apache::SpeedLimit and problems with IPC::Shareable > > > This sounds an awful lot like the problem I ran into when using > Apache::Session's tie in an eval'ed context. See this message: > > http://x31.deja.com/getdoc.xp?AN=536753692&CONTEXT=940379169.1 > 854472193&hitn > um=1 > and > http://www.geocrawler.com/archives/3/182/1999/10/0/2767892/ > > I assume you're using 5.00503 ? > > Hope this helps >Tobias > > > At 01:56 PM 11/10/99 -0500, Christian Gilmore wrote: > >I inserted Apache::SpeedLimit into one of our servers the > other day. It works > >as advertised, but I'm now seeing errors in the error_log > that are coming from > >Apache::SpeedLimit/IPC::Shareable. I wonder if anyone else > has had this > >problem. > > > >>From the error_log: > > > > [Wed Nov 10 13:28:55 1999] [notice] Apache/1.3.9 (Unix) > > mod_perl/1.21 mod_ssl/2.4.2 OpenSSL/0.9.4 configured > > -- resuming normal operations > > [Wed Nov 10 13:28:55 1999] [notice] suEXEC mechanism > > enabled (wrapper: /www/www/apache/bin/suexec) > > panic: restartop > > panic: POPSTACK > > Callback called exit. > > panic: restartop > > panic: POPSTACK > > Callback called exit. > > panic: restartop > > panic: POPSTACK > > Callback called exit. > > panic: restartop > > panic: POPSTACK > > Callback called exit. > > panic: restartop > > panic: POPSTACK > > Callback called exit. > > [Wed Nov 10 13:29:14 1999] [notice] caught SIGTERM, > > shutting down > > > >My software/hardware setup: > > > > IRIX64 akalice 6.5 11051732 IP25 > > mod_perl-1.21 > > apache-1.3.9 > > Apache::SpeedLimit direct from the "Apache Modules" book > > > >My apache configuration: > > > > > > PerlAccessHandler Apache::SpeedLimit > > PerlSetVar SpeedLimit 61 > > PerlSetVar SpeedSamples20 > > PerlSetVar SpeedForgive10 > > > > > >Output from ipcs: > > > > [akalice:www] /_ ipcs -mbcopt > > IPC status from /dev/kmem as of Wed Nov 10 13:42:19 1999 > > T ID KEYMODE OWNERGROUP CREATOR > > CGROUP NATTCH SEGSZ CPID LPID ATIMEDTIMECTIME > > Shared Memory: > > m 0 0x53637444 --rw-r--r-- root root root > > root 1 200382 382 9:40:42 no-entry 9:40:42 > > m140 0x53504c4d --rw-r--r-- www-nobo www-nobo www-nobo > > www-nobo 0 65536 73426277621049 13:29:07 13:29:07 16:13:46 > > > > > > > >Any help on this would be appreciated. > > > >Regards, > >Christian > > > >- > >Christian Gilmore > >Senior Technical Staff Member > >AT&T Labs IP Technology, Florham Park > >[EMAIL PROTECTED] > >http://www.research.att.com/info/cgilmore > > > > > > >
Re: Apache::SpeedLimit and problems with IPC::Shareable
This sounds an awful lot like the problem I ran into when using Apache::Session's tie in an eval'ed context. See this message: http://x31.deja.com/getdoc.xp?AN=536753692&CONTEXT=940379169.1854472193&hitn um=1 and http://www.geocrawler.com/archives/3/182/1999/10/0/2767892/ I assume you're using 5.00503 ? Hope this helps Tobias At 01:56 PM 11/10/99 -0500, Christian Gilmore wrote: >I inserted Apache::SpeedLimit into one of our servers the other day. It works >as advertised, but I'm now seeing errors in the error_log that are coming from >Apache::SpeedLimit/IPC::Shareable. I wonder if anyone else has had this >problem. > >>From the error_log: > > [Wed Nov 10 13:28:55 1999] [notice] Apache/1.3.9 (Unix) > mod_perl/1.21 mod_ssl/2.4.2 OpenSSL/0.9.4 configured > -- resuming normal operations > [Wed Nov 10 13:28:55 1999] [notice] suEXEC mechanism > enabled (wrapper: /www/www/apache/bin/suexec) > panic: restartop > panic: POPSTACK > Callback called exit. > panic: restartop > panic: POPSTACK > Callback called exit. > panic: restartop > panic: POPSTACK > Callback called exit. > panic: restartop > panic: POPSTACK > Callback called exit. > panic: restartop > panic: POPSTACK > Callback called exit. > [Wed Nov 10 13:29:14 1999] [notice] caught SIGTERM, > shutting down > >My software/hardware setup: > > IRIX64 akalice 6.5 11051732 IP25 > mod_perl-1.21 > apache-1.3.9 > Apache::SpeedLimit direct from the "Apache Modules" book > >My apache configuration: > > > PerlAccessHandler Apache::SpeedLimit > PerlSetVar SpeedLimit 61 > PerlSetVar SpeedSamples20 > PerlSetVar SpeedForgive10 > > >Output from ipcs: > > [akalice:www] /_ ipcs -mbcopt > IPC status from /dev/kmem as of Wed Nov 10 13:42:19 1999 > T ID KEYMODE OWNERGROUP CREATOR > CGROUP NATTCH SEGSZ CPID LPID ATIMEDTIMECTIME > Shared Memory: > m 0 0x53637444 --rw-r--r-- root root root > root 1 200382 382 9:40:42 no-entry 9:40:42 > m140 0x53504c4d --rw-r--r-- www-nobo www-nobo www-nobo > www-nobo 0 65536 73426277621049 13:29:07 13:29:07 16:13:46 > > > >Any help on this would be appreciated. > >Regards, >Christian > >- >Christian Gilmore >Senior Technical Staff Member >AT&T Labs IP Technology, Florham Park >[EMAIL PROTECTED] >http://www.research.att.com/info/cgilmore > >
RE: Apache::SpeedLimit and problems with IPC::Shareable
The problem is certainly with how IPC::Shareable deals with memory (re)allocation and not with mod-perl. I'm sorry to have brought it to this list. I'll see if I can't hunt down the creator of IPC::Shareable and work with him on it. Regards, Christian > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Christian Gilmore > Sent: Wednesday, November 10, 1999 1:57 PM > To: ModPerl Mailing List (E-mail) > Subject: Apache::SpeedLimit and problems with IPC::Shareable > > > I inserted Apache::SpeedLimit into one of our servers the > other day. It works > as advertised, but I'm now seeing errors in the error_log > that are coming from > Apache::SpeedLimit/IPC::Shareable. I wonder if anyone else > has had this > problem. > > >From the error_log: > > [Wed Nov 10 13:28:55 1999] [notice] Apache/1.3.9 (Unix) > mod_perl/1.21 mod_ssl/2.4.2 OpenSSL/0.9.4 configured > -- resuming normal operations > [Wed Nov 10 13:28:55 1999] [notice] suEXEC mechanism > enabled (wrapper: /www/www/apache/bin/suexec) > panic: restartop > panic: POPSTACK > Callback called exit. > panic: restartop > panic: POPSTACK > Callback called exit. > panic: restartop > panic: POPSTACK > Callback called exit. > panic: restartop > panic: POPSTACK > Callback called exit. > panic: restartop > panic: POPSTACK > Callback called exit. > [Wed Nov 10 13:29:14 1999] [notice] caught SIGTERM, > shutting down > > My software/hardware setup: > > IRIX64 akalice 6.5 11051732 IP25 > mod_perl-1.21 > apache-1.3.9 > Apache::SpeedLimit direct from the "Apache Modules" book > > My apache configuration: > > > PerlAccessHandler Apache::SpeedLimit > PerlSetVar SpeedLimit 61 > PerlSetVar SpeedSamples20 > PerlSetVar SpeedForgive10 > > > Output from ipcs: > > [akalice:www] /_ ipcs -mbcopt > IPC status from /dev/kmem as of Wed Nov 10 13:42:19 1999 > T ID KEYMODE OWNERGROUP CREATOR > CGROUP NATTCH SEGSZ CPID LPID ATIMEDTIMECTIME > Shared Memory: > m 0 0x53637444 --rw-r--r-- root root root > root 1 200382 382 9:40:42 no-entry 9:40:42 > m140 0x53504c4d --rw-r--r-- www-nobo www-nobo www-nobo > www-nobo 0 65536 73426277621049 13:29:07 13:29:07 16:13:46 > > > > Any help on this would be appreciated. > > Regards, > Christian > > - > Christian Gilmore > Senior Technical Staff Member > AT&T Labs IP Technology, Florham Park > [EMAIL PROTECTED] > http://www.research.att.com/info/cgilmore > >
