RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
Hi Stephen - I don't seem to have that particular issue. -Original Message- From: Barry, Stephen [mailto:[EMAIL PROTECTED] Sent: Thu 01/19/2006 01:36 PM To: Miner, Jonathan W (CSC) (US SSA) Cc: Subject:RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64 I am also running on FC4 x86_64, I get the same message, I am having problems with my hosts list constantly showing different servers. I click host detail and sometimes I get 2 servers, other times I get 8 servers. I am also using Monarch. However I don't know the system well enough to know the cause of the problems I am getting. Has anyone any ideas. Thanks Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miner, Jonathan W (CSC) (US SSA) Sent: 19 January 2006 17:29 To: nagios-users@lists.sourceforge.net 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! This appears during the pre-flight checks. Nagios was compiled with the native GCC compiler, which in this case is: # gcc -v Using built-in specs. Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-libgcj-multifile --enable-languages=c,c++,objc,java,f95,ada --enable-java-awt=gtk --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --host=x86_64-redhat-linux Thread model: posix gcc version 4.0.2 20051125 (Red Hat 4.0.2-8) How concerned should I be? Should I be looking for a 32-bit machine to host my production instance of Nagios? --- 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=kkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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 DISCLAIMER - This email and any file transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions expressed are those of the author and do not represent the views of Derwent Shared Services, unless otherwise explicitly stated. The information contained in this email may be subject to public disclosure under the Freedom of Information Act 2000. Unless the information is legally exempt from disclosure, the confidentiality of this email cannot be guaranteed. Derwent Shared Services is an NHS Shared Services Organisation. --- 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=lnkkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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
RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
-Original Message- From: Barry, Stephen [mailto:[EMAIL PROTECTED] Sent: Thu 01/19/2006 01:36 PM To: Miner, Jonathan W (CSC) (US SSA) Cc: Subject: RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64 I am also running on FC4 x86_64, I get the same message, I am having problems with my hosts list constantly showing different servers. I click host detail and sometimes I get 2 servers, other times I get 8 servers. I am also using Monarch. However I don't know the system well enough to know the cause of the problems I am getting. Has anyone any ideas. Most likely -- http://www.nagios.org/faqs/viewfaq.php?faq_id=21expand=falseshowdesc=f alse -- 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=lnkkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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
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: nagios-users@lists.sourceforge.net 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: nagios-users@lists.sourceforge.net 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=kkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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 --- 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=lnkkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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
RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
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: nagios-users@lists.sourceforge.net 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: nagios-users@lists.sourceforge.net 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: nagios-users@lists.sourceforge.net 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=kkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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 --- 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=kkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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 --- 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=lnkkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
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: nagios-users@lists.sourceforge.net 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: nagios-users@lists.sourceforge.net 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: nagios-users@lists.sourceforge.net 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=kkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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 --- 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=kkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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 --- 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=kkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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 --- This SF.net email is sponsored by: Splunk Inc. Do you
RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
It turns out that struct timeval is different 8-bytes verses 16-bytes. What if
the value of MAX_PLUGINOUTPUT_LENGTH was calculated at compile time, based on
the overall size of the service_message structure? Of course, I think this
would mean that all of your Nagios machines have to be of the same architecture?
I've recompiled with the two changes shown below... So far so good.
*** objects.h.orig 2006-01-19 15:46:13.0 -0500
--- objects.h 2006-01-19 15:46:25.0 -0500
***
*** 45,51
#define MAX_HOSTNAME_LENGTH 64 /* max. host
name length */
#define MAX_SERVICEDESC_LENGTH64 /* max. service
description length */
- #define MAX_PLUGINOUTPUT_LENGTH 348 /* max. length
of plugin output */
#define MAX_STATE_HISTORY_ENTRIES 21 /* max number of old
states to keep track of for flap detection */
--- 45,50
*** nagios.h.orig 2006-01-19 15:47:50.0 -0500
--- nagios.h2006-01-19 15:47:26.0 -0500
***
*** 389,394
--- 389,396
}notification;
+ #define MAX_PLUGINOUTPUT_LENGTH
512-MAX_HOSTNAME_LENGTH-MAX_SERVICEDESC_LENGTH-5*sizeof(int)-2*sizeof(struct
timeval) /* max. length of plugin output */
+
/* SERVICE_MESSAGE structure */
typedef struct service_message_struct{
char host_name[MAX_HOSTNAME_LENGTH];/* host name */
-Original Message-
From: [EMAIL PROTECTED] on behalf of Chris Waters
Sent: Thu 01/19/2006 03:19 PM
To: nagios-users@lists.sourceforge.net
Cc:
Subject:RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
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: nagios-users@lists.sourceforge.net
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: nagios-users@lists.sourceforge.net
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: nagios-users@lists.sourceforge.net
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=kkid3432bid#0486dat1642
___
Nagios-users mailing list
Nagios-users@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
---
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
[Nagios-users] PLEASE REMOVE ME FROM THIS DISTRIBUTION - RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
I need to be removed from this list. How do I need to do that?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Miner,
Jonathan W (CSC) (US SSA)
Sent: Thursday, January 19, 2006 2:59 PM
To: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
It turns out that struct timeval is different 8-bytes verses 16-bytes.
What if the value of MAX_PLUGINOUTPUT_LENGTH was calculated at compile
time, based on the overall size of the service_message structure? Of
course, I think this would mean that all of your Nagios machines have to
be of the same architecture?
I've recompiled with the two changes shown below... So far so good.
*** objects.h.orig 2006-01-19 15:46:13.0 -0500
--- objects.h 2006-01-19 15:46:25.0 -0500
***
*** 45,51
#define MAX_HOSTNAME_LENGTH 64 /* max.
host name length */
#define MAX_SERVICEDESC_LENGTH64 /* max.
service description length */
- #define MAX_PLUGINOUTPUT_LENGTH 348 /* max.
length of plugin output */
#define MAX_STATE_HISTORY_ENTRIES 21 /* max number of
old states to keep track of for flap detection */
--- 45,50
*** nagios.h.orig 2006-01-19 15:47:50.0 -0500
--- nagios.h2006-01-19 15:47:26.0 -0500
***
*** 389,394
--- 389,396
}notification;
+ #define MAX_PLUGINOUTPUT_LENGTH
512-MAX_HOSTNAME_LENGTH-MAX_SERVICEDESC_LENGTH-5*sizeof(int)-2*sizeof(st
ruct timeval) /* max. length of plugin output */
+
/* SERVICE_MESSAGE structure */
typedef struct service_message_struct{
char host_name[MAX_HOSTNAME_LENGTH];/* host name */
-Original Message-
From: [EMAIL PROTECTED] on behalf of Chris
Waters
Sent: Thu 01/19/2006 03:19 PM
To: nagios-users@lists.sourceforge.net
Cc:
Subject:RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
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: nagios-users@lists.sourceforge.net
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: nagios-users@lists.sourceforge.net
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: nagios-users@lists.sourceforge.net
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=kkid3432bid#0486dat1642
___
Nagios-users mailing list
Nagios-users@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
RE: [Nagios-users] PLEASE REMOVE ME FROM THIS DISTRIBUTION - RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64
-Original Message- From: [EMAIL PROTECTED] [mailto:nagios-users- [EMAIL PROTECTED] On Behalf Of Forough, Hamid Sent: Thursday, January 19, 2006 3:02 PM To: Miner, Jonathan W (CSC) (US SSA); nagios-users@lists.sourceforge.net Subject: [Nagios-users] PLEASE REMOVE ME FROM THIS DISTRIBUTION - RE: [Nagios-users] Nagios 2.0rc2 on FC4 x86_64 I need to be removed from this list. How do I need to do that? Follow the link below, go to the bottom of the page, and follow the instructions to 'change your subscription'. Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users -- 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=lnkkid3432bid#0486dat1642 ___ Nagios-users mailing list Nagios-users@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
