Re: configuring monit's httpd

[Allen Shaw]

Hi Jan,

> I looked at the gdb stack trace and strace list you sent (mailman
> refused to send your mail to this list because it was to big. Besides
> sending a 700Kb mail to the list may not be appreciated by everyone :)
>
> Anyway, the stack trace did not give much information bacause it was
> run with a stripped monit. (The Makefile that installs monit strips
> away debug information).

Yeah, I'm sorry about the big file -- I should have thought more about that
(won't try it again...).  Thanks for looking at the file yourself.  Martin
also made the same point as you, and based on your helpful instructions, I
have what I hope is useful output from gdb.  Using the non-stripped monit
(compiled with `./config && make` rather than `./config && make make), I get
gdb output like this:

#0  0x0805c959 in fillprocesstree (pt=0x80847e0) at process/common.c:263
263     fillprocesstree(pt->children[i]);
(gdb) bt
#0  0x0805c959 in fillprocesstree (pt=0x80847e0) at process/common.c:263
#1  0x0805c95e in fillprocesstree (pt=0x80847e0) at process/common.c:263
#2  0x0805c95e in fillprocesstree (pt=0x80847e0) at process/common.c:263
#3  0x0805c95e in fillprocesstree (pt=0x80847e0) at process/common.c:263
..
#261926 0x0805c95e in fillprocesstree (pt=0x80847e0) at process/common.c:263
#261927 0x0805c95e in fillprocesstree (pt=0x80847e0) at process/common.c:263
#261928 0x080503c8 in initprocesstree (reference=0xbfffe548)
    at monit_process.c:226
#261929 0x08055ead in validate () at validate.c:149
#261930 0x0804fe25 in do_default () at monitor.c:562
#261931 0x0804f97e in do_action (args=0xbfffe604) at monitor.c:348
#261932 0x0804f649 in main (argc=2, argv=0xbfffe604) at monitor.c:115
#261933 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
(gdb) quit

> Finally, I _did_ test monit version 4.1.1 with the config file you
> submitted, but could not reproduce the problem. Please do a 'uname -a'
> such as shown below so we can see what kind of system you are running.
>
> # uname -a
> Linux localhost 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown
>
>
> Ps. Have you updated glibc or installed a new kernel recently? it's
> not unthinkable that the problem could be related to the system
> itself.

The system has glibc 2.2.90 installed -- I see the latest is 2.3.2, and I
presently cringe at the task of upgrading, but will dive into it if I should
be so recommended by somebody who knows what they're doing (that is, not
me).

And as for the system itself, uname -a tells me this:
Linux example.com 2.4.24-RHsmp122 #2 SMP Mon Jan 5 23:07:13 CST 2004 i686
unknown

If the output shown here gives any clues, I'd love a chance to fix
whatever's going on.  Thanks for your help.

--
Allen Shaw