We're using WebMonkey as a front-end to mon (latest development version) and
we're getting extremely slow performance as it queries the mon server. I'm
far from an expert on mon, so I have no idea what the mon server is doing
while Apache sits there waiting for a response. Here's an excerpt from
strace:
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
ioctl(3, SNDCTL_TMR_TIMEBASE, 0xbffff770) = -1 EINVAL (Invalid argument)
_llseek(3, 0, 0xbffff7c0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
ioctl(3, SNDCTL_TMR_TIMEBASE, 0xbffff770) = -1 EINVAL (Invalid argument)
_llseek(3, 0, 0xbffff7c0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
connect(3, {sin_family=AF_INET, sin_port=htons(2583),
sin_addr=inet_addr("198.69.248.7")}}, 16) = 0
write(3, "protid 9745\n", 12) = 12
read(3,
And it hangs at read(3, for up to five minutes... there's no real load on
the mon server itself during this time... and Apache itself is very lightly
loaded also. (Our mon server and Apache server are separate btw).
Finally this spews out:
read(3, "220 protocol match\n", 4096) = 19
write(3, "list opstatus\n", 14) = 14
read(3, "group=10.0.155.4 service=ping op"..., 4096) = 276
read(3, "group=10.0.201.68 service=ping o"..., 4096) = 1448
read(3, "exitval=0 timer=-221 last_succes"..., 4096) = 1448
...
...
etc
and the page is generated.
My question to you mon gurus is, what does the protid 9745 command do and why
does it take so long? The box the mon server is on is an Athlon XP 1700+ with
half a gig of RAM.
Anyways, pulling my hair out there, and unfortunately I'm not a Perl expert.
If someone could even point me in the right direction to get more debugging
output from mon itself to see what's taking so long it would be appreciated.
Thanks,
Ray Van Dolson
_______________________________________________
mon mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/mon
