On Thu, 2005-07-07 at 10:16 -0500, Jason Czerak wrote:
SOLVED. Stupid weblogic
/tmp/wlproxy.log was up to 2gig. that was killing my processes. I switch
things to only log error's to that file, not everything.
Fixing this indirectly solved a random file upload timeout problem too.
Becaus
On Thu, 2005-07-07 at 16:10 +0100, Joe Orton wrote:
> On Wed, Jul 06, 2005 at 02:58:22PM -0700, Dan Trainor wrote:
> > Jason Czerak wrote:
> > > Wed Jul 06 16:25:18 2005] [notice] child pid 24242 exit signal File size
> > > limit exceeded (25)
> > > [Wed Jul
On Wed, 2005-07-06 at 14:58 -0700, Dan Trainor wrote:
> Jason Czerak wrote:
> > Wed Jul 06 16:25:18 2005] [notice] child pid 24242 exit signal File size
> > limit exceeded (25)
> > [Wed Jul 06 16:27:00 2005] [notice] child pid 24368 exit signal File
> > size limit excee
;/u01/apache2_ia32_worker"
-D SUEXEC_BIN="/u01/apache2_ia32_worker/bin/suexec"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf&q
rror cleans up. Other then this possible solutions, Any ideas?
--
Jason Czerak ([EMAIL PROTECTED])
PPD Medical Device -- New Hope, MN
System Administrator
Desk: 763.489.6128
Cell: 586.405.8366 (Nextel: 130*21*2819)
Pager: 877.448.9280 ([E
--
> From: Jason Czerak [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 20, 2005 10:47 AM
> To: users@httpd.apache.org
> Subject: [EMAIL PROTECTED] Apache 2 - Visit based connection limiting.
>
> What I wish to accomplish is a visit based connection limiting. A visit
> defined a
.
Also, our application experiences some funky stuff in a cluster.
As for hardware, We are ordering more hardware. Correct hardware.
4xAMD64 and 10gig's ram. And something not RedHat. :) In the mean time
I'm looking for a solution to improve site experience.
Any
