Error: Function nebmodule_init() in module'/usr/local/nagios/bin/ndomod.o' returned an error.

[Steffen Poulsen]

Hi,

Thanks to Denis, who wrote us this excellent little tip, we now have NDO working (yay!):

------

I saw your post on NDOUtils, http://archive.netbsd.se/?ml=nagios-devel&a=2007-11&m=5574880 

And I just had a similar problem. To debug I added checkpoint to nebmodule_init()

i.e. 

        /* process arguments */
        if(ndomod_process_module_args(args)==NDO_ERROR) {
                ndomod_write_to_logs("arguments error\x0",NSLOG_INFO_MESSAGE);
                return -1;
        }

and it was an args error, which turned out to be the fact that in nagios.cfg I had two spaces before 'config_file' (I suspect because I copy-pasted the line from a how-to): 

broker_module=/gw/nagios/bin/ndomod.o  config_file=/gw/nagios/etc/ndomod.cfg 

When I deleted one, it started working fine. 

-------

So, beware of the two-spaces-cut-and-paste error out there :-)

Best regards,
Steffen



> -----Oprindelig meddelelse-----
> Fra: nagios-devel-bounces at lists.sourceforge.net 
> [mailto:nagios-devel-bounces at lists.sourceforge.net] På vegne 
> af Steffen Poulsen
> Sendt: 1. november 2007 13:55
> Til: Nagios Developers List
> Emne: [Nagios-devel] Error: Function nebmodule_init() in 
> module'/usr/local/nagios/bin/ndomod.o' returned an error.
> 
> Hi,
> 
> We have just tried upgrading to 3.0b6, and ndo 1.4b7.
> 
> While nagios itself definetely seems more stable in this 
> version (thanks!), ndo is not able to load properly:
> 
> [1193912686] Caught SIGHUP, restarting...
> [1193912688] Nagios 3.0b6 starting... (PID=1125) [1193912688] 
> LOG VERSION: 2.0 [1193912688] ndomod: NDOMOD 1.4b7 
> (10-31-2007) Copyright (c) 2005-2007 Ethan Galstad 
> (nagios at nagios.org) [1193912688] Error: Function 
> nebmodule_init() in module '/usr/local/nagios/bin/ndomod.o' 
> returned an error.  Module will be unloaded.
> [1193912688] Event broker module 
> '/usr/local/nagios/bin/ndomod.o' deinitialized successfully.
> 
> Unfortunately it is not explicit in what the error is, and we 
> are unsure how to debug.
> 
> Any ideas?
> 
> Best regards,
> Steffen

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/