Stas:
Since you wrote the script, do you recommend some good default settings in
GTopLimit to start with, i.e.,
use Apache::GTopLimit;
Apache::GTopLimit-set_max_size(1);
Apache::GTopLimit-set_min_shared_size(4000);
Apache::GTopLimit-set_max_unshared_size(6000);
I am trying to install GTop in order to install GTopLimit and am getting
the following error on make:
glob failed (child exited with status 2) at Makefile.PL line 242.
glob failed (child exited with status 2) at Makefile.PL line 242.
Note (probably harmless): No library found for -lgtop
Note
When trying to install GTop, I received the following
Note (probably harmless): No library found for -lgtop
Note (probably harmless): No library found for -lgtop_sysdeps
Note (probably harmless): No library found for -lgtop_common
Note (probably harmless): No library found for -lglib
Can't exec
Thanks Perrin. I've wasted so much time today trying to figure out what
was going on with my glib installation.
I guess your suggestion might be the better solution anyhow as I sure don't
want to run into installation problems for my customers down the road!
I also suppose that this means
Here's an odd question for you. Why is it when I go to places like
cgi-resources.com and other cgi repositories, mod_perl applications are far
and few between...commercially that is?
All I see are common cgi scripts written in plain perl.
Does it have anything to do with the configurability
some enourmous leaks as well, based on circular reference,
and those ate up 1 GB of memory in about 30 minutes... It took us
about three weeks to find it.
Gregory Matthews writes:
So am I being overly paranoid concerning the leak potential of mod_perl
programming?
If I start with strict
Thanks to everyone for the great input on Memory Leaks. Now that I have a
good starting point for tracking down the problem, when I TEST for leaks,
or simply check for a continued increase in server memory usage, how do I
go about monitoring the processes growth?
For example, is there a
, we have a cluster of machines and roll the
restarts every hour. Each machine is offset but 10 minutes.
Gregory Matthews writes:
I too thought of setting a cron job to restart the server once per day in
order to keep the memory fresh.
In a production environment, are there any downsides
Does using the Apache::GTopLimit module have the same net effect as
restarting the server itself by simply killing off the actual processes
which are growing beyond the set threshold, and thereby causing new
processes to be born?
If so, this sounds like a good alternative to setting a cron
So to modify my previous question, other than the loss of some shared
memory over time, GTopLimit will have the same effect as restarting the
server?
On a side note, how are you tracking/discovering the this minimal loss over
time?
Gregory
At 08:38 PM 5/20/2002 -0400, you wrote:
Does
Sorry for being lazy! I will read the guide all the way through...promise!
Thanks though for everyone's help up to this point!
Gregory
At 12:04 PM 5/21/2002 +0800, you wrote:
Gregory Matthews wrote:
Thanks to everyone for the great input on Memory Leaks. Now that I have
a good starting point
the server because of it. Can
this file be read and checked for correctness but not loaded?
Gregory
At 09:57 AM 5/19/2002 +0200, you wrote:
At 02:50 19.05.2002, Gregory Matthews wrote:
Tried that...doesn't work either.
@INC still cannot find my config.pl file. If I add the use lib statement
to my
with the
Apache::DBI-connect_on_init option, and even though I put in bogus
database info, Apache starts fine with no errors?
Any ideas on what is going on?
Gregory
At 09:57 AM 5/19/2002 +0200, you wrote:
At 02:50 19.05.2002, Gregory Matthews wrote:
Tried that...doesn't work either.
@INC still
to find diagnostic messages... (looking in the
normal webserver logs, or the ssl logs, as compared to the mod_perl
daemon's error logs)
On Sun, 19 May 2002, Per Einar Ellefsen wrote:
At 18:57 19.05.2002, Gregory Matthews wrote:
I added the below STDER statement and did NOT see the printout either
to the mod_perl
daemon's error logs)
On Sun, 19 May 2002, Per Einar Ellefsen wrote:
At 18:57 19.05.2002, Gregory Matthews wrote:
I added the below STDER statement and did NOT see the printout either on
screen or in my error_log file.
It sounds like then my startup.pl file is not even
be able to see a reference to the connection in my error_log file?
I checked both my virtual host error_log file and the server error_log
file. Nothing in either.
Gregory
At 10:21 PM 5/19/2002 +0200, you wrote:
At 22:03 19.05.2002, Gregory Matthews wrote:
Tom:
Fixed it. I needed to add a 1
19.05.2002, Gregory Matthews wrote:
Tom:
Here is one of them. I think that I saw it elsewhere also. When I come
across the other pages, I will advise.
http://perl.apache.org/preview/modperl-site-ok/docs/1.0/guide/config.html
Hello again.
Is Apache::Leak the easiest/best module to use for both detecting AND
allowing us to find the source of a memory leak in mod_perl?
If so, I am not finding any good documentation on its use. I am not a
mod_perl guru and what I've read so far sounds rather involved.
Can someone
I have a couple of questions regarding leaking memory in mod_perl:
1. What are the main culprits, in order of severity, of memory leaks, i.e.:
a. global variables (NOT lexically scoped via my)
b. ...
c. ...
2. When writing code from scratch (a new application), what is the best
way to
So am I being overly paranoid concerning the leak potential of mod_perl
programming?
If I start with strict code to begin with and try my best to stay away
from the problems you mentioned, then any potential memory leak/drain
issues will be avoided?
Keep in mind, although my application is
Hello again:
I figured out my Apache::DB problem with the help from Stas Bekman. Thanks!
Now on to Apache::DBI.
The documentation says NOT to use this module IF you are opening a special
connection for each of your users.
Does this mean if each user has to use a unique username/password to
At 01:30 AM 5/18/2002 +0800, you wrote:
[please don't forget that to CC the list!]
Gregory Matthews wrote:
Stas:
Thanks for your reply on my issue in the Mod_Perl list.
Excuse my ignorance, but how do I do the following:
before you try to build Apache::DB try to build test.c with the contents
Perrin:
Yes, my prog checks for valid username/password requests and issues the
proper response. So it sounds like Apache::DBI is a good solution then
since all users will be working under the same handle?
Gregory
At 02:03 PM 5/18/2002 -0400, you wrote:
Gregory Matthews wrote:
Does this mean
I am getting the following repeating code in my error log in doing some
testing on my script:
DB1 DB1 DB1 DB1 DB1 DB1 DB1 DB1
Does anyone know what this means? It seems to go away when I restart apache.
Gregory
I am trying to:
use lib qw(/dir/foo);
in my startup.pl file but INC is NOT showing the path. I keep getting
Can't locate config.pl in INC errors after restarting the server and
calling the script.
My prog reads:
require qq(config.pl);
I am not sure what is going on. INC shows:
(INC
Stas:
Thanks again!
Gregory
At 01:30 AM 5/18/2002 +0800, you wrote:
[please don't forget that to CC the list!]
Gregory Matthews wrote:
Stas:
Thanks for your reply on my issue in the Mod_Perl list.
Excuse my ignorance, but how do I do the following:
before you try to build Apache::DB try
(path to files);
That adds the path to @INC. Someone correct me if that's the wrong way to do
things
- Original Message -
From: Gregory Matthews [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, May 18, 2002 6:12 PM
Subject: Modifying @INC via startup.pl
I am trying to:
use
Hello All.
I am trying to install Apache::DB and am getting the following error:
+
make test
cc -c-DVERSION=\0.06\ -DXS_VERSION=\0.06\ -DPIC -fpic
-I/usr/libdata/perl/5.00503/mach/CORE DB.c
In file included from /usr/include/sys/time.h:289,
from
28 matches
Mail list logo
