[xymon] Re: Premature end of script headers: bb-histlog.sh xymon 4.3.0-0.beta2

[Asif Iqbal]

On Mon, Aug 16, 2010 at 10:27 AM, Anton Burkhalter
<anton.burkhalter at gmx.net> wrote:
>
>> On Fri, Jul 23, 2010 at 1:57 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
>>
>>>> I am getting core dump only for historical yellow data for some hosts.
>>>>
>>>> apache log:
>>>>
>>>> [Fri Jul 23 16:17:22 2010] [error] [client 192.168.0.94] Premature end
>>>> of script headers: bb-histlog.sh, referer:
>>>> https://xymon.example.net/hobbit-cgi/bb-hist.sh?HISTFILE=cer1cc-015.clientcare.example.net.cpu&ENTRIES=50&IP=192.168.0.209&DISPLAYNAME=cer1cc-015.clientcare.example.net
>>>>
>>>>
>>>> (hobbit)@xymon:~$ REQUEST_METHOD=GET SCRIPT_NAME=bb-histlog.sh
>>>> QUERY_STRING="HOST=cer1cc-014.clientcare.example.net&SERVICE=cpu&TIMEBUF=Wed_Jul_21_14:56:42_2010"
>>>> cgi-bin/bb-histlog.sh
>>>>
>>>> generates core dump.
>>>>
>>>> (hobbit)@xymon:~$ file core
>>>> core:           ELF 32-bit LSB core file 80386 Version 1, from 'hobbitsvc.cgi'
>>>>
>>>> (hobbit)@xymon:~$ gdb server/bin/hobbitsvc.cgi core
>>>> [..]
>>>> (gdb) backtrace
>>>> #0  0xfed64fa1 in realfree () from /lib/libc.so.1
>>>> #1  0xfed655bf in cleanfree () from /lib/libc.so.1
>>>> #2  0xfed64adb in _malloc_unlocked () from /lib/libc.so.1
>>>> #3  0xfed64a04 in malloc () from /lib/libc.so.1
>>>> #4  0x08067621 in xmalloc (size=12) at memory.c:119
>>>> #5  0x0805a1f1 in expand_env (s=0x80707bb "4.2.3") at environ.c:296
>>>> #6  0x0805a08c in xgetenv (name=0x80715c9 "HOBBITDREL") at environ.c:165
>>>> #7  0x0805db08 in headfoot (output=0x8089e28, template=0x80717d3
>>>> "histlog", pagepath=0x80716c6 "", head_or_foot=0x80717f3 "header",
>>>>    bgcolor=4) at headfoot.c:1114
>>>> #8  0x0805f639 in generate_html_log (hostname=0x80913a8
>>>> "cer1cc-014.clientcare.example.net",
>>>>    displayname=0x80913a8 "cer1cc-014.clientcare.example.net",
>>>> service=0x808aa90 "cpu", ip=0x8099168 "10.240.91.208", color=4,
>>>>    sender=0x80ad668 "10.240.91.208", flags=0x806ff21 "", logtime=0,
>>>> timesincechange=0x8047bbc "0.00 minutes",
>>>>    firstline=0x8094128 "yellow Wed Jul 21 14:56:35 GMT 2010 up: 98
>>>> days, 0 users, 624 procs, load=7.51",
>>>>    restofmsg=0x80ae61f "&yellow Load is HIGH\nSystem clock is 0
>>>> seconds off\n\n\n\n\n  2:56pm  up 98 days, 17:04,  0 users,  load
>>>> average: 9.38, 7.51, 4.34\n624 processes: 623 sleeping, 1 running, 0
>>>> zombie, 0 stopped\nCPU states:  0"..., acktime=0, ackmsg=0x0,
>>>> acklist=0x0,
>>>>    disabletime=0, dismsg=0x0, is_history=1, wantserviceid=0,
>>>> htmlfmt=0, hobbitd=0,
>>>>    multigraphs=0x8073060 ",disk,inode,qtree,quotas,snapshot,TblSpace,if_load,",
>>>>    linktoclient=0x808ae40
>>>> "bb-histlog.sh?CLIENT=cer1cc-014.clientcare.example.net&amp8TIMEBUF=1279724202",
>>>> nkprio=0x0, nkttgroup=0x0,
>>>>    nkttextra=0x0, output=0x8089e28) at htmllog.c:150
>>>> #9  0x08054189 in do_request () at hobbitsvc.c:421
>>>> #10 0x0805530e in main (argc=4, argv=Cannot access memory at address 0x555202bc
>>>> ) at hobbitsvc.c:518


hopefully more people will report this to make it a higher priority


-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?