'Unclosed compound' error in naemon.log
The 'Unclosed compound' error in naemon.log indicates configuration issues in merlin.conf. The resolution involves locating missing closing braces, correcting the file, and restarting the monitoring service.
The 'Unclosed compound' error in naemon.log indicates configuration issues in merlin.conf. The resolution involves locating missing closing braces, correcting the file, and restarting the monitoring service.
Event cancellation by IO broker input can stop checks from running in Naemon. Verify time periods, remove exclusions, ensure active pollers, and test enabling or disabling checks in the web GUI.
Business service management (BSM) connects IT operations with business impact by mapping IT services and their dependencies. This guide explains how to create BSM logic, build rule sets, and visualize services using existing monitoring metrics in OP5.
A specific service in OP5 Monitor may stop performing checks or return incorrect output due to configuration changes, upgrades, or communication issues with monitoring agents. Troubleshooting involves verifying service configurations, core service statuses, monitoring agent settings, and custom plugin availability.
Sharing a dashboard in OP5 requires filters to be set as global; user-specific filters will prevent the dashboard from loading for others. To share filters, edit them in the Filter Builder and enable the global checkbox before sharing the dashboard.
Removing a peer node can cause Poller nodes to become INACTIVE in the OP5 cluster. To fix this, remove the deleted peer from the Poller's configuration to restore node activity.
OP5 Monitor HTTP API creates object entries in etc/timeperiods.cfg instead of the specified file. Ensure the API user has FILE permissions enabled in Group Rights under Manage > Configure > Group rights.
API queries for objects containing a slash may result in errors when the slash is not properly encoded. The solution is to double url-encode the slash by using "%252F" instead of a single "%2F" in the query URL.
RRD graphs in OP5 can change axis units automatically when data exceeds previous limits, such as switching to Terabytes for disk usage over 1 TB. This behavior is expected and results from PNP4Nagios and RRDTool, which generate the graphs.
Monitoring Microsoft Biztalk environments involves tracking ports, queues, orchestrations, and host instances using the check\biztalk plugin. The guide provides command definitions and examples for monitoring key Biztalk components and performance counters with NSClient++ and check\nrpe.
The check_nt plugin in OP5 cannot monitor disk space using absolute units like Gb or Tb, only percentages. To monitor disk space in absolute units, use a wrapper script or switch to the check_nrpe plugin.
Running OP5 Monitor in a virtual environment is supported but may cause timing inaccuracies and hardware access challenges. The guidance explains potential pitfalls and suggests using physical machines if performance or reliability issues arise.
Security scanners may report outdated software versions and vulnerabilities incorrectly on CentOS and RHEL systems due to RedHat's backporting of security fixes. Running the latest RedHat packages for your supported OS version generally ensures security despite scanner warnings.
Certificate based authentication between check_nrpe and NSClient++ secures communication using client and server certificates verified against a CA certificate. The setup involves configuring verify mode in NSClient++ and using appropriate certificate options with check_nrpe for one-way or mutual authentication.
Certificate management for LDAP SSL with Active Directory involves installing AD CS and handling certificates for secure authentication. The process includes exporting the public certificate from Windows and importing it into OP5 Monitor to enable certificate verification.
OP5 users cannot change the UI timezone from UTC when setting maintenance mode on hostgroups. Time values are based on server timezone settings and cannot be altered in the current design.
Changing the ITRS OP5 Monitor images on the login page and GUI allows rebranding with a company logo. This is done by replacing specific image files in the brands directories, but changes revert after OP5 upgrades.
The check_traffic plugin in OP5 monitors network traffic and error rates on specified interfaces using SNMP and configurable thresholds. The FAQ provides detailed command examples and options for Windows and Linux to customize monitoring parameters and security settings.
CHECK_VMWARE UNKNOWN occurs when the check\vmware service fails to connect to vSphere due to resource limits. Increasing the allowed number of open files via a systemd override resolves connection errors and service failures.
OP5 nodes running different versions, including minor releases, are not compatible within the same cluster and may cause communication failures. All nodes must run the exact same OP5 and Merlin versions to ensure cluster stability and functionality.
Configuration changes in OP5 cannot be saved due to issues like incorrect file permissions, invalid configurations, database locks, or duplicate entries. The resolution involves verifying permissions, validating configuration files, clearing database locks, and removing duplicates before re-importing and restarting services.
Configuring a specific poller for hostgroups allows targeted polling of hosts from designated pollers in OP5. This is done by creating a hostgroup, assigning hosts, modifying the merlin.conf file on masters, and restarting the masters.
Configuring NSClient++ from the Windows command prompt involves using the nscp command to view and change settings, manage modules, and control logging. After making changes, you must restart the NSClient++ service to apply the new configuration.
Configuring the NagVis automap addresses visualization challenges in large OP5 Monitor environments with many host relationships. Adjusting the render mode to unidirect2 improves map clarity and spacing for better readability.
Creating a list view filter query allows you to display a specific subset of objects based on criteria like name, group membership, or state. The documentation provides guidance on constructing queries to filter list views effectively.
Creating command-line tools using the OP5 Monitor HTTP API enables remote command execution. The guide provides PHP script examples for submitting passive check results and building reusable API-driven tools.
Changing ownership of a dashboard in OP5 Monitor requires modifying the database directly, as no in-product option exists. The process involves backing up the dashboards table, identifying the dashboard ID, and updating the owner value with SQL queries.
Copying dashboards between users in OP5 Monitor requires removing the target user's existing dashboard first. A custom script helps automate copying and deleting dashboards after upgrading to version 7.2.6.
Database maintenance in OP5 involves purging old data from the MySQL database to reduce its size. Use the mon log purge command with the --remove-older-than option to delete log files and database entries older than a specified time period.
Disabling configuration changes on a Monitor node hides the "Configure" menu in the web GUI and prevents GUI-based edits. The API can also be disabled by invalidating authentication, which blocks all API calls including configuration commits.
The Merlin project enables distributed Nagios installations by allowing direct information exchange between Nagios processes. It functions as a backend for the Ninja GUI, storing status data in a database and providing fault tolerance.
Downgrading OP5 versions is not safe or recommended due to lack of proper downgrade procedures and potential environment issues. The FAQ explains that backups are essential before upgrading and manual restoration is complex and unreliable.
Duplicate notifications in OP5 often occur due to misconfiguration in the merlin.conf file on Master or Poller nodes. The solution involves setting notifies = no in the Poller configuration blocks and restarting the monitoring service.
Enabling and disabling SMS or email notifications for multiple OP5 users on vacation cannot be done in bulk. Notifications must be managed individually for each user using the standard enable/disable process.
Enabling debug logging for Business Services in Synergy helps troubleshoot service issues. To do this, set debug to true in config.lua, restart the synergy service, and check logs in syslog or journalctl.
The ERROR: Unused Arguments message can appear when rendering RRD graphs from the check\mssql\health command. Removing the trailing comma in the specified file line or checking for extra colons in rrdtool output may resolve the issue.
Estimating necessary bandwidth in an OP5 Monitor cluster depends on the number of checks and intervals. Bandwidth needs vary, with about 0.26 to 0.36 Mbit/s per 1,000 checks as a conservative estimate.
Executing PowerShell scripts via the op5 Agent involves creating a script, configuring the agent, and adjusting PowerShell execution policies. The process includes testing the script from the op5 Monitor console and adding it as a service check on a host.
Fetching perfdata via the API can fail with a ‘DS does not exist’ error. Ensure the API endpoint specifies the correct datasource and the RRD Storage Type is set to MULTIPLE.
Corrupted tables in MySQL/MariaDB can cause errors and instability in OP5 features. Repairing the tables using mysqlcheck and restarting Monitor services resolves these issues.
OP5 Monitor stores personally identifiable information in user accounts, contacts, log files, and databases. This includes names, email addresses, phone numbers, and login details found in specific system and backup locations.
Getting started with OP5 Monitor covers installation, license details, and initial configuration steps. It explains how to install OP5 Monitor on software or cloud servers and how to add hosts using the Host Configuration Wizard.
Graphing total acknowledged and unacknowledged services in op5 Monitor helps track incident handling over time. The process involves creating a custom plugin, check command, and PNP template for improved graph visualization.
Adding new graph templates in OP5 Monitor allows visualization of performance data from check plugins. The process involves creating a PHP template file that defines graph options and data series for clearer, customized performance graphs.
The OP5 GUI may show an error and lock up even when the license is still valid. Restarting the php-fpm service usually resolves the issue, and if not, contacting ITRS support for a new license file is recommended.
OP5 GUI/UI may become unresponsive or slow due to high disk I/O, CPU, or memory usage and insufficient hardware resources. Troubleshooting involves checking system resource usage, restarting related services, and upgrading hardware or contacting support if needed.
The handler receives interface up/down SNMP traps from HP ProCurve switches in OP5 Trapper version 2.1. It provides a demo script for monitoring link status changes but is unsupported by ITRS support.
Hardware support for OP5 Monitor Appliances is provided directly by Dell for warranty-covered components. Customers should prepare specific information and contact Dell for hardware replacement or support issues.
Unix timestamps in nagios.log can be converted to human-readable formats using a perl oneliner. A bash function with PHP code offers sortable output and time zone display for easier analysis.
Installing the check_linux_stats plugin on Debian or Ubuntu requires specific dependency packages. After installing dependencies, copy the plugin to /usr/lib/nagios/plugins and configure commands for execution via the NRPE agent.
Monitoring all Microsoft Windows services in automatic mode uses the check_nrpe_win_services command with the CheckAll argument. You can exclude specific services from the check by adding an exclude parameter to the command.
Performing HTTPS checks against websites using NTLM authentication is not supported by default in OP5 Monitor plugins. A third-party Nagios Exchange plugin using a curl wrapper can handle NTLM authentication, but it is unsupported and may not be fully compatible.
You can view your OP5 Monitor license details and validity through the web UI or command line. The OP5 License Inspector tool helps inspect license files without installing them on the server.
Dell Openmanage can be completely uninstalled from an Appliance Server by removing all related packages. This involves erasing srvadmin packages and deleting the Dell repository file from the system.
The hostname in OP5 Monitor e-mail notification links defaults to the monitoring server's hostname. You can change it by creating a notify configuration file and setting the hostname property.
Integrating op5 Monitor authentication with Microsoft Active Directory enables centralized user management. The integration process and detailed instructions are provided in the Active Directory Integration how-to article.
Monitoring Microsoft Windows performance counters with op5 Monitor involves collecting and graphing specific system metrics. The process is detailed in the Monitoring and graphing Windows performance counters guide.
OP5 Monitor is affected by Microsoft's default hardening of DCOM servers starting March 14, 2023. OP5 Monitor version 8.4 and later include updates to check\wmi\plus to address these WMI/DCOM security changes.
Performance data from check plugins is processed through naemon configuration and stored in perfdata files. These files are then handled by npcd and process_perfdata.pl to update RRD files, which generate graph data in op5 Monitor.
ist-collect gathers logs, configuration files, and system data from nodes for support analysis. It uses modules to select files, performs file discovery, and collects data with options to include sensitive files or specify modules.
Group rights in OP5 Monitor define user permissions based on group membership for accessing system, host, service, and API functions. The documentation details specific permission categories and their meanings to clarify user capabilities within the product.
Adding a .lic license file to OP5 Monitor involves copying and installing the license on the server. The process includes setting correct permissions and verifying the license, with special steps for multi-node environments.
Adding a host and service in OP5 Monitor can be automated using a Perl script with the HTTP API and LWP. The example script demonstrates creating a host, adding a service, and saving the configuration programmatically.
Service dependencies in OP5 allow you to link one service's status to another to avoid redundant alerts. You can configure dependencies by selecting the host and service, setting the dependency criteria, and saving the changes carefully.
Adding a user with limited visibility in OP5 Monitor involves assigning them to predefined groups with restricted permissions. The process includes creating a contact, assigning group membership, linking the user to specific hosts, and optionally limiting accessible menu items.
Environment variables for naemon check_commands in OP5 Monitor are limited due to non-login session execution. You can add variables by defining them in the monitor.service file and then reloading and restarting the service.
Adding hosts in OP5 Monitor can be done using the REST API with a CSV input file. The provided sample script demonstrates this process at a proof of concept level and includes example files for formatting guidance.
Adding new hosts involves including servers, network devices, or other devices for monitoring in OP5. The process includes scanning the network or using a management pack to apply checks to the new device.
Adding new services to an existing host object allows monitoring of additional metrics like CPU or disk. Services can be tied to host groups for reuse or added individually to specific hosts as needed.
Adding or renewing an SSL certificate for OP5 Monitor ensures secure, verified connections without browser errors. The process involves creating a CSR, obtaining a CA-signed certificate, and configuring Apache on the Monitor server.
Adding PNP graphs to the OP5 dashboard requires creating a NagVis map with graph objects. After creating the map, add it as a NagVis widget on the dashboard to display the PNP graphs.
Scheduled downtimes can be added manually or via cron using external commands in OP5. This process involves sending specific command strings to the monitor user and can be automated with cron jobs for repeated downtimes.
Adding Selenium tests to op5 Monitor automates web application testing using Firefox and Xvfb in a headless environment. The process involves installing required packages, configuring the selenium plugin, creating test cases, and setting up commands and services in op5 Monitor.
Adjusting rrdcached options can help improve IO performance when monitoring many services in OP5. You need to edit the rrdcached.service file and restart rrdcached to apply the changes.
The mon command can be run with root privileges using sudo by configuring user permissions. Adding users to the mon\operators group allows limited mon command access, while full system administrator rights enable broader command use.
Sysload issues with high runq-sz and iops/tps values indicate potential CPU or disk bottlenecks. The guidance explains how to interpret these metrics and identify if the system is CPU-bound or experiencing heavy disk transfers.
Automatically deleting old backup files prevents disk space from filling up and avoids errors or crashes in OP5 Monitor. This FAQ provides a cronjob command to delete backup files older than 7 days and guidance on managing backup directories.
Changing the root password is necessary to access the OP5 Portal when deploying OP5 Monitor in Azure. This guide explains how to SSH into the system and update the root password for portal login.
Scheduled reports in OP5 are sent from a default email address that may cause delivery issues. You can change the sender address by editing reports.php or configuring Postfix to rewrite the sender address.
The Status URL in outgoing notifications can be changed by editing the notify.yml file. Add the host name in the /etc/op5/notify.yml configuration to update the URL.
Changing the behavior of a check_command involves editing or copying an existing command to modify its options or arguments. The process includes creating a new command based on the original, updating its command line, and applying it to relevant services.
Checking host availability via a custom TCP port is possible when ICMP ping is not reachable. You can change the host check command to a predefined or custom TCP port check plugin in the host's advanced configuration.
Check the VMware Perl SDK version running on OP5 Monitor using a specific command. The command provides the exact SDK version installed on the system for verification.
Cloning multiple dashboards to another user in OP5 Monitor requires using a specific Python script. The provided script works with OP5 Monitor 7.2.7 and Python 2.7 but is not officially supported by ITRS.
Collecting files and system information for OP5 support ticket submission is done using the ist-collect tool. This tool automates gathering relevant files and command outputs into an archive for easy submission and troubleshooting.
Configuring 802.1q VLAN in OP5 Monitor segments network traffic to improve monitoring efficiency. The process involves creating VLAN interface files and adjusting network settings on CentOS 7.
Configuring a passive poller behind NAT allows monitoring without port forwarding. The setup involves editing host files, adjusting merlin.conf, and ensuring SSH connectivity between master and poller.
Configuring a Linux server for SNMP monitoring requires setting up the SNMP daemon properly. This guide explains how to add SNMPv3 users, secure access, and verify configuration for op5 Monitor.
Configuring geomap to use OpenStreetMap requires setting the localMapsUrl to a tile server URL. This can be done via the web UI or by editing the settings file, then reloading the geomap page without restarting.
Configuring monitoring objects in OP5 Monitor is done through the REST API using HTTP requests like GET, POST, and PATCH. The API allows adding, changing, viewing, and deleting hosts, services, groups, templates, and contacts with commands demonstrated using curl.
Configuring NSClient++ settings in the Windows Registry involves editing keys under HKEY_LOCAL_MACHINE\SOFTWARE\NSClient++. This includes managing allowed hosts, logging, modules, and external scripts, with changes requiring a service restart to take effect.
Configuring OP5 Trapper Extension enables handling Cisco device traps as passive results in op5 Monitor. The process involves creating handlers, binding trap OIDs, and verifying trap processing and severity mapping in Monitor.
Configuring SELinux enforcing mode for OP5 Monitor involves enabling SELinux and adjusting permissions for required services. The guide provides commands and a script to allow necessary features, ensuring OP5 Monitor runs properly with SELinux enforcing.
Configuring separate storage for RRD graph data with RRDCached can fail if the base directory uses symbolic links. The solution is to avoid symbolic links by using a bind mount for the base directory to ensure RRDCached starts correctly.
The report_data table stores Nagios event information but is hard to read directly. SQL queries can convert this data into a more human-readable format by interpreting event types and state codes.
Creating a local mirror of the OP5 repositories allows fetching packages without direct Internet access. The process involves setting up a CentOS server, synchronizing repositories, configuring Apache, and updating OP5 Monitor repository settings.
Management packs group services linked to a hostgroup and allow adding custom variables for consistent monitoring. They are created by selecting a hostgroup, naming the pack, adding an icon and description, then saving and optionally activating or importing them.
Creating an event handlers with Python in OP5 Monitor automates responses to service state changes. The process involves scripting the handler, defining it as a command, and associating it with a service in OP5 Monitor.
Creating tickets from Logger using listview columns involves adding a custom column with a link that generates a pre-filled email. The process includes configuring the Log messages view to display a "Support" column that opens an email form when clicked.
Delaying notifications in OP5 Monitor queues alerts during off-hours for later delivery. This method uses scripts, a special contact, and a cron job to batch-send notifications at a set time.
Disabling Dokuwiki permanently involves editing the Apache configuration to block access to the dokuwiki folder. This is done by adding a Directory section in ssl.conf and verifying access is forbidden via the browser.
Disabling performance data collection is useful on pollers that send results to a master for processing. To disable it, update naemon.cfg to stop perfdata handling and disable the NPCD service responsible for performance data shuffling.
Automating agent distribution and configuration for NMS using Puppet simplifies large IT environment management. The paper and project files provide guidance on efficient deployment and service management with Puppet.
OP5 minor updates from version 8.x to higher versions can be performed on CentOS despite its End-of-Life status. The process involves enabling Centos-Vault.repo repositories, updating repo files, and verifying yum uses the vault repositories.
Downloading OP5 Monitor 8 or 7.5 installers requires specific URL paths for older versions. Use designated URL extensions to access base and other versions not listed on the ITRS Downloads page.
Enabling Apache Auth in OP5 Monitor involves configuring the Apache auth modules and assigning group rights within OP5. The process requires setting up authentication in Apache for specific paths and enabling auto login in OP5 to handle user authentication properly.
Graphs do not display for services using the check_icmp plugin after updating OP5 Monitor to 9.13. Editing the processperfdata.cfg file to use MULTIPLE storage and restarting the service resolves the graph display issue.
Enabling Naemon debug logging requires editing the naemon.cfg configuration file and setting debug options. After configuring log file path, debug level, verbosity, and max file size, restart Naemon to apply the changes.
Trapper Collector logging can flood /var/log/messages with SNMP trap data lines. Create a custom collector service with modified command line arguments to redirect logs and disable the original service.
Exporting objects like hosts and services to a CSV file uses the mon query ls command with Livestatus/LMD. You select tables and columns, then output semicolon-separated data directly to a CSV for further processing.
Exposing op5 Monitor's API through a reverse proxy allows secure external access. The guide explains configuring Apache HTTP server and recommends security measures like firewalls and certificate verification.
Extracting specific columns from OP5 Monitor CSV report exports enables data reuse in other applications. Command-line tools like App::CSV, csvkit, and awk provide methods to automate column extraction from availability reports.
Faking perfdata helps test graphs, RRD files, and integrations using a custom plugin. Create a script that outputs random data, then configure a check command and service to use it.
Fetching CSV reports over the OP5 Monitor HTTP API requires authentication and setting specific report parameters. The process involves generating reports via the web interface, copying the direct link, appending CSV output and authentication details, while considering server performance impacts.
Finding all hosts without any associated services helps identify unmanaged or inactive devices. Use the filter numservices = 0 in the hosts list to display hosts with no linked services.
Backups of previous configuration saves by Nachos are stored as tar files in /var/cache/naemon before each commit. You can restore configurations by replacing the /opt/monitor/etc directory and forcing a reimport of the configuration files.
The error "1364 Field 'alias' doesn't have a default value" occurs during configuration import. Removing the "STRICT_TRANS_TABLES" mode from MySQL/MariaDB settings and restarting the service resolves this issue.
The error "Cannot find a valid baseurl for repo: base" occurs on EL6 due to CentOS 6 reaching end-of-life. Updating the CentOS Base repos to use vault.centos.org instead of mirrorlist resolves the issue and allows OP5 Monitor updates.
The error occurs when pushing configuration due to a missing host group in merlin.conf. Create the host group before adding it to Merlin to resolve the issue.
Gateway Timeout errors occur when accessing group rights or other OP5 pages due to insufficient HTTP timeout settings. Adjust the timeout value in /etc/httpd/conf/httpd.conf and restart the httpd service to resolve the issue.
The "License signature is invalid" error in OP5 Monitor occurs due to OS-level security settings disabling certain signature algorithms. The issue can be resolved by adjusting the security policy to DEFAULT and updating specific license-related packages.
Undefined property: CorePDOHandler error in Nagvis occurs due to incorrect back-end settings. Fix this by correcting the back-end value in nagvis.ini.php or map-specific files without restarting Apache.
The "We found no log messages for your selected options" error occurs when event log files are missing or unreadable. Fix file permissions or remove compressed files to restore log message display in OP5.
Users in the limited_edit group cannot edit hosts or services if they lack permission to view the related templates. Administrators must enable "Host Template View All" and "Service Template View All" permissions for the affected group to resolve this.
Expired checks on the check_distribution service can result from high node load or disabled active checks. Use system monitoring tools and configuration scripts to diagnose and unify settings across the cluster.
Critical alerts on "Nachos - HTTP" and "Magellan - HTTP" occur in clustered OP5 environments due to connection refusals on specific ports. Updating to OP5 Monitor 8.2.1 and replacing old HTTP services with new ones resolves these alerts.
Dell repository GPG key and certificate validation errors can cause yum update failures. Updating the CA bundle and manually adding missing keys resolves these certificate and key issues.
False positives with the check_vmware_api plugin occur when alarms are cached in the database but not present in vCenter. Clearing the event log and updating it can resolve this issue, with additional guidance available from VMware Knowledgebase and Veeam forums.
Incorrect report data in OP5 Monitor can be fixed by synchronizing and reinserting report data or inserting a global OK state. These methods rebuild report data from logs or set all objects to OK at a specific time.
Missing dependencies occur when installing OP5 Monitor 8 on Red Hat Enterprise Linux 7 without enabling the optional-rpms repository. Enabling the optional-rpms repository resolves these dependency issues and allows successful installation.
Missing locations in OP5 Geomap occur if required XML files are absent, have incorrect permissions, or contain invalid data. Ensuring links.xml, locations.xml, and settings.xml exist with proper ownership and valid content resolves the issue.
Negative latency values can cause the check_vmware_api plugin to return CRITICAL status intermittently. This issue can be resolved by collecting multiple data samples or by switching to the newer check_vmware_v2 plugin.
Perl-based checks may break after upgrading OP5 Monitor due to stricter Perl library requirements for encrypted HTTP connections. The issue can be resolved by configuring Perl to accept insecure certificates using an environment variable and restarting Naemon.
Report generation fails with a time string parsing error when the dateformat setting in naemon.cfg is changed. Keeping the default dateformat setting prevents this PHP error and ensures proper report rendering in OP5 Monitor.
Bischeck enables dynamic and adaptive threshold monitoring in OP5 Monitor using historical data and time-based rules. It integrates via APIs and allows configuring hosts, services, and serviceitems with flexible thresholds for accurate alerting.
Getting started with NagVis involves creating your first map using the included op5 installation. This video tutorial demonstrates the process and applies to Naemon or Nagios environments too.
OP5 Trapper allows receiving SNMP traps using a simple generic rule to list all incoming traps. The process involves creating a catch-all handler, sending a test trap, and verifying traps appear in the list view.
HTTPS is now enabled on the OP5 Monitor package repository, affecting yum baseurl settings. To fix update issues, allow firewall access to port 443 or revert yum baseurl to HTTP, though HTTPS is recommended.
UI failover is not supported in an OP5 master-peer setup, causing UI access issues when the primary master is inactive. Use one designated primary master for full UI access and configure the secondary master for limited monitoring during failover.
Hiding credentials for service checks in OP5 improves security by using $USERn$ macros defined in resource.cfg. This method requires syncing resource.cfg across nodes and restarting services to ensure credentials are properly obfuscated and accessible.
Agentless monitoring of Windows servers using WMI enables monitoring without installing an agent. This guide explains how to configure WMI access, add hosts, and set up service monitoring in OP5 Monitor.
SAML based authentication on CentOS 7 integrates OP5 Monitor with an Identity Provider like Okta using Apache and mod_auth_mellon. The process involves configuring Okta, setting up Apache authentication modules, and updating mod_auth_mellon for SSO functionality.
Implementing SSL for OP5/NRPE on Linux secures monitoring using self-signed certificates. This guide explains creating a certificate authority, configuring certificates, and testing SSL connections for NRPE checks.
Hosts can be bulk-imported into OP5 Monitor using an Excel file with specific headers. The script supports cloning service checks and auto-detecting Windows disk usage for added hosts.
Including custom files or folders in op5-backup requires creating a module file with the folder paths. Adding these paths to the module file ensures they are backed up during every op5-backup run.
Increasing the datatimeout setting in Merlin allows nodes more time before being marked INACTIVE. The same datatimeout value must be set on all peered nodes in the cluster for consistency.
Inspecting data collected by ist-collect involves viewing compressed tar archives without extraction. Use vim or tar with less to navigate and read files directly on the production machine.
Installing Bischeck on OP5 Monitor requires configuring the Nagios Service Check Acceptor (NSCA) and editing specific configuration files. The guide provides steps for setting encryption methods, passwords, and restarting services to enable Bischeck functionality.
Installing DokuWiki stand-alone on CentOS 8 involves setting up Apache, PHP, and configuring permissions for the wiki directories. The guide provides step-by-step instructions for installation, initial setup, user management, and migrating existing content.
Installing and configuring the NRPE agent on Debian and Ubuntu client hosts is explained. The guide covers package installation, configuration, and firewall settings for proper monitoring with OP5 Monitor.
Installing the NRPE agent on RHEL based systems enables monitoring client hosts with OP5 Monitor. The process involves adding the EPEL repository, installing NRPE and plugins, configuring allowed hosts, and restarting the agent.
Installing OP5 Monitor in a Hyper-V environment requires configuring the virtual machine correctly. Use a legacy network adapter instead of a standard network adapter to avoid installation errors.
Installing OP5 Monitor support tools requires adding the community yum package repository. The process involves running specific commands for versions 8.x and 9.x to complete the installation.
Installing the NRPE agent on SLES 12 and 15 enables monitoring with OP5 Monitor using UNIX client services. The guide explains repository setup, NRPE installation, configuration, firewall adjustments, and service addition in OP5 Monitor.
Installing the NRPE daemon on CentOS 8 enables remote checks with OP5 Monitor despite lack of direct support. The process involves adding the EPEL repository, installing NRPE and plugins, configuring the daemon, and adjusting firewall settings.
Installing third-party plugins in op5 Monitor extends monitoring capabilities and integrates new devices or systems. This guide explains how to upload, configure, and troubleshoot plugins using SSH/SFTP and the op5 Monitor command interface.
Active Directory integration with OP5 Monitor enables centralized user and group management via LDAP authentication. The setup involves creating a service account, configuring LDAP settings, and defining user groups to control access permissions within OP5 Monitor.
Integrate OP5 Monitor with Slack to send alerts directly to your team's Slack channel. Configure the Slack plugin, create check commands, and assign a Slack contact to hosts or services.
Integrating OP5 Monitor with PagerDuty sends alerts directly to the correct contact. Set up a PagerDuty service and create a matching contact in OP5 Monitor using the integration email.
Integration of op5 Monitor with BMC Proactive Net Performance Management uses BMC Impact Poster (msend). Configuration steps, command setup, and testing methods for sending notifications to BPPM are detailed in the guide.
The check_nrpe plugin returns CRITICAL by default on socket timeouts. Adding the -u flag to the check command changes the timeout response to UNKNOWN instead.
Making the same change on many objects in OP5 Monitor involves using groups or templates. You can also propagate selected settings to multiple objects for batch updates without inheritance.
OP5 Monitor security can be improved by enabling Merlin encryption and restricting "test this check" permissions. Additional steps include installing signed SSL certificates and disabling non-encrypted SNMP versions for safer data transfer.
Managing operating system settings in OP5 Monitor on EL7 involves using new tools like nmtui and chronyd. This guide explains configuring network, time synchronization, email sender, backups, updates, and service management on RHEL 7.
Migrating an OP5 Monitor Server from EL6 to EL7 involves updating CentOS 6 to CentOS 7. This guide provides the necessary steps to perform the migration while considering supported OP5 versions 8.4.x and 9.x.
Migrating OP5 Monitor 7 or 8 from EL6 to EL7 requires matching versions and careful backup handling. The process involves setting up EL7 machines, backing up and restoring data, and transferring IP settings and custom plugins.
The NSClient++ 0.5.2.35 web server has a vulnerability exposing the web administrator's password to local users. Disabling the web server and verifying its status prevents unauthorized access and mitigates this security risk.
Agentless monitoring of Citrix XenServer clusters uses the XEN API to check hosts and VMs. The setup involves adding commands and services in OP5 Monitor and configuring user access to the XenServer hosts.
Monitoring a Kubernetes cluster with OP5 involves using the built-in plugin or a third-party Nagios-compatible plugin. Configuration requires installing dependencies, setting up scripts, and connecting the OP5 server to the monitoring server.
Monitoring a KVM installation with OP5 Monitor uses the check\libvirt plugin for agentless resource tracking. The plugin supports SSH and TLS protocols and monitors host and VM parameters like CPU, memory, and storage usage.
Monitoring a process with a specific argument in OP5 involves using the checkprocs plugin with the -a option. This method filters processes to monitor only those matching the specified argument.
Monitoring a SAN box with OP5 is possible using SNMP protocols. Consult your SAN manufacturer for available SNMP traps to enable effective monitoring.
Monitoring servers with Enhanced IPMI sensors requires configuring IPMI and using the check\ipmi\sensor plugin. The plugin supports local and remote checks and monitors various hardware sensor groups based on system configuration.
Monitoring a specific Microsoft Windows event ID with OP5 Monitor uses the NSClient++ check_eventlog function. This allows creating a service that alerts when the specified event ID occurs within the last 24 hours.
Monitoring an Oracle database server requires installing Oracle Instant Client and using the check\oracle.pl plugin. The plugin automates common DBA tasks and monitors availability, tablespace usage, transactions, and more with user authentication support.
Monitoring Cisco UCS Blade chassis requires installing a custom plugin since OP5 Monitor lacks built-in support. The guide explains downloading, configuring SNMP commands, and adding services to monitor chassis temperature, fans, power supplies, IO cards, and fault summaries.
Dell servers can be monitored remotely using SNMP and the Dell OpenManage Server Administrator (OMSA) with the OP5 Monitor plugin. The process involves installing OMSA, verifying SNMP connectivity, updating the plugin, and adding the appropriate monitoring service in OP5 Monitor.
Monitoring FreeBSD 13 servers using NRPEv3 with OP5 Monitor 8.4.0 involves installing and configuring NRPE3 and custom check plugins. The guide provides step-by-step instructions for setup, configuration, and creating services in the Monitor GUI.
HP printers with JetDirect cards can be monitored using two different plugins. Use either the check\hpjd or check\snmp\printer command for printer status monitoring.
Monitoring HPE 3PAR StoreServ with op5 Monitor involves setting up a custom check script and configuring SSH access for the monitor user. The process includes downloading the plugin, creating SSH keys, and defining check commands to enable service monitoring.
Monitoring JBoss with check_jmx involves using the plugin to track MBean attributes exposed via JMX on the application server. The process requires enabling the JMX agent, installing the check_jmx plugin, and configuring check commands and services within OP5 Monitor.
Monitoring Linux and Unix servers via SNMP involves configuring the SNMP daemon and adding hosts in OP5 Monitor. SNMP v3 and v2c checks monitor CPU, memory, disk usage, and processes with recommended security settings.
Monitoring log filters in OP5 Monitor involves using the check\op5\filter plugin to create queries and set alert thresholds for log messages. The process includes building filter queries, configuring checks, and optionally graphing performance data for detailed log analysis.
Monitoring Microsoft Active Directory involves checking domain controllers and core services like LDAP and Kerberos using op5 Monitor. The process includes configuring NSClient++, adding check commands, and optionally creating a service group for easier status overview.
Monitoring Microsoft Hyper-V requires installing the latest op5 NSClient++ and configuring firewall settings for ICMP ping or version checks. The process includes monitoring OS metrics, essential Hyper-V services, and specific performance counters for disk, memory, network, and virtual machine health.
Monitoring Microsoft SQL clustered servers requires configuring OP5 Monitor to track drives and Win32 services on virtual server names. The setup involves adding virtual servers as hosts and escaping the $-sign in service names for accurate monitoring.
Monitoring Microsoft SQL Server 2012 health with op5 Monitor involves using the check_mssql_health plugin. You need to set the TDS version to 8.0 in /etc/freetds.conf for compatibility with SQL Server 2012 or later.
Monitoring Microsoft SQL Server involves checking server resources, operating system performance counters, database queries, and backup jobs using OP5 Monitor. The guide explains configuring check commands, adding services, and adapting settings for SQL Server 2012 or clustered environments.
Monitoring specific Microsoft Windows Eventlog IDs helps detect system changes and behavior patterns. Configuration involves adding check commands and services using NSClient++ 0.4.4.15 in op5 Monitor.
Monitoring Red Hat Enterprise Linux servers with OP5 Monitor requires installing the NRPE client and configuring checks. The process includes adding servers via the Host Wizard or manually selecting NRPE services for basic and additional monitoring.
Monitoring SNMP traps with OP5 Monitor involves using the Trapper tool for effective trap handling. Configuration details and setup guidance are available in the Admin Guide and related documentation.
Monitoring local hardware on OP5 Monitor servers uses Dell OpenManage Server Administrator software. Install OMSA, verify SNMP, and add services to track server health and access the web GUI.
Monitoring unused switch ports in OP5 Monitor involves configuring SNMP access and adding specific check commands and services. The process allows viewing detailed reports on port status, description, speed, and idle time for effective network management.
Monitoring VMware vSphere infrastructure with check_vmware_v2 covers datacenters, hosts, and virtual machines. It explains installation, configuration, service management, available counters, and troubleshooting for effective monitoring.
WebInject monitors websites by testing real-world scenarios like login processes and page content. It uses XML configuration and test case files to perform tests and integrates with op5 Monitor for automated monitoring.
Monitoring Windows performance counters in op5 Monitor involves selecting and verifying counters using perfmon and command-line tools. The process includes adding a specific check-command and service to graph and track the desired performance data.
Monitoring Zimbra MailServer requires installing a plugin, configuring NRPE, and setting appropriate sudo permissions on the server. This guide provides step-by-step instructions for plugin installation, NRPE setup, and adding the management pack in op5 Monitor.
One-way integration between OP5 Monitor and ServiceNow automatically creates and populates ServiceNow incidents with alert information. The integration requires uploading the ServiceNow pack, installing dependencies, configuring settings, creating a check command, and assigning a ServiceNow contact.
Disabling Logger permanently in OP5 Monitor involves stopping syslog-ng or rsyslog configurations and optionally disabling PostgreSQL. The process includes editing configuration files and managing log rotation to prevent related error messages.
The perf_scan script helps identify hosts and services with the longest execution times. It runs on the Monitor server and shows the top five slowest hosts and services.
Disaster recovery for OP5 involves creating and restoring backups using the op5-backup and op5-restore scripts. The process includes preparing hardware, installing OP5 software, and restoring data from a recent backup tarball to recover the system.
OP5 Monitor includes the ist diagnose tool to quickly detect common system issues without making configuration changes. Running ist diagnose prints warnings or errors to help identify problems or prepare detailed reports for Client Services support.
Removing custom plugins from OP5 Monitor involves deleting the associated NRPE command and removing the check from all service configurations. The process includes managing commands in the OP5 Monitor interface and saving configuration changes.
Removing or resetting a specific service graph involves deleting the related RRD and XML files from the OP5 server's perfdata directory. To fully clear cached performance data, the npcd daemon must be stopped, rrdcached flushed, files removed, and npcd restarted.
Local user passwords in OP5 are stored as hashes in the '/etc/op5/auth\users.yml' file. The '/usr/bin/op5-manage-users' command is used to reset passwords but overwrites entire user entries, requiring careful syntax.
Restarting services automatically when OP5 Monitor generates an alert is possible. The process involves using event handlers as described in the Using event handlers to restart services guide.
Running NRPE plugins as root or another user allows execution of scripts with elevated privileges. Configuring sudo permissions and updating NRPE command files enables password-less execution of specified commands safely.
Saving a scheduled report under /tmp subfolders fails due to httpd's PrivateTmp=true setting. Disabling PrivateTmp via a systemctl override or creating writable subfolders resolves the issue.
Securing communications between the OP5 Monitor master and pollers involves setting up OpenVPN with x509 certificates for encrypted connections. The guide explains installing Easy-RSA, creating a certificate authority, generating certificates, and configuring OpenVPN for NAT-aware, secure master-poller communication.
Failed login attempts in the Ninja web interface for OP5 Monitor are recorded in the logs. Enabling debug log level in /etc/op5/log.yml for auth.log allows viewing these failed login entries.
Identifying which application created a specific file involves using the auditd tool to monitor file creation and execution events. By applying auditd rules and analyzing logs, you can trace the parent process responsible for creating the file.
Sending metrics from OP5 Monitor to Grafana involves using Nagflux to export performance data to InfluxDB, which Grafana then visualizes. The process includes installing and configuring Grafana, InfluxDB, and Nagflux, then creating dashboards to display your metrics.
Sending outgoing notifications via SMTP relay in OP5 Monitor requires configuring Postfix correctly. This includes setting relayhost, authentication, address rewriting, and verifying with test messages to ensure email delivery.
Contact-specific notification skins in OP5 allow customizing email notifications per user by creating folders named after contacts. The notification script uses these folders to override default skins for outgoing emails to those contacts.
Setting a variable notification delay in OP5 adjusts the time before notifications are sent for hosts and services. This can be done using the HTTP API for templates or an older shell script, affecting new hosts and services added afterward.
Setting up a geographical map in NagVis requires configuring map options and assigning latitude and longitude coordinates to hosts. The process involves creating a map, setting its size and source type, and optionally filtering hosts by group for display.
Remote NRPE monitoring involves installing the NRPE agent on hosts and the NRPE client for monitoring. Several guides are available for different operating systems to help set up remote NRPE monitoring effectively.
Setting up Selenium Server on Microsoft Windows involves installing required software and configuring OP5 Monitor. This guide explains installation steps, test case export, and monitoring setup using the Selenium check plugin.
Virtual Router Redundancy Protocol (VRRP) allows one DNS name and IP address to switch between master servers automatically. The setup involves configuring VRRP on master servers and activating it via the keepalived.conf file and a command.
Secure communication between an OP5 master and cloud poller is established using OpenVPN with specific certificate and key configurations. The setup involves generating keys, configuring OpenVPN files, adjusting firewall rules, and enabling OpenVPN to autostart on both systems.
Login issues in OP5 can occur due to empty or NULL passwords in the auth_users.yml file. The solution involves identifying users without passwords and resetting them using the op5-manage-users command.
The maximum response size of 104857600 bytes in OP5 Monitor can cause all values to show as zero. Increasing the Livestatus response size in the configuration file and restarting Naemon resolves this issue.
The error occurs because NSClient++ uses a 512 bit key instead of the required 2048 bit key. Generating and installing a new 2048 bit Diffie-Hellman key resolves the SSL handshake failure with check_nrpe.
Sound alarms can be played in your browser when alerts occur in OP5 if the browser supports required plugins. The alarm sounds are automatically played from specific NagVis map files without additional configuration.
Submitting status updates through the op5 Monitor HTTP API enables passive checks for services and hosts. The process uses cURL or scripts with proper permissions to update service statuses and integrate with other applications.
Wireless monitoring involves tracking access point status, interface traffic, and connected clients to prevent network failures and bottlenecks. Baseline monitoring includes ping checks, interface status, error rates, and client counts using OP5 Monitor plugins and SNMP scans.
Successful network monitoring implementation involves planning, prioritizing tasks, and involving key stakeholders. It requires staged deployment, proactive alerts, and using reports to manage IT services and improve operations.
Sync contact groups in OP5 Monitor using the LDAP Helper module and LDAP groups. Configure the module, run the sync script, and optionally schedule periodic updates with a cron job.
Synchronizing files and folders between OP5 Monitor peers using Merlin requires configuring each peer in the merlin.conf file. The synchronization is performed by the monitor user, so files and directories must be owned by that user for successful syncing.
Testing an SMS-Modem using Minicom involves configuring serial ports and sending AT commands. This guide provides steps to check modem status, network registration, SIM PIN, and signal strength.
Trimming rrd graphs removes peaks by limiting maximum values in the RRD file. This involves tuning, dumping, and restoring the RRD file to apply the new limits and omit excess data.
Argument parsing issues in OP5 Monitor can be troubleshooted using the pwrap command wrapper script. This script logs arguments, environment variables, output, and return codes to help analyze and re-execute commands accurately.
Gaps in a service performance graph can occur due to errors, zero or missing performance data, poller failures, long check intervals, or disabled checks. Troubleshooting involves verifying check execution, performance data output, and backend graphing processes to identify the cause.
The check_yum_update plugin may show incorrect output compared to a manual yum run due to errors in the update command output. Troubleshooting involves identifying and resolving these errors, such as disabling or commenting out defunct repositories causing the issues.
Nachos troubleshooting covers issues with service status, configuration saving, database access, and common errors like stuck exports or missing tables. It provides steps to check service, logs, database credentials, and configuration to resolve or diagnose problems.
Troubleshooting the GSM Modem, GSM Gateway, or GSM Terminal involves verifying SMS sending, daemon status, LED indicators, and network registration. The guide provides steps to check modem connection, logs, COM port settings, and LED status for effective diagnosis.
Tuning thresholds in op5 Monitor helps reduce false or excessive notifications by adjusting alert configurations. The process involves generating reports to identify top alert sources and modifying settings based on detailed problem analysis.
Tuning PHP and MySQL settings can improve OP5 Monitor performance for large configurations and heavy reports. Adjustments involve creating custom configuration files and restarting services, with rollback possible by deleting these files.
An empty event log page in OP5 Monitor can result from missing data or configuration issues. Checking Livestatus output, the archives folder, and Naemon service status helps identify and resolve these problems.
Updating OP5 Monitor involves using yum for minor upgrades and specific steps for major versions. Migration from Monitor 8 to 9 requires a new EL8 server and the op5-check-migration tool.
check_by_snmp_memory reports incorrect memory usage on Red Hat Enterprise Linux 7.7 and CentOS 7.7. Use the -S flag in OP5 Monitor 7.5.4 or later to disable double subtraction of cached and buffered memory.
Check_by_ssh allows monitoring remote Linux systems using SSH instead of NRPE, avoiding extra daemon installation. The setup involves creating a remote user, generating SSH keys, installing monitoring plugins, and configuring check commands and services in OP5 Monitor.
Using check_oracle with Oracle Instant Client allows direct monitoring of Oracle databases without third-party agents. The setup involves installing Instant Client, configuring environment variables for Naemon, and verifying connectivity through OP5 Monitor commands.
Event handlers in OP5 Monitor automate actions like restarting services when a host or service state changes. This guide explains configuring event handlers with NSClient++ on Windows to restart IIS and manage scripts on both client and server sides.
ITRS Support Tools (ist, ist-collect, and ist-diagnose) help with diagnostics and log collection for OP5 Monitor. Use ist-diagnose first to identify issues, then run ist-collect to gather detailed data for support if problems persist.
PowerShell can be used to send POST and GET requests to the OP5 Monitor HTTP API. This guide provides example scripts for creating hosts and retrieving monitored hosts using PowerShell.
Using rrdtool helps inspect and insert data into RRD files for troubleshooting graphing issues. It provides commands to verify stored data, manually update files, and display file information.
Using the dollar sign ($) in check_command_args requires special handling to avoid variable interpretation. Encapsulate the argument in double quotes and escape the dollar sign with another dollar sign to pass it correctly.
Naemon object configuration files can be verified for errors using the naemon -v command. This command checks all linked configuration files and reports any errors that must be fixed for Naemon to accept the configuration.
The SNMP limitation causes totalnumberofzombieprocesses to misreport Idle processes as Zombie in Linux Kernel v4.14 and later. Using NRPE with a custom checkproczombie command provides an accurate workaround for monitoring Zombie processes in OP5.
Writing OP5 Monitor plugins with Python involves using exit codes and output for status messages. The guide explains plugin development basics, argument parsing, and using libraries like pynag to simplify coding.
Writing custom plugins for OP5 Monitor allows monitoring of applications not covered by default plugins. The process involves creating executable scripts that perform tests, output diagnostic messages, and return standard exit codes for integration with OP5 Monitor services.
Graphed performance data values may appear inaccurate or flattened due to data averaging and resolution limits. This happens because RRD files store values with varying accuracy over time and graph images use averaged measurement points.
Installing the NRPE monitoring agent on RHEL-based systems with SELinux or IPv6 is done via the EPEL repository. The process includes configuring the repository, installing NRPE, and optionally disabling the EPEL repository to prevent unintended package installations.
Forwarding SNMP traps received by trapper in OP5 Monitor is possible. Adding a configuration option in the collector.conf file enables traps to be forwarded to a second destination while still processing them locally.
OP5 Monitor can be installed on RHEL8 or CentOS 8 only with version 9. Refer to the Compatibility Matrix for detailed installation requirements and supported versions.
Monitoring a scheduled NMAP port scan is possible by using NMAP's output saved to the server log directory. The check_log2 feature can then monitor these logs and create alarms based on specific scan results.
Setting up a service or check_command with a dollar sign ($) requires escaping it as $$. Single quotes must surround $ARGn$ to prevent shell variable expansion during command execution.
Monitoring IBM LTO robots is possible using SNMP protocols. This allows tracking media access, physical media count, security breaches, and storage library status.
Support is available for monitoring IBM Servers X336, X335, X330, X306, and X305 using client control of the OS. Advanced hardware checks and notifications can be performed with IBM Supervice adapter 2 and op5 Trapper Extension.
LDAP authentication errors in OP5 UI occur when the account used has expired or is disabled. To fix this, contact the AD administrator to reactivate the account or reset its password.
OP5 License expiration notifications begin 26 days before the license expires, and the license validity is precise to the start time and date. After expiration, login to the OP5 GUI is disabled, but monitoring and alerting continue through command queries.
The OP5 Monitor license file is about to expire or has expired, affecting GUI access. Renew the license by contacting your Account Manager to restore full functionality.
License self-monitoring may show a warning despite having a valid OP5 Monitor license. Restarting the OP5 GUI or contacting support for a license update can resolve this issue.
Load balancer or HAproxy is not supported for peered master nodes in OP5. One peer should be the Primary Master handling all configurations and API requests to avoid conflicts.
Forwarding log messages from CentOS 7 or RHEL 7 to OP5 Monitor requires configuring rsyslog on the remote host. Ensure OP5 Monitor accepts connections on port 514 using TCP for reliable log forwarding.
Sending test messages to op5 Logger/LogServer helps verify log monitoring filters using the logger command line utility. This guide explains how to create and send syslog messages from a Linux shell to the op5 Monitor server for testing purposes.
Rsync protocol data stream errors occur when pushing configuration to a poller using rsync. Troubleshoot by checking rsync logs and addressing issues like large files, disk space, SSH keys, version mismatches, or missing directories.
MySQL running at very high CPU usage in Merlin can indicate corrupt tables or disabled indexing. The solution involves repairing tables if corrupt and enabling indexing for report\data to reduce CPU load.
Merlin Dashboard is incompatible with OP5 Monitor versions 9.18 and later due to PHP version changes. The dashboard is unsupported and cannot be fixed or updated by OP5 developers.
Merlin How-To provides procedural information for version 2.0.8 and other versions of Merlin. The content is imported from the Merlin git repository and is unsupported by ITRS support.
Microsoft has changed LDAP security policies, affecting OP5 Monitor users without SSL/TLS for LDAP AD integration. To comply, enable LDAP over SSL/TLS in the OP5 Monitor authentication module after Microsoft implements these changes.
Modifying Apache response headers in OP5 Monitor can affect the functionality of external widgets. Users need to adjust the Apache configuration to allow specific external widgets while understanding the security implications of these changes.
Monitoring high CPU processes on Windows with OP5 involves using a Powershell script executed via NSClient++. The process includes adding the script to the OP5 Agent, adjusting execution policies, testing the script, and configuring a new service in OP5 Monitor.
Monitoring temperature, humidity, and wetness with Sensatronics EM2 sensors in OP5 Monitor is explained. Configuration steps for probes, SNMP, and services with check_em1 commands are provided for effective monitoring and graphing.
Common files and logs that can fill up OP5 filesystem include backup files, naemon archive logs, and database entries. Guidance covers identifying large files and using tools like ncdu to manage disk space effectively.
Nachos.log errors like PermissionError and ConfigBackupException indicate configuration file access issues. Correct file ownership and directory permissions for the monitor user to resolve these errors.
Nagvis URL errors in OP5 Monitor often stem from outdated nagvis.ini.php files or missing Apache aliases. Updating the configuration file or adding an Apache alias and restarting the server resolves these errors.
Notifications in OP5 Monitor may not be sent due to downtime, disabled settings, missing contacts, or inactive email and SMS services. Troubleshooting involves checking service status, notification configurations, logs, and ensuring required services like Naemon, Postfix, and smsd are active.
NRPE installation on IBM AIX involves downloading packages, configuring nrpe.cfg, and setting up commands for monitoring. The process includes enabling dont_blame_nrpe, restarting NRPE, and linking it to run-level 2 for automatic startup.
NSClient++ script timeouts can cause errors due to cascading timeout settings across multiple components. Adjusting each timeout slightly lower than the next helps prevent overlapping timeouts and related script failures.
Offline upgrades of OP5 Monitor without ISO files apply to same major version updates on RHEL systems. This guide explains creating a local repository and running yum update from a downloaded tarball.
Monitoring HP RAID controllers requires an external script and HP ACU CLI installation. The guide explains how to configure the script and add a RAID status service in op5 Monitor.
Monitoring response time with NSClient++ measures average roundtrip time and packet loss. Configuration involves setting up check\ping on a remote Windows server and adding commands to OP5 Monitor.
OP5 supports comprehensive logging, audit trails, and policy enforcement to meet key NIS2 compliance requirements. Some NIS2 areas like continuous monitoring, vulnerability checks, and incident reporting are outside OP5’s current scope.
Creating custom commands in OP5 involves copying and adapting existing command templates to fit your monitoring needs. The FAQ guides you through safely duplicating a command, modifying its settings, and using it in service checks.
The FAQ explains how to install the ist-collect tool offline in environments with strict network security restrictions. It provides steps to download, extract, and install the necessary packages to enable ist-collect commands without online access.
OP5 license host allocation limits can be checked by monitoring the "license percentage of host left" self-monitoring service check or running the plugin manually. If the limit is exceeded, contact ITRS Support for a license upgrade.
Merlin Dashboard is a third-party fork of nagios-dashboard designed to display unhandled system problems on a big-screen TV, with added Livestatus support and fixes for OP5 Monitor. It is maintained externally on GitHub and is not officially supported by OP5.
OP5 SLA calculation in cluster mode (best state) measures availability based on all nodes being down simultaneously. The SLA may be less than 100% due to overlapping non-UP states like WARNING affecting the cluster’s availability calculation.
OP5 displays all time values in the UTC time zone by default, regardless of user location. The time zone is set on the OP5 Monitor server and cannot be changed to match local user time zones.
Oracle Instant Client packages are no longer included in OP5 Monitor repositories or installation bundles due to licensing restrictions. For installation and usage, refer to the separate guide on using check\oracle with Oracle Instant Client.
The recommended thresholds for the "check_load" plugin depend on the number of CPU cores in the system. Thresholds should be set to a load value not exceeding 1.0 per core based on a 5-minute average.
Exporting CSV performance data from pnp4nagios in OP5 Monitor requires using a specific base URL and host/service parameters. Authentication differs from standard pnp4nagios, as OP5 Monitor uses login cookies instead of basic HTTP authentication.
Pollers or peers may show as disconnected due to version mismatches, SSH key issues, or invalid Naemon configuration. Troubleshooting involves verifying versions, ensuring SSH keys are correctly propagated, restarting services, and checking node communication.
Indexes disabled on MySQL tables can cause slow GUI operations and report generation in OP5. Re-enable indexes by running the enable keys query after a full backup and during a scheduled maintenance window.
Replacing the Jira API token in OP5 Monitor requires updating configuration files on the server. There is no standard GUI option, so changes must be made manually and the related service restarted.
The "Request-URI Too Large" error occurs when the requested URL exceeds the server's length limit. This issue can be resolved by adding a custom Apache configuration file and restarting the httpd service.
The OP5 Monitor cookie banner may appear in reports due to using a custom skin. To fix this, copy the common.css file from the default skin to your custom skin.
Reverse or negated service checks return opposite result codes for monitoring conditions like bandwidth thresholds. The Negate plugin enables this by running checks from /opt/plugins and optionally changing output text with the -s flag.
Sending passive results to OP5 Monitor using the mon query handler allows checks from unscheduled scripts. The guide explains using mon commands or sockets to submit service and host check results, including multiline and performance data support.
Service checks for system updates fail due to a GPG signature error caused by missing keys for the monitor user. Running dnf check-update as the monitor user or using asmonitor with root resolves the issue.
The SMS terminal recommended for OP5 is the CEP HT910G model. Specifications and datasheets are provided, but ITRS does not support SMS modem queries or issues.
Smsd service fails to start if the smsd.working runtime file cannot be created. Ensure the custom directory in /etc/smsd.conf exists and is owned by smstools:smstools to fix this.
SMS issues after upgrading to OP5 Monitor 8.0.7 are caused by permission conflicts with the smsd daemon running as a non-root user. The hotfix adjusts file ownership and group memberships to restore proper access and functionality.
Adding custom MIBs to an OP5 Monitor server involves compiling and placing MIB files in the correct directory. You must update the snmp.conf file to include all MIBs and restart the SNMP daemon for changes to take effect.
SNMP traps may not appear in the OP5 interface due to missing packets or DNS issues. Checking packet arrival and DNS configuration helps identify and resolve trap display problems.
SNMP self-monitoring can break during upgrade or migration to OP5 v9, causing errors in self checks. The issue can be resolved by manually adding SNMP users on the affected OP5 Monitor nodes using specific commands.
Time periods in OP5 Monitor control when services are checked and notifications are sent. They can be configured to include work hours, holidays, exclusions, and specific notification schedules.
NSClient++ connection issues occur due to service status, firewall, Allowed Hosts, or SSL settings. Troubleshoot by verifying service, firewall port 5666, Allowed Hosts configuration, and SSL certificates on the Windows server.
UI may fail to load if the license file is improperly copied to the OP5 host. Ensure the license file name, ownership, and permissions meet the specified requirements to resolve this issue.
NRPE-based checks cannot run scripts or file check plugins inside /var and /tmp directories due to systemd service restrictions. Modifying the nrpe.service file, reloading the daemon, and restarting the service resolves this issue.
OP5 Monitor licensing is based on the number of hosts monitored and the contract duration. Hosts include physical or virtual devices with unique names, and licenses can be upgraded anytime during the contract period.
The Livestatus Multitool Daemon (LMD) provides cached monitoring data when Naemon is unavailable. Configuration options and troubleshooting steps help maintain access and resolve common LMD service issues.
Updating OP5 Monitor may cause 404 errors due to removed and obsolete repositories. Remove old repo files, enable correct repos, and clear yum cache to fix update issues.
Upgrade and migration processes for OP5 Monitor require setting up new servers for major version changes. Detailed steps guide migrating from versions 7.5.x and 8.x on EL6 or EL7 to version 9.x on EL8.
RRD in MULTIPLE mode addresses issues with check plugins that produce a variable number of performance data labels. Enabling this mode creates separate RRD files per data source, allowing dynamic scaling and preventing update errors.
The OP5 web interface may have missing or non-rendering icons in the browser. To resolve this, verify the icon directory contains .png files and clear the browser cache or try a different browser.
Using git repositories to track and restore local OP5 configuration files helps manage changes over time. The process involves setting up git as the monitor user, automating commits, and using git commands to revert or inspect configuration changes.
Using the op5 Monitor REST API with PHP enables communication between your application and op5 Monitor. This guide provides setup instructions, prerequisites, and example code to list service states on a specific host.
A valid OP5 licence may not be recognized, causing the GUI to display a licence expired message despite confirmation from op5-licence-inspector. Restarting the php-fpm service can resolve this inconsistency after a system update.
OP5 Monitor requires specific configuration to produce SLA reports for redundant Nameservers or DNS. Using Business Services or an alternative check command that tests all nameservers ensures accurate SLA reporting for redundant DNS setups.
NPCD errors often occur when service names are too long or when processing times out. Adjust service name length or increase the TIMEOUT setting to resolve performance data processing issues.
No data shown in the OP5 Monitor UI can be caused by stopped or crashed naemon or lmd services. Use the ist diagnose tool to check system status and restart the naemon or lmd services if needed.
The op5-extra-tools-check-migration package may be missing during migration to OP5 Monitor 9.x. Ensure the op5-monitor-updates repository is enabled and its .repo file exists to resolve this issue.
Using <, >, or = in the check_nrpe command causes a 403 Forbidden error due to Mod Security blocking these characters. The recommended solution is to wait for the MON-12608 bug fix or temporarily disable Mod Security if immediate use is necessary.
Creating a Graph Collection can fail if the service name contains a colon or forward slash character. To resolve this, rename the service to remove these characters, or wait for the permanent fix in MON-12438.
OP5 Monitor sends unreachable notifications for child hosts when their parent host is down, indicating the parent host's status affects child host alerts. To avoid these notifications, adjust the contact, host, or host template settings to uncheck unreachable notifications.
OP5 Monitor is no longer shipped with an operating system to enhance security and reduce attack risks. Customers must now prepare their own operating system installations, with guidance available for offline installation scenarios.
Passwords or SNMP community strings containing "!" do not work because "!" is a separator in OP5 Monitor commands. To use "!" in these strings, you must escape it with a backslash "\" so OP5 interprets it correctly.
Apache/httpd may fail to start due to issues with the SSL certificate private key in OP5 Monitor. The resolution involves verifying that the checksum of the private key and certificate matches to fix the error.
GSM/UMTS gateways may fail to register on 3G networks due to factory misconfiguration disabling UMTS mode. Sending specific commands to the modem enables 3G functionality, allowing automatic connection to supported 3G networks.
Host checks may run more often than check_interval due to on-demand checks triggered by service state changes. These checks prevent multiple notifications by ensuring the host enters hard critical before its services.
No FAQs match your search.