On 23/04/13 22:48, Ryan Perry wrote:
> except I use a threaded MPM so I can't use child_terminate. Is there
> another method similar to that?
yes, use prefork, ;-)
Sorry, couldn't resist.
Torsten
except I use a threaded MPM so I can't use child_terminate. Is there
another method similar to that?
On Tue, Apr 23, 2013 at 3:42 PM, Torsten Förtsch
wrote:
> On 23/04/13 17:49, Ryan Perry wrote:
> > I've been plagued by some bug that makes a call to LWP stop working:
> > "Can't connect to 192.
On 23/04/13 17:49, Ryan Perry wrote:
> I've been plagued by some bug that makes a call to LWP stop working:
> "Can't connect to 192.168.0.222 (Bad hostname)"
If you can catch the error when it occurs, you can call
$r->child_terminate to terminate the process after the current request.
The parent a
hostname)"
I haven't been able to figure out
why, but a
simple httpd
restart fixes
it for a day or 2.
Since I can'
MONIT – wouldn’t go a day wthout it ;-)
Joe N
From: Ryan Perry
Sent: Tuesday, April 23, 2013 3:27 PM
To: modperl@perl.apache.org
Subject: Re: automatically restart httpd
On Tue, Apr 23, 2013 at 2:09 PM, Jim Albert wrote:
On 4/23/2013 2:33 PM, Ryan Perry wrote:
On Tue, Apr 23
stop working:
>> "Can't connect to 192.168.0.222 (Bad hostname)"
>>
>> I haven't been able to figure out why, but a
>> simple httpd
>> restart fixes
>>
t figure out a real fix, I'm
wondering if
there is a
way for
me to automatically restart httpd whenever
the bug
hits. Maybe
whenever
it appears in the htt
ering if
there is a
way for
me to automatically restart httpd whenever the bug
hits. Maybe
whenever
it appears in the httpd-error.log? W
;> stop working:
>> "Can't connect to 192.168.0.222 (Bad hostname)"
>>
>> I haven't been able to figure out why, but a simple httpd
>> restart fixes
>> it for a day or 2.
>>
>>
Since I can't figure out a real fix, I'm wondering if
there is a
way for
me to automatically restart httpd whenever the bug
hits. Maybe
whenever
it appears in the httpd-error.log? What are my option
;t figure out a real fix, I'm wondering if there is a
way for
me to automatically restart httpd whenever the bug hits. Maybe
whenever
it appears in the httpd-error.log? What are my options?
Without more to go on to the actual cause of the problem...
stop working:
>> "Can't connect to 192.168.0.222 (Bad hostname)"
>>
>> I haven't been able to figure out why, but a simple httpd restart fixes
>> it for a day or 2.
>>
>> Since I can't figure out a real fix, I'm wondering if th
7;t figure out a real fix, I'm wondering if there is a way for
me to automatically restart httpd whenever the bug hits. Maybe whenever
it appears in the httpd-error.log? What are my options?
Without more to go on to the actual cause of the problem...
Restarting apache daily isn't a bad
ndering if there is a way for me
to automatically restart httpd whenever the bug hits. Maybe whenever it
appears in the httpd-error.log? What are my options?
--
*Ryan Perry*
Technology Director
RestoreHealth
1289 Deming Way
Madison, WI 53717
608.833.7046 ext 700
rpe...@restorehc.com
14 matches
Mail list logo
