Internal documentation only
This page has been marked as draft.
CHECK_VMWARE UNKNOWN
Related to Copied
[ERROR] 500 error: Failed to connect to vSphere: [errno 16] Device or resoruce busy
OSError: [Errno 16] Device or resource busy OSError: [Errno 24] Too many open files
Problem Copied
The check_vmware service check fails and in the OP5 GUI the following message is disaplyed:
“CHECK_VMWARE UNKNOWN - Service error: Failed to connect to vSphere: [errno 16] Device or resoruce busy”
The following messages may also be apparent in /var/log/massages.
OSError: [Errno 16] Device or resource busy.
OSError: [Errno 24] Too many open files
Possible cause(s) Copied
The error message “Too many open files” suggests that there are too many open connections.
This can be caused by the check_vmware service opening too many connections.
The number of connections that are allowed for a process is determined, and can be limited by the operating system and that is something that must be checked.
Possible solution(s) Copied
You can you check what limits are set on the OP5 system by running the following command:
ulimit -a
Typical output will imnclude a line similar to below:
open files (-n) 1024
You can create an override to allow check_vmware to open more files (connections) by creating a systemd override file. e.g. Run the following command:
# systemctl edit check_vmware.service
This will open a new file in the system editor and you can then add the following and save:
[Service]
LimitNOFILE=4096
You should then restart the service as follows:
systemctl restart check_vmware.service