Node monitoring problem

[dooblem]

Hello,

I configured it. Works like a charm for Openvz monitoring:

# /usr/lib/nagios/plugins/pve-monitor.pl --conf /etc/shinken/pve-monitor.conf --openvz       
OPENVZ OK 1 / 1 working VMs
jenkins (clusterprod-1) OK : cpu OK (0.11%), mem OK (68.37%), disk OK (53.10%) uptime 1470557

But it fails to monitor the node itself:

# /usr/lib/nagios/plugins/pve-monitor.pl --conf /etc/shinken/pve-monitor.conf --nodes --debug
Starting pve-monitor 1.07
Setting timeout to 5
Loaded node proxmox1
Loaded openvz jenkins
Trying 10.0.30.14...
DEBUG: login successful
DEBUG: successful request: GET https://10.0.30.14:8006/api2/json/version
User-Agent: libwww-perl/6.05
Cookie: PVEAuthCookie=PVE:monitor@pve:577643BA::p0Xt/8JIG3e1xXaMQQhR2oQjQ57rzY5jp+gMlhCo5p7ZDVIRd25iACztZxpfmW7n7VG2n3NdBc47Dl302VqHo/ybUeRfLWne7kRZ//l80EMwhPsUHSTwAcCFr225TPf3qb8EfUgkf2u5tBgwoITlQwU/anh8FXVkU6/nlQiBBYpL+bjfrV2Vc/e7USZWX2YVHlpOWOEBe+PiPzwpJAxpCSiujmPja2nANLIb4yGQSLzAU/pvGphoWerOKthMahnUqTPew/8vw3Gqv61zUHON87VcKvP5fpAxwFQuWQS0zV188HYVYtF3GybOgRJah2tvyO9RbR+O3uh692kf89cAog==


Successfully connected to 10.0.30.14 !
DEBUG: successful request: GET https://10.0.30.14:8006/api2/json/cluster/status
User-Agent: libwww-perl/6.05
Cookie: PVEAuthCookie=PVE:monitor@pve:577643BA::p0Xt/8JIG3e1xXaMQQhR2oQjQ57rzY5jp+gMlhCo5p7ZDVIRd25iACztZxpfmW7n7VG2n3NdBc47Dl302VqHo/ybUeRfLWne7kRZ//l80EMwhPsUHSTwAcCFr225TPf3qb8EfUgkf2u5tBgwoITlQwU/anh8FXVkU6/nlQiBBYpL+bjfrV2Vc/e7USZWX2YVHlpOWOEBe+PiPzwpJAxpCSiujmPja2nANLIb4yGQSLzAU/pvGphoWerOKthMahnUqTPew/8vw3Gqv61zUHON87VcKvP5fpAxwFQuWQS0zV188HYVYtF3GybOgRJah2tvyO9RbR+O3uh692kf89cAog==


Node 10.0.30.14 is in cluster and seems sane. Using it to query cluster status
DEBUG: successful request: GET https://10.0.30.14:8006/api2/json/cluster/resources
User-Agent: libwww-perl/6.05
Cookie: PVEAuthCookie=PVE:monitor@pve:577643BA::p0Xt/8JIG3e1xXaMQQhR2oQjQ57rzY5jp+gMlhCo5p7ZDVIRd25iACztZxpfmW7n7VG2n3NdBc47Dl302VqHo/ybUeRfLWne7kRZ//l80EMwhPsUHSTwAcCFr225TPf3qb8EfUgkf2u5tBgwoITlQwU/anh8FXVkU6/nlQiBBYpL+bjfrV2Vc/e7USZWX2YVHlpOWOEBe+PiPzwpJAxpCSiujmPja2nANLIb4yGQSLzAU/pvGphoWerOKthMahnUqTPew/8vw3Gqv61zUHON87VcKvP5fpAxwFQuWQS0zV188HYVYtF3GybOgRJah2tvyO9RbR+O3uh692kf89cAog==


Found 296 objects:
Found jenkins in resource list
NODES CRITICAL  0 / 1 working nodes
proxmox1 is in status UNKNOWN

Any idea ? Thanks in advance.

Marc

[ftrojahn]

Same problem here. Any advise or news on this?

Falko

[dpiquet]

Sorry for the late reply,

Are you sure the node name defined in the configuration file is the same as the actual cluster node name ?

[dooblem]

ok ! you got it. Changed the node name in the config and all is fine !

Maybe a small message in the doc would help ?

Anyway, thanks.