Menu
▾
▴
nagios-users
|
From: Daniel B. <dan...@gm...> - 2013-09-25 18:52:17
Attachments:
signature.asc
|
Hi all! Since I saw recently released version 4.0.0 of Nagios Core, today I tried to test it using the update procedure published [1]. But, from what I saw, the process does not start after doing a "restart". Viewing the /usr/local/nagios/var/nagios.log, I find the following: ------------------------------------------------------------------------- [1380134669] Warning: use_embedded_perl_implicitly is deprecated and will be removed. [1380134669] Warning: enable_embedded_perl is deprecated and will be removed. [1380134669] Warning: p1_file is deprecated and will be removed. [1380134669] Warning: sleep_time is deprecated and will be removed. [1380134669] Warning: external_command_buffer_slots is deprecated and will be removed. All commands are always processed upon arrival [1380134669] Warning: command_check_interval is deprecated and will be removed. Commands are always handled on arrival [1380134669] Nagios 4.0.0 starting... (PID=23082) [1380134669] Local time is Wed Sep 25 15:44:29 ART 2013 [1380134669] LOG VERSION: 2.0 [1380134669] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized [1380134669] qh: core query handler registered [1380134669] nerd: Channel hostchecks registered successfully [1380134669] nerd: Channel servicechecks registered successfully [1380134669] nerd: Channel opathchecks registered successfully [1380134669] nerd: Fully initialized and ready to rock! [1380134669] wproc: Successfully registered manager as @wproc with query handler [1380134669] wproc: Registry request: name=Core Worker 23085;pid=23085 [1380134669] wproc: Registry request: name=Core Worker 23086;pid=23086 [1380134669] wproc: Registry request: name=Core Worker 23084;pid=23084 [1380134669] wproc: Registry request: name=Core Worker 23083;pid=23083 [1380134669] Error: Module '/usr/local/nagios/bin/npcdmod.o' is using an old or unspecified version of the event broker API. Module will be unloaded. [1380134669] Event broker module '/usr/local/nagios/bin/npcdmod.o' deinitialized successfully. [1380134669] Error: Failed to load module '/usr/local/nagios/bin/npcdmod.o'. [1380134669] Error: Module loading failed. Aborting. ------------------------------------------------------------------------- May Nagios not start for failure on npcdmod.o module? Is it necessary to do something else that is not documented in [1]? Thanks in advance for your reply. Regards, Daniel [1] http://nagios.sourceforge.net/docs/nagioscore/4/en/upgrading.html#nagios3x -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598 |
|
From: Paul D. <wo...@pa...> - 2013-09-25 19:27:36
|
Are you using the latest version of PNP4Nagios? If so, maybe it doesn't support Nagios 4.0 yet? Daniel Bareiro wrote: > > Hi all! > > > Since I saw recently released version 4.0.0 of Nagios Core, today I > tried to test it using the update procedure published [1]. > > But, from what I saw, the process does not start after doing a > "restart". > > Viewing the /usr/local/nagios/var/nagios.log, I find the following: > > ------------------------------------------------------------------------- > [1380134669] Warning: use_embedded_perl_implicitly is deprecated and will be removed. > [1380134669] Warning: enable_embedded_perl is deprecated and will be removed. > [1380134669] Warning: p1_file is deprecated and will be removed. > [1380134669] Warning: sleep_time is deprecated and will be removed. > [1380134669] Warning: external_command_buffer_slots is deprecated and will be removed. All commands are always processed upon arrival > [1380134669] Warning: command_check_interval is deprecated and will be removed. Commands are always handled on arrival > [1380134669] Nagios 4.0.0 starting... (PID=23082) > [1380134669] Local time is Wed Sep 25 15:44:29 ART 2013 > [1380134669] LOG VERSION: 2.0 > [1380134669] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized > [1380134669] qh: core query handler registered > [1380134669] nerd: Channel hostchecks registered successfully > [1380134669] nerd: Channel servicechecks registered successfully > [1380134669] nerd: Channel opathchecks registered successfully > [1380134669] nerd: Fully initialized and ready to rock! > [1380134669] wproc: Successfully registered manager as @wproc with query handler > [1380134669] wproc: Registry request: name=Core Worker 23085;pid=23085 > [1380134669] wproc: Registry request: name=Core Worker 23086;pid=23086 > [1380134669] wproc: Registry request: name=Core Worker 23084;pid=23084 > [1380134669] wproc: Registry request: name=Core Worker 23083;pid=23083 > [1380134669] Error: Module '/usr/local/nagios/bin/npcdmod.o' is using an old or unspecified version of the event broker API. Module will be unloaded. > [1380134669] Event broker module '/usr/local/nagios/bin/npcdmod.o' deinitialized successfully. > [1380134669] Error: Failed to load module '/usr/local/nagios/bin/npcdmod.o'. > [1380134669] Error: Module loading failed. Aborting. > ------------------------------------------------------------------------- > > May Nagios not start for failure on npcdmod.o module? Is it necessary to > do something else that is not documented in [1]? > > > > Thanks in advance for your reply. > > > Regards, > Daniel > > [1] http://nagios.sourceforge.net/docs/nagioscore/4/en/upgrading.html#nagios3x > > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Nagios-users mailing list > Nag...@li... > 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 > |
|
From: Daniel B. <dan...@gm...> - 2013-09-25 20:52:29
Attachments:
signature.asc
|
Hi, Paul. On Wednesday, 25 September 2013 15:27:23 -0400, Paul Dubuc wrote: > Are you using the latest version of PNP4Nagios? If so, maybe it doesn't > support Nagios 4.0 yet? Mmmmmm... now that you mention it, I installed it some time ago but I'm not giving extensive use so I may uninstall (or disable) it. I'll try to find a way to do it. Thanks for your replay. Regards, Daniel -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Wheezy - Linux user #188.598 |
|
From: Sven N. <Sven.Nierlein@Consol.de> - 2013-09-25 19:45:38
|
On 9/25/13 21:27, Paul Dubuc wrote: > Are you using the latest version of PNP4Nagios? If so, maybe it doesn't > support Nagios 4.0 yet? PNP4Nagios works with Nagios4 without any modification, but you have to compile the npcdmod against the Nagios4 headers and includes. Sven |
|
From: Daniel B. <dan...@gm...> - 2013-09-26 01:02:27
Attachments:
signature.asc
|
Hi, Sven. On Wednesday, 25 September 2013 21:45:29 +0200, Sven Nierlein wrote: > > Are you using the latest version of PNP4Nagios? If so, maybe it > > doesn't support Nagios 4.0 yet? > PNP4Nagios works with Nagios4 without any modification, but you have > to compile the npcdmod against the Nagios4 headers and includes. I was reviewing the installation of Nagios which also installed PNP4Nagios and I could not find the source code of the latter so I will not be able to uninstall it with a simple "make uninstall". So what I'm trying to do is disable it. For this I was reviewing the Nagios configuration files in /usr/local/nagios/etc. nagios.cfg: I commented the following line: broker_module=/usr/local/nagios/bin/npcdmod.o Also I deleted the references to PNP4Nagios in the configuration files into the "objects" directory. With these changes I got that Nagios can start, however there are some sections that are not yet operational: * Map. * Trends. * Alerts -> Histogram. Reviewing again in /usr/local/nagios/var/nagios.log, I found the following records are repeated continuously: ------------------------------------------------------------------------- [1380156849] wproc: HOST PERFDATA job 1983 from worker Core Worker 27245 is a non-check helper but exited with return code 2 [1380156849] wproc: command: /usr/bin/perl /usr/local/nagios/libexec/process_perfdata.pl -d HOSTPERFDATA [1380156849] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0; [1380156849] Worker 27245: Unknown jobtype: 9 [1380156849] wproc: Unknown job type: 9 [1380157096] wproc: SERVICE PERFDATA job 2020 from worker Core Worker 27246 is a non-check helper but exited with return code 2 [1380157096] wproc: command: /usr/bin/perl /usr/local/nagios/libexec/process_perfdata.pl [1380157096] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0; [1380157096] Worker 27246: Unknown jobtype: 10 ------------------------------------------------------------------------- May this have to do with the components that are not yet operational? Thanks for your reply. Regards, Daniel -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598 |
|
From: Daniel B. <dan...@gm...> - 2013-09-29 16:51:29
Attachments:
signature.asc
|
Hi all! On Wednesday, 25 September 2013 22:02:14 -0300, Daniel Bareiro wrote: > I was reviewing the installation of Nagios which also installed > PNP4Nagios and I could not find the source code of the latter so I will > not be able to uninstall it with a simple "make uninstall". So what I'm > trying to do is disable it. > > For this I was reviewing the Nagios configuration files in > /usr/local/nagios/etc. > > nagios.cfg: I commented the following line: > > broker_module=/usr/local/nagios/bin/npcdmod.o > > Also I deleted the references to PNP4Nagios in the configuration files > into the "objects" directory. > > With these changes I got that Nagios can start, however there are some > sections that are not yet operational: > > * Map. > * Trends. > * Alerts -> Histogram. > > Reviewing again in /usr/local/nagios/var/nagios.log, I found the > following records are repeated continuously: > > ------------------------------------------------------------------------- > [1380156849] wproc: HOST PERFDATA job 1983 from worker Core Worker 27245 is a non-check helper but exited with return code 2 > [1380156849] wproc: command: /usr/bin/perl /usr/local/nagios/libexec/process_perfdata.pl -d HOSTPERFDATA > [1380156849] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0; > [1380156849] Worker 27245: Unknown jobtype: 9 > [1380156849] wproc: Unknown job type: 9 > [1380157096] wproc: SERVICE PERFDATA job 2020 from worker Core Worker 27246 is a non-check helper but exited with return code 2 > [1380157096] wproc: command: /usr/bin/perl /usr/local/nagios/libexec/process_perfdata.pl > [1380157096] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0; > [1380157096] Worker 27246: Unknown jobtype: 10 > ------------------------------------------------------------------------- > > May this have to do with the components that are not yet operational? Although still have these messages in the log, I could fix the errors I was having to try to get the Map, Trends and Alerts -> Histogram. The configure was not finding the GD library and include files. When now entered in the status map for the first time, the default was "user-supplied coords", with the message below: "You have not supplied any host drawing coordinates, so you cannot use this layout method. Read the FAQs for more information on specifying drawing coordinates or select a different layout method" If I select "circular (marked up)", I think it was the layout I was using with Nagios Core 3.5.0, and update, I keep getting the same message without being able to see the map. Is there to do some additional configuration? Regards, Daniel -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598 |
|
From: Daniel B. <dan...@gm...> - 2013-09-29 18:39:16
Attachments:
signature.asc
|
On Sunday, 29 September 2013 13:51:13 -0300, Daniel Bareiro wrote: > Although still have these messages in the log, I could fix the errors I > was having to try to get the Map, Trends and Alerts -> Histogram. The > configure was not finding the GD library and include files. > > When now entered in the status map for the first time, the default was > "user-supplied coords", with the message below: > > "You have not supplied any host drawing coordinates, so you cannot use > this layout method. Read the FAQs for more information on specifying > drawing coordinates or select a different layout method" > > If I select "circular (marked up)", I think it was the layout I was > using with Nagios Core 3.5.0, and update, I keep getting the same > message without being able to see the map. Is there to do some > additional configuration? This is a bug found after released version 4.0.0 of Nagios Core [1]. Regards, Daniel [1] http://tracker.nagios.org/view.php?id=470 -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598 |
Thanks for helping keep SourceForge clean.
X