NDOUtils 1.4 Stability

[Janet Post]

Hello All,

 

I have installed NDOUtils (1.4b2).  I am using nagios 2.8 on a RedHat EL
4.

 

I have connected ndomod and ndo2db-2x via socket, and everything -seems-
fine.  There are no errors in the logfiles, and, in the database, I get
nagios_conninfo entries for the connection...but nothing else.

 

I used socketdebug to see what information was being sent over the
socket, and this is the output:

 

-----------------------------------------------

server:/usr/local/nagios/var$ sudo -u nagios ../bin/sockdebug ./ndo.sock

 

 

HELLO

PROTOCOL: 2

AGENT: NDOMOD

AGENTVERSION: 1.4b2

STARTTIME: 1176480042

DISPOSITION: REALTIME

CONNECTION: UNIXSOCKET

CONNECTTYPE: INITIAL

INSTANCENAME: default

STARTDATADUMP

 

 

 

-----------------------------------------------

 

 

And that's it.  No more information is ever communicated over the
socket.  NDOMOD gives no error messages, no log entries are made,
nothing.  I have no idea what is happening at this point.

 

Nagios continues to write status information to the regular files on the
drive as if ndomod were not running.  If anyone could give me a hand
with this, I would appreciate it greatly.  Thanks.

 

Janet

 

 

Some relevant configurations:  (if you need anymore, let me know)

 

 

Nagios.cfg:

 

--------------<snip>--------------------------

# Config parameter for ndoutils: 

broker_module=/usr/local/nagios/bin/ndomod-2x.o
config_file=/usr/local/nagios/etc/ndomod.cfg

--------------<snip>--------------------------

 

Ndomod.cfg:

 

-------------<all comments removed>-----------

instance_name=default

output_type=unixsocket

output=/usr/local/nagios/var/ndo.sock

tcp_port=5668

output_buffer_items=5000

buffer_file=/usr/local/nagios/var/ndomodbuffer.tmp

file_rotation_interval=14400

#file_rotation_command=rotate_ndo_log

file_rotation_timeout=60

reconnect_interval=15

reconnect_warning_interval=15

data_processing_options=-1

config_output_options=3

----------------------------------------------

 

 

 

-----Original Message-----
From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Janet
Post
Sent: April 11, 2007 4:45 PM
To: Ton Voon
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] NDOUtils 1.4 Stability

 

Ton,

 

So ndomod will take the nagios process with it.  That does not sound

very comforting.  I run a 24x7 monitoring environment complete with NOC

team, and having our monitoring system just stop tends to annoy upper

management.  

 

Does this happen very often?  I'm not too worried about it if the system

is mostly stable.  What kind of uptimes have people had with this very

handy tool?

 

Janet

 

 

 

-----Original Message-----

From: Ton Voon [mailto:ton.voon at altinity.com] 

Sent: April 11, 2007 4:26 PM

To: Patrick Morris

Cc: Janet Post; nagios-users at lists.sourceforge.net

Subject: Re: [Nagios-users] NDOUtils 1.4 Stability

 

 

On 11 Apr 2007, at 21:20, Patrick Morris wrote:

 

> On Wed, 11 Apr 2007, Janet Post wrote:

> 

>> Hello Everyone,

>> 

>> I would -really- like to use the NDOUtils for my nagios 2.8 install.

>> But the big **DO NOT USE IN PRODUCTION ENVIRONMENT** warning is a  

>> little

>> scary.

>> 

>> Here are some questions for you all who are using it (and the

>> developers):

>> 

>> 1) is there any outward sign that the NDOMOD module has  

>> segfaulted?  A

>> logfile?

>> 

>> 2) Can nagios monitor this itself?  Or will a crash in NDOMOD cause

>> nagios itself to die as well?  (I was thinking of having nagios watch

>> for the NDOMOD process, and if it wasn't there, restart  

>> everything...but

>> if nagios goes down too, that obviously won't work)

>> 

>> 3) Any ETA on when NDOUtils will be ready?   Losing database  

>> support was

>> one of the reasons I did not want to upgrade to nagios 2.x.  Pointing

>> the cold spare to a database with up-to-date status information is  

>> just

>> easy!

> 

> Nagios will keep running if ndmomod dies; it just won't log to a

> database any more.  It's pretty easy to spot the insertion errors in

> Nagios's log if/when it happens, or by monitoring the process as you

> mentioned.

 

I don't think that is strictly true. Since ndomod is running in the  

same process space as Nagios, a problem with the broker module will  

cause the main nagios process to die too.

 

However, a failure at ndo2db (that writes to the db) will not affect  

Nagios.

 

Ton

 

 

http://www.altinity.com

T: +44 (0)870 787 9243

F: +44 (0)845 280 1725

Skype: tonvoon

 

 

 

------------------------------------------------------------------------
-

Take Surveys. Earn Cash. Influence the Future of IT

Join SourceForge.net's Techsay panel and you'll get the chance to share
your

opinions on IT & business topics through brief surveys-and earn cash

http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V

_______________________________________________

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070413/bf9acbbb/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
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