Known Issues

PNP graph icons missing after upgrade to Monitor 6.1

In some cases the graph icons for hosts and services can disappear in the list views. To correct this, edit /opt/monitor/etc/nagios.cfg and change the line saying: broker_module=/usr/libexec/livestatus/livestatus.o /opt/monitor/var/rw/live to: broker_module=/usr/libexec/livestatus/livestatus.o pnp_path=/opt/monitor/op5/pnp/perfdata /opt/monitor/var/rw/live Then restart monitor: # mon restart

Business Services configuration files

When upgrading or re-installing op5 Monitor prior to version 6.1, local configuration is overwritten. To restore the local configuration, replace /opt/monitor/etc/synergy/services.cfg with a recent backup copy. Starting with op5 Monitor 6.1, the local configuration is not overwritten. Instead, the new configuration is available as services.cfg.rpmnew. To utilize the new default configuration, services.cfg.rpmnew must be manually merged with services.cfg.

Logserver installation problems

When installing op5 Logserver on a machine that has been updated with packages newer than what was available when Logserver was released, the installation script might run into conflicts. To work around this problem, remove the offending package from the rpm directory and re-run the installation.

Monitor does not work after upgrading from 5.8.0 to 6.0.x

Upgrading from 5.8 to 6.0.x is not supported. Customers planning to upgrade will need to wait for Monitor 6.1 which is planned for release 2013-05-14.

NRPE checks fails after update

We have a small issue with the latest NRPE package where nrpe.conf isn’t marked as a configuration file, resulting in the original /etc/nrpe.conf being renamed to /etc/nrpe.conf.rpmsave resulting in a default config with allowed_hosts=127.0.0.1. To get back the original one, and allow checks to be perfomed again, simply run the following commands as root on

Unable to install Monitor on CentOS/RHEL 6.4

There are some PHP-packages that conflict with packages delivered in the tarballs. A quick work-around is to delete the conflicting (older-version) rpm’s in the installation directory, and then manually install these before proceeding with the installation. 1) cd op5-monitor-x.x.x/rpm 2) rm -f php-5.3.3* php-cli-5.3.3* php-common-5.3.3* php-gd-5.3.3* php-ldap-5.3.3* php-mbstring-5.3.3* php-mysql-5.3.3* php-pdo-5.3.3* php-process-5.3.3* php-snmp-5.3.3* php-xml-5.3.3* 3) yum install php-gd

No SMS notifications after upgrade to Monitor 6

If you experience issues with SMS notifications not going out as they should after an upgrade from Monitor 5 to Monitor 6, please run the following commands as root: yum reinstall smstools usermod -a -G smstools monitor ln -s /usr/bin/smssend /usr/bin/sendsms service smsd restart

Security vulnerabilities in op5 Monitor

Security vulnerabilities published at http://packetstormsecurity.org/files/115850/op5-xssxsrfsql.txt Last week there were 3 different kinds of vulnerabilities reported for op5 Monitor 5.4.2. Please note that all of the reported issues (except 2B) are solved in op5 Monitor 5.7.3.  We can, however, confirm that similar issues are still present but these will be addressed as described below. Because of this, we