2017-06-05 13:11:18 |
Simon Pasquier |
description |
All AFD which are evaluated against already aggregated metrics are sent to Nagios but are not configured.
In nagios log, those entries appear continuously :
[2017-02-14 14:22:12] Warning: Passive check result was received for service 'keystone-public-api-check.vip' on host 'node-7', but the service could not be found!
This concerns all AFD related to metrics listed in metrics.yaml (https://github.com/openstack/fuel-plugin-lma-collector/blob/master/deployment_scripts/puppet/modules/fuel_lma_collector/templates/metrics.yaml.erb):
cinder-api-check.vip
cinder-scheduler.workers
cinder-v2-api-check.vip
cinder-volume.workers
glance-api-check.vip
heat-api-check.vip
heat-cfn-api-check.vip
influxdb-api-check.vip
keystone-public-api-check.vip
neutron-api-check.vip
neutron-dhcp.workers
neutron-l3.workers
neutron-metadata.workers
neutron-openvswitch.workers
nova-api-check.vip
nova-cert.workers
nova-compute.workers
nova-conductor.workers
nova-consoleauth.workers
nova-free-memory.nova-free-memory
nova-free-vcpu.nova-free-vcpu
nova-scheduler.workers
rabbitmq-cluster.pacemaker
swift-api-check.vip
swift-s3-api-check.vip |
All AFD which are evaluated against already aggregated metrics are sent to Nagios but are not configured.
In nagios log, those entries appear continuously :
[2017-02-14 14:22:12] Warning: Passive check result was received for service 'keystone-public-api-check.vip' on host 'node-7', but the service could not be found!
This concerns all AFD related to metrics listed in metrics.yaml (https://github.com/openstack/fuel-plugin-lma-collector/blob/master/deployment_scripts/puppet/modules/fuel_lma_collector/templates/metrics.yaml.erb):
cinder-api-check.vip
cinder-scheduler.workers
cinder-v2-api-check.vip
cinder-volume.workers
glance-api-check.vip
heat-api-check.vip
heat-cfn-api-check.vip
influxdb-api-check.vip
keystone-public-api-check.vip
neutron-api-check.vip
neutron-dhcp.workers
neutron-l3.workers
neutron-metadata.workers
neutron-openvswitch.workers
nova-api-check.vip
nova-cert.workers
nova-compute.workers
nova-conductor.workers
nova-consoleauth.workers
nova-free-memory.nova-free-memory
nova-free-vcpu.nova-free-vcpu
nova-scheduler.workers
rabbitmq-cluster.pacemaker
swift-api-check.vip
swift-s3-api-check.vip
Workaround
==========
On the infrastructure-alerting nodes, create /etc/rsyslog.d/00-discard-nagios-passive-checks.conf with the following content
# Discard Nagios messages about unsollicited passive check results
:msg, contains, "Warning: Passive check result was received for service" ~
Then restart rsyslogd:
/etc/init.d/rsyslogd restart |
|