Related to:

Upgrading. Self-monitoring. Variable Character length. OP-65414.

Problem

A Variable limit of 64 characters is stopping the playbook "setup-monitoring.yml" from successfully completing.

Error

Opsview: "Error trying to synchronise object"
To include error detail in API responses, set 'ControllerBase::REST: {include_error_detail: 1}' in opsview_web_local.yml 

When the API setting is then added, the error is shown with: 

"Failed maximum length 64 on 'value;"

Validation

Run the below on the Linux server in question and review the output provided for DISK

df -kh
fdisk -l

Example output:

Filesystem Size Used Avail Use% Mounted on
/dev/dm-10 40G 10G 25G 75% /var/lib/docker/devicemapper/mnt/8vsvsv5e27c57ee3sdfvrt5cb3069b3f73ervdfv85bcfc54ea4ef7672436665d0f4f


DISK dev/mapper/docker-119:4-45322225-8vsvsv5e27c57ee3sdfvrt5cb3069b3f73ervdfv85bcfc54ea4ef7672436665d0f4f:
Units = sectors of 1 * 512 = 512 bytes 
Sector size (logical/physical): 512 bytes / 512 bytes 
I/O size (minimum/optimal): 512 bytes / 512 bytes

Workaround(s)

• This is related to bug OP-65414 and currently does not have a fix within the product
• Update two yaml files to ignore the variable that is having the issue, using the attached tar file.
  
  • After that is complete, re-run/attempt your upgrade
  • You will need to monitor/ensure the DISK path you encountered an issue for is monitored

1. Place the tar file on your deployment server
2. Backup the files to be overwritten
cp -p /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/_update_existing_host.yml /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/_update_existing_host.yml.backup
cp -p /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/_create_new_host.yml /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/_create_new_host.yml.backup

3. Untar the tarball with the command below, updating it to your path of where the you have placed it
tar -zxvf </path/to/tar/OP-65414.tar.gz> -C /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks

4. The permissions should be correct, but ensure the two new files match the below an update if not.
# ls -l /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/{_create_new_host.yml,_update_existing_host.yml}
-rw-r--r-- 1 root root 1770 Nov 27 11:44 /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/_create_new_host.yml
-rw-r--r-- 1 root root 2669 Nov 27 11:44 /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/_update_existing_host.yml

If needed:
# chown root.root /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/{_create_new_host.yml,_update_existing_host.yml}
# chmod 644 /opt/opsview/deploy/lib/roles/opsview_monitoring/tasks/{_create_new_host.yml,_update_existing_host.yml}

If Issue Persists

• Please contact with our Client Services team via the chat service box available in any of our websites or via email to support@itrsgroup.com
  
  
  
• Make sure you provide to us:

- ANY LOG FILE OR DIAGNOSTIC

- ANY SCREENSHOT

- ANY VENDOR/VERSION OF WHAT THEY ARE TRYING TO CONNECT TO

-Any troubleshooting step already verified from the ones described in this article.