ndoutils - new objects not active after reload

[Andreas Ericsson]

Wolfgang Powisch wrote:
> Hi,
> 
> I'm using ndoutils 1.3.1 with nagios 2.x and seeing the following problem:
> 
> My web-application queries the ndo_servicestate or ndo_hoststate table with an
> additional filter "WHERE ndo_objects.is_active=1" to get the current service and host
> states. This works well most of the time.
> 
> Now, I noticed, that every time, I add a new service or host and reload/restart
> (same behaviour) nagios, the new objects are in ndo database, but the is_active
> field is 0. An additional nagios reload/restart makes them active.
> I could reproduce this behaviour every time when adding new hosts or services.
> 
> Any Ideas if this is a bug or any reason this may be intended.
> What exactly is the "is_active" field intended for ?
> 

Use the source, Luke. If you find the answer, let us know. Documentation 
for the NDO utils are nowhere near complete, and I daresay Ethan would 
find it useful to get a bit of help with it.

A sort of semi-educated guess (based on the column-name) is that it 
denotes services and hosts that have active checks enabled, or that have 
been checked at least once. How long did you let Nagios run before you 
restarted it?

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

-------------------------------------------------------------------------
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
_______________________________________________
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