Opsview 6.x Known Issues

Overview Copied

Opsview Monitor known issues contain a list of bugs and issues that may affect the performance of your applications and components.


These known issues apply to both Opsview Monitor 6.x and Opsview Cloud version, except that Ubuntu 18 is only applicable in Opsview Monitor 6.x.

OS Specific Copied

Ubuntu 18 Copied

This known issue is only applicable to Opsview Monitor 6.x.

Email notifications will cease to work and need a new package installed Copied

In Ubuntu 18, the notify_by_email Notification Method will fail to work due to /usr/bin/mail being deprecated and replaced with /usr/bin/s-nail.

Installing bsd-mailx resolves the issue.

apt install bsd-mailx

Ubuntu 20 Copied

Re-enabling TLS 1.0 and TLS 1.1 Copied

Ubuntu 20 ships by default with TLS 1.0 and TLS 1.1 disabled. This means you may get errors when any OpenSSL libraries try to connect to external services.

Ideally, the external service should be upgraded to support TLS 1.2, but if that is not possible, then you can re-enable TLS 1.0 and TLS 1.1.


Warning: By doing this, you are reducing security.

To test the external service:

openssl s_client -connect SERVER:443 -tls1_2

This will fail if the external service does not support TLS 1.2.

To allow Ubuntu 20 to use TLS 1.0, edit /etc/ssl/openssl.cnf and add this at the top:

openssl_conf = openssl_configuration

Then add this at the bottom:

ssl_conf = ssl_configuration
system_default = tls_system_default
MinProtocol = TLSv1
CipherString = DEFAULT:@SECLEVEL=1

Now, check that connections will work.

Non-RHEL 8 Copied

SNMP Polling Copied

SNMP Polling Checks do not support the aes256 and aes256c SNMPv3 privacy protocols when run on non-RHEL8 collectors. You may see an UNKNOWN state and an error message starting with the following if this is attempted:

External command error: Invalid privacy protocol specified after -x flag: aes256


External command error: Invalid privacy protocol specified after -x flag: aes256c

See SNMP Privacy Protocol Support for further details.

SNMP Traps Copied

SNMP Traps being sent using the aes256 and aes256c SNMPv3 privacy protocol options will not appear if received by non-RHEL8 collectors.

Older operating systems Copied

On CentOS 7, OEL 7, and RHEL 7 Copied

OS Generic Copied

UI Copied

Upgrade and installation Copied

# If you use ansible_ssh_private_key_file on the opsview_deploy.yml file

        user: ec2-user  
          ansible_ssh_private_key_file: /home/ec2-user/.ssh/ec2_key
        user: ec2-user  
          ansible_ssh_private_key_file: /home/ec2-user/.ssh/ec2_key

# You need to add the following entries to /root/.ssh/config

Host ip-172-31-9-216
    User ec2-user
    IdentityFile /home/ec2-user/.ssh/ec2_key
Host ip-172-31-5-98
    User ec2-user
    IdentityFile /home/ec2-user/.ssh/ec2_key

Plugins Copied

Modules support Copied

SMS Gateway is not available in this release. If you rely on this method, please contact ITRS Support.

Databases Copied

MySQL RPM Repository Key Copied

The MySQL RPM Repository Key stored within the product has expired. This has been fixed in a later version of Opsview Monitor, but it can be amended locally without upgrading.

For APT based systems, edit /opt/opsview/deploy/lib/roles/opsview_database/vars/apt.yml on the Orchestrator, search for the line repo_key_id and amend as follows:

    repo_key_id: 3A79BD29

For RPMO based systems, edit /opt/opsview/deploy/lib/roles/opsview_database/vars/yum.yml on the Orchestrator, search for the line repo_key_id and amend as follows:

    gpgkey: http://repo.mysql.com/RPM-GPG-KEY-mysql-2022


REST API config/OBJECT list calls: The ordering of results when using MySQL 8 is not necessarily deterministic, so REST API calls may need to specify a subsort field. For example, for hosts, order=hostgroup.name is not sufficiently deterministic and will need to be order=hostgroup.name,id so that the results come back in a fixed order.

Other issues Copied

Autodiscovery Copied

AutoMonitor Copied

Opspacks Copied

# as root
wget https://community.cisco.com/kxiwq67737/attachments/kxiwq67737/4354j-docs-cisco-dev-ucs-integ/862/1/UcsSdk-0.8.3.tar.gz
tar zxfv UcsSdk-0.8.3.tar.gz
cd UcsSdk-0.8.3
sudo python setup.py install

Character support Copied

SNMP Traps Copied

SNMPTraps daemons are started on all nodes within a cluster. At start-up a master SNMP trap node is selected and is the only one in a cluster to receive and process traps. Other nodes silently drop traps.

The majority of SNMPTrap sending devices can at most send to 2 different devices.

The current fix is to manually pick two nodes in a given cluster to act as the SNMP trap and standby node. Then mark all other nodes within the cluster to not have the trap daemons installed, for example:

  Trap Cluster:
      traptest-col01: { ip:,  ssh_user: centos }
      traptest-col02: { ip:, ssh_user: centos }
      traptest-col03: { ip:, ssh_user: centos, vars: { opsview_collector_enable_snmp: False } }
      traptest-col04: { ip:,  ssh_user: centos, vars: { opsview_collector_enable_snmp: False } }
        ssh_user: centos
          opsview_collector_enable_snmp: False

On a fresh installation the daemons will not be installed.

On an existing installation the trap packages must be removed and the trap demons on the 2 active nodes restarted to re-elect the master trap node:

CentOS/RHEL: yum remove opsview-snmptraps-base opsview-snmptraps-collector
Ubuntu/Debian: apt-get remove opsview-snmptraps-base opsview-snmptraps-collector

/opt/opsview/watchdog/bin/opsview-monit restart opsview-snmptrapscollector
/opt/opsview/watchdog/bin/opsview-monit restart opsview-snmptraps

Opsview Reporting Module Copied

On upgrade to the latest version of Reporting Module, email settings will need to be reapplied.

Email configuration can be found in the file: /opt/opsview/jasper/apache-tomcat/webapps/jasperserver/WEB-INF/js.quartz.properties.

To configure email, edit the following lines in the configuration to match your required configuration.

Example configuration for internal email:


Example configuration for SNMP relay:


To apply changes, you will need to restart opsview-reportingmodule:

/opt/opsview/watchdog/bin/opsview-monit restart opsview-reportingmodule

Apache Log4Shell Vulnerabilities Copied

All listed Log4j vulnerabilities are resolved in Opsview.

["Opsview On-premises"] ["Release Notes", "Compatibility Matrix"]

Was this topic helpful?