Alert forwarding from master to server through NSCA
-
kgopiramesh
Alert forwarding from master to server through NSCA
Hi All,
I am very new to nagios and I want to transfer the data from the nagios master server to the slave server through nsca,
I have configured the slave server as master server with the host details and service details and the master will be monitor the hosts in the network, I want to forward the service check results to slave server as part of the fail over configuration.
Adding nsca outbound transfers on the master sevrer and inbound transfer would suffice my requirement or is there any additional configuration needs to be done.
I am very new to nagios and I want to transfer the data from the nagios master server to the slave server through nsca,
I have configured the slave server as master server with the host details and service details and the master will be monitor the hosts in the network, I want to forward the service check results to slave server as part of the fail over configuration.
Adding nsca outbound transfers on the master sevrer and inbound transfer would suffice my requirement or is there any additional configuration needs to be done.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Alert forwarding from master to server through NSCA
That sounds like the correct setup to me.
-
kgopiramesh
Re: Alert forwarding from master to server through NSCA
Thanks Scott for the reply, the setup was not helping me to forward the host and service check results to the slave server,
I have done the below steps to forward the alerts from the master server to slave server
1) In the master servers , I have enabled the data transfers globally and allowed outbound transfers in nsca section
2) Added the slave servers ip as destination and the password, encryption mechanism as well
3) In the inbound transfer section gave the master Ip and password, encryption mechnism and edited the nsca.cfg to add the allow_hosts.
but the alerts are not getting forwarded to the slave server, the debug option also not writing any thing in log files.
when i tried to run the service start command -> service nsca start, it gave the output as unrecognized service
Please let me know if any additional steps to be carried out.
I have done the below steps to forward the alerts from the master server to slave server
1) In the master servers , I have enabled the data transfers globally and allowed outbound transfers in nsca section
2) Added the slave servers ip as destination and the password, encryption mechanism as well
3) In the inbound transfer section gave the master Ip and password, encryption mechnism and edited the nsca.cfg to add the allow_hosts.
but the alerts are not getting forwarded to the slave server, the debug option also not writing any thing in log files.
when i tried to run the service start command -> service nsca start, it gave the output as unrecognized service
Please let me know if any additional steps to be carried out.
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Alert forwarding from master to server through NSCA
Are you sure that you restarted xinetd? You said that the changes were made but mentioned trying to restart a nsca service, so it is likely the changes did not take. Please restart xinetd is it is responsible for loading NSCA:
Code: Select all
service xinetd restart-
kgopiramesh
Re: Alert forwarding from master to server through NSCA
I have restarted the xinetd service, but still the issue is not resolved,
I have created two services of ping and / disk space usage on the master server with the active & passive checks enabled, and configured the same services of the same server and have disabled the active checks on nagios.cfg file
for the / disk usage service, I believe the alert was forwarded since I have disabled on active checks but on the slave server, the alert description came as different.
For the ping service, I didn't see any update coming to the slave server from the master server.
Let me know if there are any additional steps needs to be configured to accept the service check results.
I have created two services of ping and / disk space usage on the master server with the active & passive checks enabled, and configured the same services of the same server and have disabled the active checks on nagios.cfg file
for the / disk usage service, I believe the alert was forwarded since I have disabled on active checks but on the slave server, the alert description came as different.
For the ping service, I didn't see any update coming to the slave server from the master server.
Let me know if there are any additional steps needs to be configured to accept the service check results.
-
kgopiramesh
Re: Alert forwarding from master to server through NSCA
I have added the one server with 5 services in master server, and I could see only two services in unconfigured objects in slave server with one service check status as ok another one as pending
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Alert forwarding from master to server through NSCA
Have the other checks that you added actually received any status updates? They should get pushed over as this happens since they are being forwarded.
-
kgopiramesh
Re: Alert forwarding from master to server through NSCA
No only some service updates are recieving at the slave end, the master is having the health of all the services that are added.
Edit: is there any way to troubleshoot the problems in alert forwarding with NSCA.
Edit: is there any way to troubleshoot the problems in alert forwarding with NSCA.
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: Alert forwarding from master to server through NSCA
You can look at the syslog if you enable debugging within the nsca.cfg, you should only need to set 1 for debug=. Additionally, have you looked in unconfigured objects or your nagios log on the slave system recieving the nsca checks for unconfigured or unmatching hosts\services?
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
-
kgopiramesh
Re: Alert forwarding from master to server through NSCA
I have enabled the debug option but it is not giving any details and when I configured the 5 services on master server and didn't add them on the slave server, after some time I could see only two services one with the health result and another with the pending health check and am not sure why all the services are not reflecting in nagios un configured objects.
Edit: Hi,
Please find the attached screen shots for reference. the all service updates are not reflecting in the slave server, and some services output also coming wrong.
example :
on the slave server the status of the service is
/: 43%used(21874MB/50397MB) (80%) : OK
NOAS-IC-FRK-Switch5 Port 10112 Status 2 CRITICAL: Interface GigabitEthernet0/12 (index 10112) is down.
In this noas-ic-frk-switch5 is another switch and / service is of another host.
on the master server :
health status of the / file system is
/: 43%used(21874MB/50397MB) (<80%) : OK
Edit: Hi,
Please find the attached screen shots for reference. the all service updates are not reflecting in the slave server, and some services output also coming wrong.
example :
on the slave server the status of the service is
/: 43%used(21874MB/50397MB) (80%) : OK
NOAS-IC-FRK-Switch5 Port 10112 Status 2 CRITICAL: Interface GigabitEthernet0/12 (index 10112) is down.
In this noas-ic-frk-switch5 is another switch and / service is of another host.
on the master server :
health status of the / file system is
/: 43%used(21874MB/50397MB) (<80%) : OK
You do not have the required permissions to view the files attached to this post.
Last edited by slansing on Tue Apr 08, 2014 9:33 am, edited 1 time in total.
Reason: Merged your two posts, please do not double post as that will bump you lower on our "to be replied to" list.
Reason: Merged your two posts, please do not double post as that will bump you lower on our "to be replied to" list.