Premature end of headers with user-supplied coods and statusmap.cgi
Ethan Galstad
nagios at nagios.org
Mon Jan 5 04:20:01 CET 2004
Hi Paul -
Any chance you can run gdb and let me know where the segfault is
occurring? Make sure to use the CGIs from the distribution point
and not the installation point, as they are stripped of symbols.
On 23 Dec 2003 at 18:31, Paul L. Allen wrote:
>
> Nagios 1.1 on a Red Hat 7.3 box. Lots of hosts, so I wanted to switch
> to user-supplied coords to prevent the overlaps in circular markup.
>
> So I defined 2d_coords for each host, x and y values range from 0 to
> 400 (all integers) with no two hosts having the same co-ordinate
> pairs. E.g.,
>
> 2d_coords 200,0
>
> Since I saw some examples on the mailing list with a space after the
> comma I have tried this both ways where the is no space after the
> comma for any host and where there is always a space after the comma.
> Same result.
>
> When I select the user-supplied coords layout I get a 500 internal
> server error. Theerror log says "premature end of script errors"
> (that's the only error log entry associated with the problem) which
> usually means that statusmap.cgi has blurted something to STDOUT or
> STDERR before the end of the MIME headers.
>
> So I tried running it from the command-line and learned I had to set
> REQUEST_METHOD to GET and QUERY_STRING as appropriate. Which I did.
> To my surprise, the appropriate headers were output correctly and so
> was some of the HTML, going a little beyond the <body> tag. The last
> line output is as follows (except I've wrapped the line where there
> was a blank space present):
>
> <div id="popup" style="position:absolute; zindex:1; visibility:
> hidden"></div>
>
> And after that line is output there is a segmentation fault. With no
> clues as to why.
>
> I've seen a couple of other reports of problems with user-supplied
> coords but I've not seen any answers. However, the other reports did
> not mention the segmentation fault, so perhaps that will give somebody
> a clue.
>
> In the meantime, I'll have to live with balanced tree layout, which
> would actually be much better than the hassle of user-supplied co-ords
> but for one thing. With the number of hosts I'm monitoring, there's a
> lot of sideways scrolling involved. Rotating the coords by 90 degrees
> would convert that to vertical scrolling (at the minute I have some
> hosts that are gr5andchildren but it goes no deeper so I won't get
> sideways scrolling). Vertical scrolling is a lot easier: you can use
> the arrow keys; you can use the page-up/down keys; you can use the
> mousewheel if you want to develop carpal tunnel syndrome; if you're a
> real masochist you can even click on the scrollbars. Sideways
> scrolling is a pain because you don't have the equivalent of
> page-up/down keys.
>
> So would anyone else be in favour of a feature request to rotate
> (possibly as an option) the output of the tree layouts?
>
> Note that every other layout method works perfectly.
>
> --
> Paul Allen
> Softflare Support
Ethan Galstad,
Nagios Developer
---
Email: nagios at nagios.org
Website: http://www.nagios.org
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list