Re: Process exiting prematurely
On Wed, 3 Sep 2003, Stas Bekman wrote: > Flowers, Jay wrote: > > > > Do you get this behavior with some particular script or > > just any kind? Does the same script work fine as > > mod_cgi? > > > > All scripts, work the same. They work fine under mod_cgi. > > Do normal handlers behave the same way? i.e. if you don't > use registry but a complete handler: > http://perl.apache.org/docs/2.0/user/intro/start_fast.html#Handler_Modules > > If the problem persists, make sure to submit a complete > problem report here and may be someone on Windows XP will > be able to help you. For more info see: > http://perl.apache.org/bugs/ Seeing if normal handlers work would be a very good check. And giving the information described at http://perl.apache.org/bugs/ would also help. I might also suggest checking that the mod_perl version you have corresponds to the Apache version it was compiled against (if you used the most recent ppm, this would be against Apache 2.0.47) - if in doubt, try resinstalling it, and make sure the mod_perl.so is copied to your Apache2 modules/ directory. You might also try putting in a directive LoadFile "/Path/to/Perl/bin/perl58.dll" before loading mod_perl.so. -- best regards, randy kobes -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
Re: Process exiting prematurely
Flowers, Jay wrote: Do you get this behavior with some particular script or just any kind? Does the same script work fine as mod_cgi? All scripts, work the same. They work fine under mod_cgi. Do normal handlers behave the same way? i.e. if you don't use registry but a complete handler: http://perl.apache.org/docs/2.0/user/intro/start_fast.html#Handler_Modules If the problem persists, make sure to submit a complete problem report here and may be someone on Windows XP will be able to help you. For more info see: http://perl.apache.org/bugs/ __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
RE: Process exiting prematurely
Title: Re: Process exiting prematurely Do you get this behavior with some particular script or just any kind? Doesthe same script work fine as mod_cgi?All scripts, work the same. They work fine under mod_cgi.
Re: Process exiting prematurely
Flowers, Jay wrote: That is the bugger of it, there is no error, it's a behavior that I noticed. Every request is slow because it needs to restart the Apache Child process. It feels much slower than CGI on IIS. Do you get this behavior with some particular script or just any kind? Does the same script work fine as mod_cgi? __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
RE: Process exiting prematurely
> Possibly change the MaxRequestsPerChild to 100 and see if it still restarts? > Roger no joy. Thanks Jay Flowers Systems Engineer Integic Corp.
RE: Process exiting prematurely
Possibly change the MaxRequestsPerChild to 100 and see if it still restarts? Roger On Wed, 2003-09-03 at 13:17, Flowers, Jay wrote: > Jay, I can't see from your error_log what problem you are talking about. > Apache always starts and immediately restarts, so what you see is normal. It does not work this way on my Windows 2000 server machines. After every request it restarts the Apache Child Process, even though the config file has MaxRequestsPerChild set to 0. > What shows up in the error_log when you issue a request to a registry > script? Just what I showed, the log would just be a repetition of the restart for each request. > I suppose nothing? There is no segfault, no nothing? What's the exact > error message that you get from the system? (I suppose it does that via a > pop up window, right?) That is the bugger of it, there is no error, it's a behavior that I noticed. Every request is slow because it needs to restart the Apache Child process. It feels much slower than CGI on IIS.
RE: Process exiting prematurely
> Jay, I can't see from your error_log what problem you are talking about. > Apache always starts and immediately restarts, so what you see is normal. It does not work this way on my Windows 2000 server machines. After every request it restarts the Apache Child Process, even though the config file has MaxRequestsPerChild set to 0. > What shows up in the error_log when you issue a request to a registry > script? Just what I showed, the log would just be a repetition of the restart for each request. > I suppose nothing? There is no segfault, no nothing? What's the exact > error message that you get from the system? (I suppose it does that via a > pop up window, right?) That is the bugger of it, there is no error, it's a behavior that I noticed. Every request is slow because it needs to restart the Apache Child process. It feels much slower than CGI on IIS. -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
Re: Process exiting prematurely
Flowers, Jay wrote: I am running Windows XP, Apache 2.0.46, mod_perl 1.99, and Perl 5.8. Every request to my Perl script causes the Apache child process to exit. I have not been able to identify the issue. Below I have listed my config file (the number of threads per child is limited to ten for brevity of the log file) and the error log (this includes startup of the server and one request). Jay, I can't see from your error_log what problem you are talking about. Apache always starts and immediately restarts, so what you see is normal. What shows up in the error_log when you issue a request to a registry script? I suppose nothing? There is no segfault, no nothing? What's the exact error message that you get from the system? (I suppose it does that via a pop up window, right?) __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
Process exiting prematurely
I am running Windows XP, Apache 2.0.46, mod_perl 1.99, and Perl 5.8. Every request to my Perl script causes the Apache child process to exit. I have not been able to identify the issue. Below I have listed my config file (the number of threads per child is limited to ten for brevity of the log file) and the error log (this includes startup of the server and one request). # # Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See http://httpd.apache.org/docs-2.0/> for detailed information about # the directives. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/foo.log" # with ServerRoot set to "C:/Apache_Group/Apache2" will be interpreted by the # server as "C:/Apache_Group/Apache2/logs/foo.log". # # NOTE: Where filenames are specified, you must use forward slashes # instead of backslashes (e.g., "c:/apache" instead of "c:\apache"). # If a drive letter is omitted, the drive on which Apache.exe is located # will be used by default. It is recommended that you always supply # an explicit drive letter in absolute paths, however, to avoid # confusion. # ### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation (available # at http://httpd.apache.org/docs-2.0/mod/mpm_common.html#lockfile>); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # ServerRoot "C:/Apache_Group/Apache2" # # ScoreBoardFile: File used to store internal server process information. # If unspecified (the default), the scoreboard will be stored in an # anonymous shared memory segment, and will be unavailable to third-party # applications. # If specified, ensure that no two invocations of Apache share the same # scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK. # #ScoreBoardFile logs/apache_runtime_status # # PidFile: The file in which the server should record its process # identification number when it starts. # PidFile logs/httpd.pid # # Timeout: The number of seconds before receives and sends time out. # Timeout 300 # # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to "Off" to deactivate. # KeepAlive On # # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. # MaxKeepAliveRequests 100 # # KeepAliveTimeout: Number of seconds to wait for the next request from the # same client on the same connection. # KeepAliveTimeout 15 ## ## Server-Pool Size Regulation (MPM specific) ## # WinNT MPM # ThreadsPerChild: constant number of worker threads in the server process # MaxRequestsPerChild: maximum number of requests a server process serves ThreadsPerChild 10 MaxRequestsPerChild 0 # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses (0.0.0.0) # #Listen 12.34.56.78:80 Listen 80 # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled m