Thanks but I can't get the configuration to work right. I am now using
EmbPerlChain. What should my PerlHandler line in httpd.conf say?
I didn't have used EmbperlChain on my own so far, but if you search the
modperl mailing list archives (http://forum.swarthmore.edu/epigone/modperl)
, you
Hi,
if I set optEarlyHttpHeader (64) within my EMBPERL_OPTIONS my
page ist correctly shown in the browser. But if
optEarlyHttpHeader is not set, the contents of my page are mixed
up. I use several blocks of [- -] and [* *] and I execute two
Shellscripts using perls backtick-syntax (unfortunately
Hi,
if I set optEarlyHttpHeader (64) within my EMBPERL_OPTIONS my
page ist correctly shown in the browser. But if
optEarlyHttpHeader is not set, the contents of my page are mixed
up. I use several blocks of [- -] and [* *] and I execute two
Shellscripts using perls backtick-syntax
On Tue, 18 Jan 2000, Stas Bekman wrote:
I'm still confused... which is the right scenario:
1) a mod_perl process generates a response of 64k, if the
ProxyReceiveBufferSize is 64k, the process gets released immediately, as
all 64k are buffered at the socket, then a proxy process comes in,
Can someone please explain why Apache does all the dlclosing and
dlopening of shared files on startup and a restart? I can think of no
reson why this would ever be necessary - why on earth is it done?
Alan Burlison
On Tue, Jan 18, 2000 at 12:59:13PM +, Alan Burlison wrote:
Can someone please explain why Apache does all the dlclosing and
dlopening of shared files on startup and a restart? I can think of no
reson why this would ever be necessary - why on earth is it done?
Alan Burlison
Probably
Can someone please explain why Apache does all the dlclosing and
dlopening of shared files on startup and a restart? I can think of no
reson why this would ever be necessary - why on earth is it done?
I don't know, but I know for sure that causes a lot of trouble with mod_perl
and Perl
Probably the biggest reason for dlopen/dlclose on a restart is that the
list of modules in the config file can change on a restart. The reason
for the reload on startup has something to do with parsing the config
file in the parent and child; it was never adequately explained to me.
The
We are using Embperl 1.2, Apache Session 1.3 (using
DBIStore/SysVSemaphoreLocker) with Oracle as the backend.
We've been observing periodic browser hangs which can be sporadically
replicated by hitting the same page in quick succession using the same
session id. After doing that, updating
Okay. I'm poor programmer. I'm dumb. OKAY, I'M AN IDIOT. I agree.
But now, PLEASE, point me WHY Apache::Session does NEVER get destroyed
it the sample handler.
Have I told you that I'm poor programmer, don't know Perl at all and
overall dumb and cannot even type?
JUST POINT ME TO MY ERROR!
On Tue, Jan 18, 2000 at 02:40:59PM +0100, Gerald Richter wrote:
Probably the biggest reason for dlopen/dlclose on a restart is that the
list of modules in the config file can change on a restart. The reason
for the reload on startup has something to do with parsing the config
file in the
[EMAIL PROTECTED] wrote:
Okay. I'm poor programmer. I'm dumb. OKAY, I'M AN IDIOT. I agree.
But now, PLEASE, point me WHY Apache::Session does NEVER get destroyed
it the sample handler.
Have I told you that I'm poor programmer, don't know Perl at all and
overall dumb and cannot even
I'll start this off with the error message I've been getting:
Undefined subroutine Apache::perl_hook called at
/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/mod_perl.pm line 28.
I have installed the Apache bundle (as well as several dozen other Apache
modules). This error is occuring in
We are using Embperl 1.2, Apache Session 1.3 (using
DBIStore/SysVSemaphoreLocker) with Oracle as the backend.
We've been observing periodic browser hangs which can be sporadically
replicated by hitting the same page in quick succession using the same
session id. After doing that, updating
I'll start this off with the error message I've been getting:
Undefined subroutine Apache::perl_hook called at
/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/mod_perl.pm line 28.
I have installed the Apache bundle (as well as several dozen other Apache
modules). This error is occuring
That is what my patch did. And that was the explanation I posted of
the problem last week when we were debugging it.
Sorry, I missed that thread. I have posted this problem more then once here,
because it have beaten me and other often when using Embperl. The problem
there is often more
I looked at mod_proxy and found the pass thru buffer size
is IOBUFSIZ, it reads that from the remote server then
writes to the client, in a loop.
Squid has 16K.
Neither is enough.
In an effort to get those mod_perl daemons to free up for long
requests, it is possible to patch mod_proxy to read as
Vivek Khera [EMAIL PROTECTED] writes:
This has infinite more flexibility than squid, and allows me to have
multiple personalities to my sites. See for example the sites
http://www.morebuiness.com and http://govcon.morebusiness.com
If when you say "multiple personalities", you mean virtual
On 17 Jan 2000, Michael Alan Dorman wrote:
Vivek Khera [EMAIL PROTECTED] writes:
This has infinite more flexibility than squid, and allows me to have
multiple personalities to my sites. See for example the sites
http://www.morebuiness.com and http://govcon.morebusiness.com
If when you
On Tue, Jan 18, 2000 at 08:26:17PM +0100, Gerald Richter wrote:
Also I didn't tried it yet, your patch makes much sense too me. I will try
it out as soon as I get a litle free time. The next step is to port it NT,
because there isn't a dlopen/dlclose (of course there is one, but with a
Todd Finney wrote:
At 12:26 PM 1/17/00 , Gerd Kortemeyer wrote:
Clay wrote:
so i am just wanting to know what anyone
has found out on mod perl not working properly
under redhat 6.1?
If you install everything (including modperl) from RedHat's RPMs, no
problem (I
did this on five
Vivek Khera wrote:
AB To summarise: Apache dlclose's the mod_perl.so, which then results in
AB the perl libperl.so being unloaded as well (there's a linker dependency
Excellent summary... thanks!
AB from mod_perl - perl libperl.so). Unfortunately the perl XS modules
AB loaded in
On Tue, Jan 18, 2000 at 08:03:42PM +, Alan Burlison wrote:
The current fix is to forcibly unload the perl XS modules during the
unload. However, on reflection I'm not at all sure this is the correct
thing to do. Although you can unload the .so component of a perl
module, you can't
Well, I've got a performance question
We all know that mod_perl is quite hungry for memory, but when you have
lots of SQL requests, the sql engine (mysql in my case) and httpd are
competing for memory (also I/O and CPU of course). The simplest solution
is to bump in a stronger server until it
"SB" == Stas Bekman [EMAIL PROTECTED] writes:
SB replacing with new expensive machine. The question is what are the
SB immediate implications on performace (speed)? Since the 2 machines has to
SB interact between them. e.g. when setting the mysql to run on one machine
SB and leaving
Stas Bekman wrote:
Well, I've got a performance question
We all know that mod_perl is quite hungry for memory, but when you have
lots of SQL requests, the sql engine (mysql in my case) and httpd are
competing for memory (also I/O and CPU of course). The simplest solution
is to bump in a
SB replacing with new expensive machine. The question is what are the
SB immediate implications on performace (speed)? Since the 2 machines has to
SB interact between them. e.g. when setting the mysql to run on one machine
SB and leaving mod_perl/apache/squid on the other. Anyone did that?
To summarise:...
Thanks for the summary, but I already know this problem for a long time and
I am very happy that somebody has taken the time track this down and provide
a solution :-)
However, other folks have reported the exact same problem on other OSs,
eg Linux BSD, so I think that in
"SB" == Stas Bekman [EMAIL PROTECTED] writes:
SB Throwing away the cheap box and putting two expensive instead is even
SB better :) Of course you are right about long-term planning, I was talking
SB about the case when you don't have to buy the cheap box, since we have it
SB already...
Then
Daniel Jacobowitz wrote:
On Tue, Jan 18, 2000 at 08:03:42PM +, Alan Burlison wrote:
The current fix is to forcibly unload the perl XS modules during the
unload. However, on reflection I'm not at all sure this is the correct
thing to do. Although you can unload the .so component of
Gerald Richter wrote:
That's the same on NT. It seems to occur on all OSs, so it won't help
anything to make the linker responsible, there are to much linkers... and I
am not sure if the linker can know under all circumstances which libraries
to unload.
Yes it can. Its main job is to keep
Ok, thanks for the asnwers
Seems like a great addon for the guide's performance chapter.
Just to ride on this thread and to make the the section complete, what are
the suggested HW requirements for a machine running a general SQL vs
machine doing pure I/O and CPU (httpd/mod_perl). Let me try:
According to Stas Bekman:
We all know that mod_perl is quite hungry for memory, but when you have
lots of SQL requests, the sql engine (mysql in my case) and httpd are
competing for memory (also I/O and CPU of course). The simplest solution
is to bump in a stronger server until it gets
Yes it can.
No it can't :-)
Its main job is to keep track and control the dependencies
between libraries. It's just that sometimes thy don't do a particularly
good job of it ;-)
This works only if this dependencies are know at link time, but look at the
source of Dynloader. You can
On Tue, Jan 18, 2000 at 10:19:04PM +0100, Gerald Richter wrote:
Yes it can.
No it can't :-)
Its main job is to keep track and control the dependencies
between libraries. It's just that sometimes thy don't do a particularly
good job of it ;-)
This works only if this
You're confusing the dynamic and static linkers. The dynamic linker is
what he was referring to; it knows what libraries it resolves symbols
to.
Yes, I know this difference and you will be right in most cases, but the
address that is returned, could be passed around to other libraries and
On Tue, Jan 18, 2000 at 10:43:09PM +0100, Gerald Richter wrote:
You're confusing the dynamic and static linkers. The dynamic linker is
what he was referring to; it knows what libraries it resolves symbols
to.
Yes, I know this difference and you will be right in most cases, but the
Gerald Richter wrote:
This works only if this dependencies are know at link time, but look at the
source of Dynloader. You can retrieve address of any (public)symbol inside a
library dynamicly at runtime. Now you have the entry address and can pass it
around. No linker will ever have a
Hi there,
I compiled everything from source, no rpms. It went together without a
hitch. Are people having problems with 6.1?
[EMAIL PROTECTED] was having problems earlier as well.
I didn't see anyone reply to him yet.
73,
Ged.
Hmmm :-(
On 14 Jan 2000, Frank D. Cringle wrote:
Without having checked your list, I'll wager that the "good" modules
are all pure perl and the "bad" ones use machine-language XS
extensions.
So typical modules like MD5 and MIME::Body are "bad" modules?
Ricardo
On Mon, 17 Jan 2000, Todd Finney wrote:
[...]
I compiled everything from source, no rpms. It went together without a
hitch. Are people having problems with 6.1?
I use RedHat 6.1 on my workstation and my notebook and a few production
boxes without any problems. No DSO though.
- ask
--
Cliff Rayman wrote:
i don't think he is saying that the module is "bad",
he is saying that modules that use XS, with apache
mod_perl have caused problems with startup and restarts.
based on the running posts regarding
dlopen and dlclose, i'd say he was correct.
cliff rayman
genwax.com
Alan Burlison wrote:
AB from mod_perl - perl libperl.so). Unfortunately the perl XS modules
AB loaded in during startup via dlopen are *not* unloaded, nor do they
AB succeed in locking the perl libperl.so into memory (you could construe
AB this as a linker bug). Then Apache reloads the
Stas:
One other thing you might want to mention in your thread: the use of
Apache::DBI to maintain persistent connections to the DB can cause a
problem if you have multiple modperl servers all talking to the same DB
server.
For instance, on our site, we have 2 hosts running modperl, each of
Actually, I retract that statement. It is *not* a linker bug. By
explicitly adding a dependency between the XS .so modules and the perl
libperl.so, the problem can be made to dissapear, as ld.so then knows
that there is a dependency between the XS module and the perl libperl.so
I think
Hi,
I have tested the patch to unload all XS libraries, when libperl is
unloaded, Daniel sended a few days ago on Unix and on NT and it works!
Really great!!
Here is a sligthly modified version, so it works also on NT (and on others
OS's). It uses the Apache function ap_os_dso_unload instead of
On Mon, 17 Jan 2000, you wrote:
Why do you need this intermediate step i.e.
A
HREF="/login/indxnav1.epl?session_id=[+$session_ID+]digest=[+$digest+]"
TARGET="index"Update..
?
Why not just get the server to populate frame index with required data
up front ? Or have I missed something
At 21:17 -0800 00.1.18, Scott Chapman wrote:
On Mon, 17 Jan 2000, you wrote:
Why do you need this intermediate step i.e.
A
HREF="/login/indxnav1.epl?session_id=[+$session_ID+]digest=[+$digest+]"
TARGET="index"Update..
?
Why not just get the server to populate frame index with
Here's the situation:
The user loads this page with the two frames. The left frame is the
navigation frame. The user clicks on the left frame the link to log in.
The right frame changes to the login screen and they login. When
they are done, I want the server to populate the frame
On Thu, 4 Nov 1999, Andrei A. Voropaev wrote:
Hi!
For some reason I get lots of
'Attempt to free unreferenced scalar during global destruction.'
in my error log. Any one can give me a pointer where to search for the
problem?
it's most likely due to a buggy xs module. that message
On Wed, 22 Dec 1999, Clinton Gormley wrote:
I am using a home-baked session manager on my web site. I clean up
expired sessions by called a child exit handlder and this all worked
rather well.
However, we have recompiled Perl, Apache, mod_perl and Perl modules with
pgcc and a different
On Thu, 23 Dec 1999, Li,Yuan N.(NXI) wrote:
I have fought hard quite a few days trying to add mod_perl1.21 onto apache
1.3.9 on HP 11. I use the c compiler comes with the machine, and installed
Perl 5.00503 under my home directory /home/c015932/opt/perl(I do not have
access to the root),
Hi,
While documenting the 'restart twice on start' apache's behavior, I've
tested $Apache::Server::ReStarting and $Apache::Server::Starting.
Perl section is executed twice -- OK.
startup.pl is executed once -- OK.
$Apache::Server::ReStarting never gets set! - I suppose it's a
On Fri, 7 Jan 2000, Martin Lichtin wrote:
Hi,
I'm using send_fd() to send relatively large files. Apache's Timeout is
currently set to 60s and indeed, mod_perl aborts as soon as the minute
elapses. (error msg: mod_perl: Apache-print timed out).
However, it shouldn't do that, right?
On Sun, 9 Jan 2000 [EMAIL PROTECTED] wrote:
"Eric" == Eric writes:
Eric On Sun, Jan 09, 2000 at 08:47:04PM +0300, [EMAIL PROTECTED] wrote:
I'm trying to configure httpd.conf using Perl sections (mod_macro is
not enough for me), but the result is weird.
Eric Do you have a specific
On Tue, 11 Jan 2000, Jim Winstead wrote:
There appears to be a file upload bug in libapreq that causes httpd
processes to spin out of control. There's a mention of this in the
mailing list archives with a patch that seems to be a partial
solution, but we're still seeing problems even with
looks good, thanks David!
On Tue, 11 Jan 2000, David D. Kilzer wrote:
Hi,
The patch below fixes a problem in Apache::RedirectFixLog when the URI
being logged required use of a filename listed the DirectoryIndex
directive.
The solution is described in the following post by Doug
On Thu, 13 Jan 2000, Bill Moseley wrote:
At 08:50 AM 1/13/00 +0200, you wrote:
Does anyone have experience using an alarm() call under Apache::Registry?
http://perl.apache.org/guide/debug.html#Handling_the_server_timeout_case
Should I set alarm(0) as my script "exits" or is it ok to
thanks Charles, I think your patch is the way to go for now, or something
close to it for 1.22
On Thu, 13 Jan 2000, Charles Levert wrote:
Hi.
[ I use Apache 1.3.9 and mod_perl 1.21. ]
I believe that there is a difference between the following two
behaviors for an Apache module handler:
On Fri, 14 Jan 2000, Jason Bodnar wrote:
A line in the proxy example of the eagle book on page 380 does not seem to work
(entirely):
The line:
$r-headers_in-do(sub {$request-header(@_);});
what if you change that to:
$r-headers_in-do(sub {$request-header(@_); 1});
?
On Fri, 14 Jan 2000, Cere M. Davis wrote:
I have found the weirdest problem with (I think) DBD::Ingres,
DBI::trace() and Apache::DBI when the DBI::trace level is set to 1 or 0.
I get an error in the Apache error_logs that says:
unitialized value at
On Wed, 19 Jan 2000, Stas Bekman wrote:
Why? Some users need a control of what gets reloaded and what not on
server start (Yes I know if you put in startup.pl file it loads only once)
For example parsing and loading some heavy xml files...
Why do you want to take it away?
I think
62 matches
Mail list logo
