I've been seeing this (without problem) throughout the 2.0b series on
x86_64.
As of building 2.0rc2 though, I'm getting errors with the same config
that were not present earlier:
Premature end of script headers: cmd.cgi
Haven't tracked down the cause, it's only occuring now when accessing
the GUI. After initially building rc2 I had problems with nagios
segfaulting. I switched to the p1.pl interpreter from /contrib/ and
that issue went away.
It may be unrelated, but could just now be manifesting itself also.
/eli
Chris Waters wrote:
I have the same issue on Nagios 2.06b FC4 x86_64 although I have not
seen an actualy problem arise from the warning yet that I can tell.
Chris Waters
WAN/LAN Technician
JELD-WEN, Inc.
Network Services Group
===================
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Miner,
Jonathan W (CSC) (US SSA)
Sent: Thursday, January 19, 2006 12:00 PM
To: [email protected]
Subject: RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
I didn't modify "objects.h", so it must be the compiler padding things
differently for 64-bit.
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Marc
Powell
Sent: Thu 01/19/2006 02:32 PM
To: [email protected]
Cc:
Subject: RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:nagios-users-
[EMAIL PROTECTED] On Behalf Of Miner, Jonathan W (CSC) (US
SSA)
Sent: Thursday, January 19, 2006 11:29 AM
To: [email protected]
Subject: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
Hi -
I've noticed an interesting warning when running Nagios on a 64-bit
machine:
Warning: Size of service_message struct (528 bytes) is > POSIX-
guaranteed
atomic write size (512 bytes). Service checks results may get lost
or
mangled!
The most probable reason for this is that you have modified the
MAX_HOSTNAME_LENGTH (64), MAX_SERVICEDESC_LENGTH (64) or
MAX_OLUGINOUTPUT_LENGTH (348) variables from their defaults in
include/objects.h. They are set so that the entire service_message
struct is < 512 bytes. If that's not the case then you may be seeing
compiler oddities that cause other structs or types (int, timeval) to be
larger than normal.
How concerned should I be? Should I be looking for a 32-bit machine
to
host my production instance of Nagios?
While I can't tell you all the possible problems that might result, one
that I know is that if you are using passive checks, the results may get
lost or mangled because they're larger than what can usually be written
to a named pipe in one go. 32-bit vs 64-bit isn't a factor unless 64-bit
allows for larger pipes. The hostname length + service description
length + plugin output length would have to be > ~480 bytes to be
worrisome.
--
Marc
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems? Stop! Download the new AJAX search engine that
makes searching your log files as easy as surfing the web. DOWNLOAD
SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
_______________________________________________
Nagios-users mailing list
[email protected]
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
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems? Stop! Download the new AJAX search engine that
makes searching your log files as easy as surfing the web. DOWNLOAD
SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
_______________________________________________
Nagios-users mailing list
[email protected]
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
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
_______________________________________________
Nagios-users mailing list
[email protected]
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
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Nagios-users mailing list
[email protected]
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
