Is it possible to include the VMs running on a node in the monitoring?
For example: I've created the VM monitoring on farm4. Farm4 is monitored in the PVE cluster, can I find any details about this specific VM?

Hello, I recently needed to get a proxmox cluster into monitoring and find this pve-check absolutely useful. I managed to get it working in less than 1 hour e2e.
We have some issues with one of the nodes swapping and this feature is missing in the check, but it's quite important.
Tried to modify the perl script myself, but it's not easy to mess with someone else's code.
So, is there going to be a swap feature?
It is available under" nodes//status

Hi Damien,
I've come accross an issue in the regular expression used to parse node names .
My cluster node names contain the '-' character which is not contained in \w .
\w Match "word" character (alphanumeric plus "_")
\S Match non-whitespace character
So , on line 281 i had to replace
if ( $objLine =~ m/([\w.]+)\s+([\w.]+)(\s+([\w.]+))?/i ) {
with
if ( $objLine =~ m/([\w.]+)\s+([\S.]+)(\s+([\w.]+))?/i ) {

This works for me but i'm not sure if it breaks anything else :)
Rgds
Ian

Hello,

First of all, monitoring nodes and storages works like a charm for me, thanks!

Unfortunately, whenever I add an "lxc" or "container" declaration in my .conf file, pve-monitor recognizes this declaration as an openvz container.
Obviously, the result is CRITICAL - status UNKNOWN.

Is this a bug or am I missing something here?
Any help would be greatly appreciated.
Thanks in advance.

Tim

Hello,

Thanks for your work !
I have a little issue, when i'm trying to check my containers - i got an unknown state :

OPENVZ CRITICAL 0 / 6 working VMs
mail is in status UNKNOWN
frontal is in status UNKNOWN
...

Thanks for you help.

When an email is sent, $reportSummary remains empty.
Sample email:

***** Nagios *****

Notification Type: RECOVERY

Service: Qemu VMs
Host: pve-cluster
Address: pve-cluster
State: OK

Date/Time: Fri Mar 6 11:21:44 CET 2015

Additional Info:

QEMU OK 3 / 3 working VMs

if I interpret this line correctly, the report data should be appended to the email, right?

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

I've installed nagios according to this tutorial. But I don't have the folder /etc/nagios3/conf.d/ present, as described in this step in the wiki.

I'm also unsure where to put the configuration file that is mentioned here.

The nagios version I'm using is Nagios® Core™ 4.0.8.

Thank you!

Hi their,
is it possible to define a couple VM/LXC pools and chose in command line which one i need to monitor. As example:
perl pve-monitor.pl --conf prod-pve-monitor.conf --conf prod-pve-monitor.conf --pools <POOLNAME> --containers --qemu
it will be useful to define a different Nagios checks without creating a different conf files.

Thank you.

I was trying to monitor two nodes not in the same cluster, but seems the main loop just connects to one node and then the rest of checks are done using that connection.

Hi,

As said in the title, I got a lot of False positive memory alert due to cached ram on monitored openvz containers.

I didn't dig in the code yet so I don't know if I'm missing something in the configuration of pve-monitor or if it's a feature not implemented.

I use another plugin for hosts monitoring (linux-snmp for the record) that didn't encounter the same problem.

I don't really know what logs I can provide to help, so if you need more informations, please ask.

Thanks in advance.

See if it is possible to check rgmanager status via API

Hello,

I'm using pve-monitor 1.07 on CentOS 7 and getting this warning on every command execution :

Using the default of SSL_​verify_​mode of SSL_​VERIFY_​NONE for client is deprecated! Please set SSL_​verify_​mode to SSL_​VERIFY_​PEER together with SSL_​ca_​file If you really don't want to verify the certificate and keep the connection open to Man-​In-​The-​Middle attacks please set SSL_​verify_​mode explicitly to SSL_​VERIFY_​NONE in your application. ******************************************************************* at /usr/lib64/perl5/LWP/Protocol/http.​pm line 35. length​() used on @array (did you mean "scalar​(@array)​"?) at /usr/lib64/perl5/IO/Compress/Zlib/Extra.​pm line 198. ******************************************************************* Using the default of SSL_​verify_​mode of SSL_​VERIFY_​NONE for client is deprecated! Please set SSL_​verify_​mode to SSL_​VERIFY_​PEER together with SSL_​ca_​file If you really don't want to verify the certificate and keep the connection open to Man-​In-​The-​Middle attacks please set SSL_​verify_​mode explicitly to SSL_​VERIFY_​NONE in your application. ******************************************************************* at /usr/lib64/perl5/LWP/Protocol/http.​pm line 35. ******************************************************************* Using the default of SSL_​verify_​mode of SSL_​VERIFY_​NONE for client is deprecated! Please set SSL_​verify_​mode to SSL_​VERIFY_​PEER together with SSL_​ca_​file If you really don't want to verify the certificate and keep the connection open to Man-​In-​The-​Middle attacks please set SSL_​verify_​mode explicitly to SSL_​VERIFY_​NONE in your application. ******************************************************************* at /usr/lib64/perl5/LWP/Protocol/http.​pm line 35. ******************************************************************* Using the default of SSL_​verify_​mode of SSL_​VERIFY_​NONE for client is deprecated! Please set SSL_​verify_​mode to SSL_​VERIFY_​PEER together with SSL_​ca_​file If you really don't want to verify the certificate and keep the connection open to Man-​In-​The-​Middle attacks please set SSL_​verify_​mode explicitly to SSL_​VERIFY_​NONE in your application. ******************************************************************* at /usr/lib64/perl5/LWP/Protocol/http.​pm line 35. OPENVZ OK 5 / 5 working VMs

It is saying that it is possible to "SSL_​verify_​mode explicitly to SSL_​VERIFY_​NONE" but it'd be insecure.

I have installed it as follows:

yum install perl-CPAN perl-JSON perl-libwww-perl perl-IO-Socket-SSL perl-Switch
cpan install Net::Proxmox::VE

Hi,
I'm recieving the following error when monitoring a qemu guest with a raw disk. This is because a zero value is returned for $item->{maxdisk} .
As a workaround to allow the script to run i've replace line

$mqemu->{curdisk} = sprintf("%.2f", $item->{disk} / $item->{maxdisk} * 100);

with

$mqemu->{curdisk} = "1";

Rgds
Ian

Bonjour, j'ai un problème de connexion au serveur proxmox :
Setting timeout to 5
Loaded node Proxmox
Loaded openvz example
Loaded openvz example-lxc-host
Loaded storage local
Loaded pool Sample
Loaded qemu Debian
Trying 192.168.0.11...
DEBUG: login not successful
DEBUG: 401 authentication failure
J'ai créer un user sous Proxmox avec les droits Admin que j'utilise dans le fichier de conf avec une connexion de type realm.
Mais toujours l'erreur de connection. J'aimerais essayer votre VE via github, mais je ne sais pas comment l'installer.

im Unable to get any informations about storage/openvz or qemu, but node works fine

i probobly choose a bad hostname.... it's called host

my perl is to poor to find the issue or how it's working :(

root@monitoring:/root/pve-monitor-stable-1.0 # ./pve-monitor.pl --storage --conf pve-monitor.conf --debug
Loaded node host
Loaded openvz proxy
Loaded qemu Router
Loaded storage local
Trying <address>
DEBUG: login successful
DEBUG: successful request: GET https://<address>:8006/api2/json/version
User-Agent: libwww-perl/6.05
Cookie: PVEAuthCookie=PVE:<user>@pam:5315E019::IzLhhBv/MNY8ufi7jv7Di/Qs9w5V5M8b+ySdoBhATBCmLdFHDxCgbOFMTZaZbJgJ9r+BuDB7XiWvaccyh0fEKZ/DPROoRoP0PlsXuH/pP3faffPyk9lmoM2QHNoS2y0t1C3SvzwA3xTpny8dJQHi2gnNH6G4T96CH73Jqe5btVlKGnGDak8PnMeVKAsoQBN6TixwZRo/svrmDYfjxAF7PCAmp8WstaWaB+P1b+wiiAM6OfFvNSI8kg2Cz28VdCAeJnTOu4/qE3zi+qzLmGsnChkWpaMqkOIfUyAST0AJjnpLnwioozWbX2ofKGvET7PRCfmaCLh1X+INYdqPDSoxvA==


Successfully connected to <address> !
DEBUG: successful request: GET https://<address>:8006/api2/json/cluster/resources
User-Agent: libwww-perl/6.05
Cookie: PVEAuthCookie=PVE:<user>@pam:5315E019::IzLhhBv/MNY8ufi7jv7Di/Qs9w5V5M8b+ySdoBhATBCmLdFHDxCgbOFMTZaZbJgJ9r+BuDB7XiWvaccyh0fEKZ/DPROoRoP0PlsXuH/pP3faffPyk9lmoM2QHNoS2y0t1C3SvzwA3xTpny8dJQHi2gnNH6G4T96CH73Jqe5btVlKGnGDak8PnMeVKAsoQBN6TixwZRo/svrmDYfjxAF7PCAmp8WstaWaB+P1b+wiiAM6OfFvNSI8kg2Cz28VdCAeJnTOu4/qE3zi+qzLmGsnChkWpaMqkOIfUyAST0AJjnpLnwioozWbX2ofKGvET7PRCfmaCLh1X+INYdqPDSoxvA==


Found 1 objects:
Found host in resource list
STORAGE CRITICAL 0 / 1 working storages
local (host) CRITICAL: storage is on a dead node

node host {
    address 10.10.10.10
    port 8006 # Optional, default is 8006
    monitor_account <user>
    monitor_password <password>
    realm pam # Optional, default is pam
    # test
    mem 80 90 # optional, not monitored if not defined
    cpu 80 95 # optional
    disk 80 90 # optional
}

# openvz example
openvz proxy {
    mem 80 90
    cpu 80 95
    disk 80 90
}

# qemu example
qemu Router {
    mem 80 90
    cpu 80 95
    disk 80 90
}

#storage example
storage local {
    disk 80 90
    node host
}

I tried to install the plugin and I get this error when run from console

perl /usr/lib/nagios/plugins/pve-monitor.pl --conf /etc/nagios3/pve-monitor.conf --nodes --debug
Loaded node proxmox1.XXXX.com
Loaded node proxmox2
Trying 192.168.1.201...
DEBUG: login not successful
DEBUG: 500 SSL negotiation failed:
Trying 192.168.1.202...
DEBUG: login not successful
DEBUG: 500 SSL negotiation failed:

This is the configuration file:

node proxmox1.XXXX.com {
address 192.168.1.201
port 8006 # Optional, default is 8006
monitor_account nagios
monitor_password XXXXXXX
realm pve # Optional, default is pam
mem 80 90 # optional, not monitored if not defined
cpu 80 95 # optional
disk 80 90 # optional
}

node proxmox2 {
address 192.168.1.202
port 8006 # Optional, default is 8006
monitor_account nagios
monitor_password XXXXXXX
realm pve # Optional, default is pam
mem 80 90 # optional, not monitored if not defined
cpu 80 95 # optional
disk 80 90 # optional
}

I have a Proxmox 3.3-5

thanks for your work!

Hello,

i have a problem with your script:

pve-monitor.conf looks like this:

node kvm {
    address 192.168.1.30
    port 8006
    monitor_account root
    monitor_password pass
    realm pam
    mem 80 90
    cpu 80 95
    disk 80 90
}

qemu Debian {
    mem 80 90
    cpu 80 95
    disk 80 90
}

storage local {
    disk 80 90
    node pyrit
}

I get the following output:

#./pve-monitor.pl --debug --singlenode --qemu --conf pve-monitor.conf
Loaded node kvm
Trying 192.168.1.30...
DEBUG: login successful
DEBUG: successful request: GET https://192.168.1.30:8006/api2/json/version
User-Agent: libwww-perl/6.04
Cookie: PVEAuthCookie=PVE:root@pam:5439783B::BnGPXDopM2ysaUXV+Nllq6zsvqYXVvx/IAOXN63qMsaBJMkOEr2oWB3YMnjWLXVqNaGLo+cuc397Qqq2h7TFcPjoXPAdP9MsBzC8WS/wDFKQ4WDg+8XgrR3CNNZ6yEf6zd6CwpLpJTOCjLlapdTs3dBlTUW8eNxWESO4Xj7uD4i/2EaCKH75ANkMZd1ypMf3TiS0JcB3odWhFz81doWF700lLmSRAdphJewjcdI9tVkGA4n6rdppvPbApUYFOlC9Ok9z1wdu/ZIR4lDYNuEB1uzWVjX9WHvlA8KgQsaMelIRAelGBj1d1dKEE1ThmVTs+nV3sBEFet9misXsRfYRgg==


Successfully connected to 192.168.1.30 !
Skipping cluster checks (--singlenode passed to command line)
Deep recursion on subroutine "Net::Proxmox::VE::get" at /usr/local/share/perl/5.20.1/Net/Proxmox/VE/Nodes.pm line 26.
Deep recursion on subroutine "Net::Proxmox::VE::Nodes::nodes" at /usr/local/share/perl/5.20.1/Net/Proxmox/VE.pm line 284.
Getötet

PVE Manager version 3.3-2/995e687e
Kernelversion Linux 2.6.32-33-pve

The server has 512 mb ram, normally 100 mb is used. If i execute the script it fills all the ram until it gets killed. I don't think this is normal behaviour. Can you please take a look? Thanks :)

Bonjour damien et merci pour ce plugin .
J'ai un soucis , lorsque je l'execute à la main il me répond parfaitement .
Par contre dans Shinken ou Thruk je n'arrive à avoir aucun résultat , a part toujours critique

Ex : ligne de commande
shinken:~/shinken/libexec# /usr/bin/perl /usr/local/shinken/libexec/pve-monitor.pl --conf /usr/local/shinken/etc/configs/cluster1.conf --qemu
QEMU OK 1 / 1 working VMs
shinken (sd-57902) OK : cpu OK (1.23%), mem OK (53.01%), disk OK (0.00%) uptime 75028

Avez vous quelqu'un qui le fait fonctionner sous shinken ( thruk ) ?

merci

adapt pve-monitor to pve4

Hello Everyone,
This is my first real swing at this. I got my config set for running the script/plugin:
./pve-monitor.pl --conf pve-monitor.conf --nodes
Could not connect to any server

Here is the top of the config file:
node pyrit { <- is this a host name or is pyrit a perl process?
address 10.x.x.xxx
port 8006 # Optional, default is 8006
monitor_account monitor@pve
monitor_password P@$$w0rd
realm pve # Optional, default is pam
mem 80 90 # optional, not monitored if not defined
cpu 80 95 # optional
disk 80 90 # optional
}

Just not sure where to look and fix this issue,
Thanks in advance for your help.
Michael

I have got an issue.
When I run the following command:
root@ubuntu:# perl pve-monitor.pl --nodes --conf /etc/nagios3/pve-monitor.conf
It shows that:
root@ubuntu:# Could not connect to any server !
My pve-monitor.conf file is:
node node1a {
address 192.168.102.1
port 8006 # Optional, default is 8006
monitor_account root
monitor_password super@dm!n
mem 80 90 # optional, not monitored if not defined
cpu 80 95 # optional
disk 80 90 # optional
}

Please help me to find out the problem.

Hi, I have a problem, when I run:
./check_pve_monitor.pl --conf ../etc/objects/pve-monitor.conf --node
NODES OK 1 / 1 working nodes
pve OK : cpu OK (0.01%), mem OK (27.23%), disk OK (10.39%) cpu alloc OK (12.50%), mem alloc OK (51.94%), uptime 94854
Its ok, but when I execute it from the nagios it returns this:
(No output on stdout) stderr: Can't locate Net/Proxmox/VE.pm in @inc (@inc contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/local/nagios/libexec/check_pve_monitor.pl line 36.

it is as if "Net::Proxmox::VE" is not installed and if it is installed, it can not be.
cpan install Net::Proxmox::VE
Loading internal null logger. Install Log::Log4perl for logging messages
Reading '/root/.cpan/Metadata'
Database was generated on Tue, 27 Mar 2018 12:41:03 GMT
Net::Proxmox::VE is up to date (0.33).

Sorry for the translation, I speak Spanish.

Hola, un problema, cuando ejecuto
./check_pve_monitor.pl --conf ../etc/objects/pve-monitor.conf --node
NODES OK 1 / 1 working nodes
pve OK : cpu OK (0.01%), mem OK (27.23%), disk OK (10.39%) cpu alloc OK (12.50%), mem alloc OK (51.94%), uptime 94854
todo bien, pero cuando lo ejecuto desde el nagios devuelve esto:
(No output on stdout) stderr: Can't locate Net/Proxmox/VE.pm in @inc (@inc contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/local/nagios/libexec/check_pve_monitor.pl line 36.

es como si no estuviese instalado "Net::Proxmox::VE" y si esta instalado, no se que puede ser.
cpan install Net::Proxmox::VE
Loading internal null logger. Install Log::Log4perl for logging messages
Reading '/root/.cpan/Metadata'
Database was generated on Tue, 27 Mar 2018 12:41:03 GMT
Net::Proxmox::VE is up to date (0.33).

Disculpa la traducción, hablo español.

Bonjour
j'ai deux soucis
si j'utilise la version 1.05

/usr/bin/perl /usr/local/nagios/libexec/pve-monitor.pl --conf /usr/local/nagios/libexec/pve-monitor.conf --nodes --debug

Setting timeout to 5
Loaded node amphiprion3
Loaded openvz example
Loaded qemu msvm
Loaded storage local
Loaded pool Sample
Trying 192.168.17.3...
DEBUG: login not successful
DEBUG: 401 authentication failure

node amphiprion3 {
address 192.168.17.3
port 8006 # Optional, default is 8006
monitor_account root
monitor_password XXXXXXXXXX
realm pve # Optional, default is pam
mem 80 90 # optional, not monitored if not defined
cpu 80 95 # optional
disk 80 90 # optional
}

soucis N° 2 si j'utilise la derriere version

Bareword found where operator expected at /usr/local/nagios/libexec/pve-monitor-1.4.pl line 5, near ""en" class"
(Missing operator before class?)
Bareword found where operator expected at /usr/local/nagios/libexec/pve-monitor-1.4.pl line 13, near "<title>pve"
(Missing operator before pve?)
Can't modify numeric lt (<) in scalar assignment at /usr/local/nagios/libexec/pve-monitor-1.4.pl line 5, near ""en" class"
syntax error at /usr/local/nagios/libexec/pve-monitor-1.4.pl line 5, near ""en" class"
Unrecognized character \xC2; marked by <-- HERE after at master <-- HERE near column 49 at /usr/local/nagios/libexec/pve-monitor-1.4.pl line 13.

des idées ??

On CentOS 6 is PVE-monitor is not working:
Starting pve-monitor 1.06
Setting timeout to 5
Loaded node <* not public >
Loaded qemu < not public >
Trying < not public >
DEBUG: login not successful
DEBUG: 500 Can't connect to < not public >:8006 (SSL connect attempt failed error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed)
Could not connect to anperl -MIO::Socket::SSL=debug4 pve-monitor.pl --conf pve-monitor.conf --nodes
DEBUG: .../IO/Socket/SSL.pm:2688: new ctx 36257920
DEBUG: .../IO/Socket/SSL.pm:605: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:607: socket connected
DEBUG: .../IO/Socket/SSL.pm:629: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:665: not using SNI because hostname is unknown
DEBUG: .../IO/Socket/SSL.pm:697: request OCSP stapling
DEBUG: .../IO/Socket/SSL.pm:729: call Net::SSLeay::connect
DEBUG: .../IO/Socket/SSL.pm:2589: did not get stapled OCSP response
DEBUG: .../IO/Socket/SSL.pm:2542: ok=0 [0] /CN=Proxmox Virtual Environment/OU=e6cfc5aec0801662e5d2af956214fc15/O=PVE Cluster Manager CA/OU=PVE Cluster Node/O=Proxmox Virtual Environment/CN=< not public *>
DEBUG: .../IO/Socket/SSL.pm:732: done Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:735: SSL connect attempt failed

DEBUG: .../IO/Socket/SSL.pm:735: local error: SSL connect attempt failed error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
DEBUG: .../IO/Socket/SSL.pm:738: fatal SSL error: SSL connect attempt failed error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
DEBUG: ...erl5/Net/HTTPS.pm:47: ignoring less severe local error 'IO::Socket::INET configuration failed', keep 'SSL connect attempt failed error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed'
DEBUG: .../IO/Socket/SSL.pm:2721: free ctx 36257920 open=36257920
DEBUG: .../IO/Socket/SSL.pm:2726: free ctx 36257920 callback
DEBUG: .../IO/Socket/SSL.pm:2733: OK free ctx 36257920

[root@nagios libexec]# cpan Net::Proxmox::VE
CPAN: Storable loaded ok (v2.20)
Going to read '/root/.cpan/Metadata'
Database was generated on Mon, 30 Nov 2015 11:41:02 GMT
Net::Proxmox::VE is up to date (0.009).

[root@nagios libexec]# cpan IO::Socket::SSL
CPAN: Storable loaded ok (v2.20)
Going to read '/root/.cpan/Metadata'
Database was generated on Mon, 30 Nov 2015 11:41:02 GMT
IO::Socket::SSL is up to date (2.020).

Am I doing something wrong? Nmap port 8006 is up and pve is reachable via browser.

I've set up a config file almost exactly as the given sample:

#define nodes
    node farm4 {
        address 192.168.178.6
        port 8006 # Optional, default is 8006
        monitor_account root
        monitor_password pass
    #    realm pve # Optional, default is pam
        mem 80 90 # optional, not monitored if not defined
        cpu 80 95 # optional
        disk 80 90 # optional
    }

    node farm5 {
        address 192.168.178.7
        port 8006 # Optional, default is 8006
        monitor_account root
        monitor_password pass
    #    realm pve # Optional, default is pam
        mem 80 90 # optional, not monitored if not defined
        cpu 80 95 # optional
        disk 80 90 # optional
    }

    node farm5 {
        address 192.168.178.8
        port 8006 # Optional, default is 8006
        monitor_account root
        monitor_password pass
    #    realm pve # Optional, default is pam
        mem 80 90 # optional, not monitored if not defined
        cpu 80 95 # optional
        disk 80 90 # optional
    }

It works fine when running pve-monitor from the command line:

root@proxmox-monitoring:/usr/lib/nagios/plugins# ./pve-monitor.pl --conf /usr/local/nagios/etc/configs/pve-monitor.cfg --nodes
NODES OK  3 / 3 working nodes
NODE farm4 OK : cpu OK (0.88%), mem OK (40.47%), disk OK (2.47%) uptime 145405
NODE farm5 OK : cpu OK (0.02%), mem OK (2.85%), disk OK (1.05%) uptime 78381
NODE farm5 OK : cpu OK (0.02%), mem OK (2.85%), disk OK (1.05%) uptime 78381

However, running /etc/init.d/nagios start fails with this error:

Error: Unexpected token or statement in file '/usr/local/nagios/etc/configs/pve-monitor.cfg' on line 2.

Thanks for all help.

Hey,

i became an error running against proxmox 3.0.

my config file

 node proxmox01-slave {
    address 10.96.0.35
    port 8006 # Optional, default is 8006
    monitor_account root
    monitor_password XXXX
    mem 80 90 # optional, not monitored if not defined
    cpu 80 95 # optional
    disk 80 90 # optional
 }

output

 root@proxmox-slave02:~/pve-monitor-stable-1.0# perl ./pve-monitor.pl --conf pve-monitor.conf --nodes
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 706.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 711.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 716.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 721.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 726.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 731.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 706.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 711.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 716.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 721.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 726.
 Use of uninitialized value in numeric gt (>) at ./pve-monitor.pl line 731.

I tried to use the plugin directly from the shell on a CentOS 5 server and i got the following message.

Can't use an undefined value as a HASH reference at /usr/lib/perl5/5.8.8/Net/Proxmox/VE.pm line 367.

'timeout|t' => $arguments{timeout}, should be 'timeout|t=s' => $arguments{timeout}, or timeout is set to 1 if set in arguments !

Hello ! Here's my pve-monitor.conf;

Example Cluster definition

node example

node srv02 {
address 192.168.128.12
port 8006 # Optional, default is 8006
monitor_account root
monitor_password potato
realm pam # Optional, default is pve
# test
mem 80 90 # optional, not monitored if not defined
cpu 80 95 # optional
disk 80 90 # optional
}

openvz example

openvz example {
mem 80 90
cpu 80 95
disk 80 90
}

qemu example

qemu msvm {
mem 80 90
cpu 80 95
disk 80 90
}

storage example

storage local {
disk 80 90
node srv02
}

from debian jessie box (192.168.128.210) i can ping and telnet on 8006 192.168.128.12 but when i run any command from: /usr/bin/perl pve-monitor.pl --conf /etc/nagios3/pve-monitor.conf i always obtain "Could not connect to any server !" Thanks to help

Hello Guys,

Not sure this is the right place for this, However I am trying to install the pve-monitor in my nagios and the installation is not clear on where and what is suppose to be installed

1 - Install needed software - Is this on the nagios server or the client server or on both
2 - On nagios server or client server or both?
3 - I am going to assume this is on the nagios server

Thank you in advance for your assistance.

Hi,
Thank you for your good job.
I have a problem with status qemu disk.
This is my pve-monitor.conf:
....
qemu server-01 {
mem 80 90
cpu 80 95
disk 80 90
}
....
and the result:
server-01 OK : cpu OK (0.04%), mem OK (25.52%), disk OK (0.00%) uptime 5114
The disk information is not correct.

On the server local, result df:
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 22G 8.0G 13G 39% /

I don't have the problem for lxc, container or others just qemu.
Can you help me for this?
Thank you.
Best regards,
Nicolas

Hi,
Thanks for taking the time to write this excellent plugin. I have started to use it with Icinga . I encountered an issue when monitoring my qemu guests. They all report that their status was UNKNOWN .
To resolve this i added the following line at #666

$mqemu->{status} = $status{OK};

Rgds
Ian