Re: unexpected Apache::VMonitor output

2005-01-28 Thread Stas Bekman
Todd Finney wrote: At 09:53 PM 1/28/2005 -0500, Stas Bekman wrote: I don't think it'll make any difference. Are you brave enough to delve into the C code? I think the scoreboard module misses some check for the validity of the record, that mod_status does have. So I'd go for mod_status.c, check

Re: unexpected Apache::VMonitor output

2005-01-28 Thread Stas Bekman
Todd Finney wrote: At 09:18 PM 1/28/2005 -0500, Stas Bekman wrote: Todd Finney wrote: Can you give this a try? Yup, it works perfectly fine for me. Only httpd procs are printed and they all exist. Would it be worthwhile for you to run that little script against my server's scoreboard? I can op

Re: unexpected Apache::VMonitor output

2005-01-28 Thread Stas Bekman
Stas Bekman wrote: [...] For now the following simply disables vhosts for Apache::DummyScoreboard (which is the one used when modperl is not loaded). Index: Scoreboard.xs === --- Scoreboard.xs (revision 127) +++ Scoreboard.xs

Re: unexpected Apache::VMonitor output

2005-01-28 Thread Stas Bekman
Stas Bekman wrote: I'm not sure if it's related, but this: -- #!/usr/bin/perl -w use strict; $|++; use Apache::Scoreboard; my $image=Apache::Scoreboard->fetch("[a scoreboard url]"); for (my $parent = $image->parent; $parent; $parent = $parent->next) { my

Re: unexpected Apache::VMonitor output

2005-01-28 Thread Stas Bekman
Todd Finney wrote: At 08:37 PM 1/21/2005 -0500, Stas Bekman wrote: Todd Finney wrote: Unlikely. The errant processes all seem to be daemontools programs like supervise and svcscanboot. Those processes are started long before apache starts, and they exist until after it goes away. Understood. I

Re: unexpected Apache::VMonitor output

2005-01-21 Thread Stas Bekman
Todd Finney wrote: At 08:37 PM 1/21/2005 -0500, Stas Bekman wrote: Todd Finney wrote: Unlikely. The errant processes all seem to be daemontools programs like supervise and svcscanboot. Those processes are started long before apache starts, and they exist until after it goes away. Understood. I

Re: unexpected Apache::VMonitor output

2005-01-21 Thread Stas Bekman
Todd Finney wrote: At 05:30 PM 1/21/2005 -0500, Stas Bekman wrote: Any chance you could compare the logic of mod_status and Apache::VMonitor and see why there is a difference? Let me get my stick and turn off the lights. I'd suspect that what you see is some process IDs that used to be use by Ap

Re: unexpected Apache::VMonitor output

2005-01-21 Thread Stas Bekman
Todd Finney wrote: [...] Allow me to rephrase the question. Looking at contemporaneous VMonitor and ExtendedStatus reports (below), I don't know where to being interpreting the differences between the two, or the fact that the spurious processes show up in the former, but not the latter. In th

Re: unexpected Apache::VMonitor output

2005-01-13 Thread Stas Bekman
Todd Finney wrote: At 09:13 AM 1/13/2005 -0500, Stas Bekman wrote: You forgot to mention what Apache::VMonitor version you are using (also what Apache::Scoreboard version) My apologies. VMonitor 2.01 and Scoreboard 0.11. All this information is coming from Apache's scoreboard, A-VM just pulls i

Re: unexpected Apache::VMonitor output

2005-01-13 Thread Stas Bekman
Todd Finney wrote: This is Apache 1.3.33 with mod_perl 1.29 on a mucho-bastardized RH6.2 install with a 2.2.25 kernel. Everything, including Perl 5.8.6, is installed from source just a few hours ago. You forgot to mention what Apache::VMonitor version you are using (also what Apache::Scoreboard