You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Stas Bekman <st...@stason.org> on 2004/11/27 21:57:39 UTC
mod_proxy debug warnings
I know those are debug level warnings, but are those really needed?
I get 34 of these identical lines every time the module is initialized:
[Sat Nov 27 15:37:42 2004] [debug] proxy_util.c(1444): proxy: initialized
worker 0 for (rabbit.stason.org:8529) min=0 max=2 smax=2
why so many identical traces? Can we possibly get rid of this noise?
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_proxy debug warnings
Posted by Stas Bekman <st...@stason.org>.
Mladen Turk wrote:
> Stas Bekman wrote:
>
>> So it's not possible that the number of logs relates to the number of
>> child_init calls. Though I do have 32 vhosts, which matches much
>> better the number of debug lines (33). So does it print one per vhost?
>>
>
> Yes, they are duplicated for each virtual host and that is wrong
> behavior. They should be initialized only once.
>
> I'll fix that.
That's better :) Thanks Mladen!
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_proxy debug warnings
Posted by Mladen Turk <mt...@apache.org>.
Stas Bekman wrote:
> So it's not possible that the number of logs relates to the number of
> child_init calls. Though I do have 32 vhosts, which matches much better
> the number of debug lines (33). So does it print one per vhost?
>
Yes, they are duplicated for each virtual host and that is wrong
behavior. They should be initialized only once.
I'll fix that.
--
Mladen.
Re: mod_proxy debug warnings
Posted by Stas Bekman <st...@stason.org>.
Jeff Trawick wrote:
> On Sun, 28 Nov 2004 13:54:02 -0500, Stas Bekman <st...@stason.org> wrote:
>
>>Mladen Turk wrote:
>>
>>>Stas Bekman wrote:
>>>
>>>
>>>>I know those are debug level warnings, but are those really needed?
>>>>
>>>>I get 34 of these identical lines every time the module is initialized:
>>>>
>>>>[Sat Nov 27 15:37:42 2004] [debug] proxy_util.c(1444): proxy:
>>>>initialized worker 0 for (rabbit.stason.org:8529) min=0 max=2 smax=2
>>>>
>>>>why so many identical traces? Can we possibly get rid of this noise?
>>>>
>>>
>>>Probably adding getpid() would give more sense to that log line.
>>
>>That's a good idea, but the amount of output doesn't make much sense to
>>me, since I start only 2 procs (prefork). why do I get 34 reports then?
>>I'd expect 2 lines, no?
>
>
> messages in a child init hook will spew any time a new child process
> is created, whether at initialization (starting enough child processes
> to reach the StartServers limit), or later on during steady state
> (adding processes as load increases or replacing processes which
> exited due to MaxRequestsPerChild)
Doesn't look like the case, I've just rebuilt worker and the config is:
<IfModule worker.c>
StartServers 1
MinSpareThreads 2
MaxSpareThreads 2
ThreadsPerChild 2
MaxClients 4
MaxRequestsPerChild 0
</IfModule>
So it's not possible that the number of logs relates to the number of
child_init calls. Though I do have 32 vhosts, which matches much better
the number of debug lines (33). So does it print one per vhost?
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_proxy debug warnings
Posted by Jeff Trawick <tr...@gmail.com>.
On Sun, 28 Nov 2004 13:54:02 -0500, Stas Bekman <st...@stason.org> wrote:
> Mladen Turk wrote:
> > Stas Bekman wrote:
> >
> >> I know those are debug level warnings, but are those really needed?
> >>
> >> I get 34 of these identical lines every time the module is initialized:
> >>
> >> [Sat Nov 27 15:37:42 2004] [debug] proxy_util.c(1444): proxy:
> >> initialized worker 0 for (rabbit.stason.org:8529) min=0 max=2 smax=2
> >>
> >> why so many identical traces? Can we possibly get rid of this noise?
> >>
> >
> > Probably adding getpid() would give more sense to that log line.
>
> That's a good idea, but the amount of output doesn't make much sense to
> me, since I start only 2 procs (prefork). why do I get 34 reports then?
> I'd expect 2 lines, no?
messages in a child init hook will spew any time a new child process
is created, whether at initialization (starting enough child processes
to reach the StartServers limit), or later on during steady state
(adding processes as load increases or replacing processes which
exited due to MaxRequestsPerChild)
Re: mod_proxy debug warnings
Posted by Stas Bekman <st...@stason.org>.
Mladen Turk wrote:
> Stas Bekman wrote:
>
>> I know those are debug level warnings, but are those really needed?
>>
>> I get 34 of these identical lines every time the module is initialized:
>>
>> [Sat Nov 27 15:37:42 2004] [debug] proxy_util.c(1444): proxy:
>> initialized worker 0 for (rabbit.stason.org:8529) min=0 max=2 smax=2
>>
>> why so many identical traces? Can we possibly get rid of this noise?
>>
>
> Probably adding getpid() would give more sense to that log line.
That's a good idea, but the amount of output doesn't make much sense to
me, since I start only 2 procs (prefork). why do I get 34 reports then?
I'd expect 2 lines, no?
> Also it has it's purpose cause those logged numbers for max
> and smax can be different then the one you've put in the config,
> and are depending on mpm and AP_MPMQ_MAX_THREADS.
(I'm talking about prefork, no threads in this particular case)
> We can log that only in child_init, cause on post_conf we don't
> have a scoreboard yet.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_proxy debug warnings
Posted by Mladen Turk <mt...@apache.org>.
Stas Bekman wrote:
> I know those are debug level warnings, but are those really needed?
>
> I get 34 of these identical lines every time the module is initialized:
>
> [Sat Nov 27 15:37:42 2004] [debug] proxy_util.c(1444): proxy:
> initialized worker 0 for (rabbit.stason.org:8529) min=0 max=2 smax=2
>
> why so many identical traces? Can we possibly get rid of this noise?
>
Probably adding getpid() would give more sense to that log line.
Also it has it's purpose cause those logged numbers for max
and smax can be different then the one you've put in the config,
and are depending on mpm and AP_MPMQ_MAX_THREADS.
We can log that only in child_init, cause on post_conf we don't
have a scoreboard yet.
Regards,
Mladen.