That was indeed the fix! Adding that option to my checks made them be sent to the central server where everything worked as it should have.
Thank you very much for pointing that out Michael. >Am 27.03.2014 13:48 schrieb "Jonathan Casco" <JCasco at >sentryds.com<https://lists.icinga.org/mailman/listinfo/icinga-users>>: > > Hello everyone, > > I've been troubleshooting an issue with a distributed Icinga setup for some time now both alone and with the Icinga IRC but have been unsuccessful in fixing my issue. > > My issue is that my remote Icinga monitor is not sending its check results to the central server using the ocsp_command that is specified in my icinga.cfg file. If I run the command manually (i.e. ./submit_check_result with some fake parameters) the central server receives them and updates the check's status on the web-page. > > I turned up the debug verbosity for my distributed server and I see that it is successfully running the checks and getting output but makes no mention of trying to send the results using the ocsp_command as you can see below: > > [1395864906.014532] [016.2] [pid=29879] Parsing check output... > > [1395864906.014541] [016.2] [pid=29879] Short Output: SSH OK - OpenSSH_5.5p1 Debian-6+squeeze2 (protocol 2.0) > > [1395864906.014548] [016.2] [pid=29879] Long Output: NULL > > [1395864906.014554] [016.2] [pid=29879] Perf Data: time=0.010223s;;;0.000000;10.000000 > > [1395864906.014562] [016.2] [pid=29879] SERVICE: ST (state_type): HARD CA (current_attempt): 1 MA (max_attempt): 1 CS (current_state): 0 LS (last_state): 0 LHS (last_hard_state): 0 > > [1395864906.014570] [016.1] [pid=29879] Service is OK. > > [1395864906.014576] [016.1] [pid=29879] Service did not change state. > > [1395864906.014589] [001.0] [pid=29879] obsessive_compulsive_service_check_processor() > > [1395864906.014600] [016.1] [pid=29879] Rescheduling next check of service at Wed Mar 26 16:17:02 2014 > > [1395864906.014608] [001.0] [pid=29879] get_next_valid_time() > > [1395864906.014614] [001.0] [pid=29879] check_time_against_period() > > [1395864906.014622] [001.0] [pid=29879] schedule_service_check() > > [1395864906.014632] [016.0] [pid=29879] Scheduling a non-forced, active check of service 'SSH' on host 'host1' @ Wed Mar 26 16:17:02 2014 > > [1395864906.014641] [016.2] [pid=29879] Scheduling new service check event for 'SSH' on host 'host1' @ Wed Mar 26 16:17:02 2014 > > [1395864906.014649] [001.0] [pid=29879] reschedule_event() > > [1395864906.014656] [001.0] [pid=29879] add_event() > > > In my distributed server's icinga.cfg file I have made the appropriate changes to make it a distributed server: > > > enable_notifications=0 > > obsess_over_services=1 > > ocsp_command=submit_check_result And your service objects themselves have obsess_over_service set? http://docs.icinga.org/latest/en/objectdefinitions.html#service > > > Here is the command definition in commands.cfg: > > define command{ > > command_name submit_check_result > > command_line $USER1$/submit_check_result $HOSTNAME$ '$SERVICEDESC$' $SERVICESTATE$ 'SERVICEOUTPUT$' > > } > > > I also tried this in the command_line option but it gave me the same lack of results: > > command_line /usr/bin/printf "\t%s\t%s\t%s\t%s\n" "$HOSTNAME$" "$SERVICEDESC$" "$SERVICESTATEID$" "$SERVICEOUTPUT$" | /usr/sbin/send_nsca -H 10.12.20.210 -c /etc/send_nsca.cfg > > > The submit_check_result script is owned by nagios and has the correct permissions: > > > nagios 3382 1 0 08:47 ? 00:00:00 /usr/sbin/icinga -d /etc/icinga/icinga.cfg > > -rwxr-xr-x 1 nagios nagios 970 Mar 18 16:53 /usr/lib/nagios/plugins/submit_check_result > > > Both hosts are Ubuntu 12.04 running Icinga 1.11.0. > Any hints on what to look into would be appreciated as I have run out of ideas on why this would not work as it should with my current setup. > > > CONFIDENTIALITY NOTICE: This communication and any attachments may contain confidential and/or privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please notify the sender immediately by telephone or email and destroy all copies of this communication and any attachments. > > > > > _______________________________________________ > icinga-users mailing list > icinga-users at > lists.icinga.org<https://lists.icinga.org/mailman/listinfo/icinga-users> > https://lists.icinga.org/mailman/listinfo/icinga-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.icinga.org/pipermail/icinga-users/attachments/20140327/94d55df5/attachment.html> CONFIDENTIALITY NOTICE: This communication and any attachments may contain confidential and/or privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please notify the sender immediately by telephone or email and destroy all copies of this communication and any attachments.
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
