Troubleshooting

What are the default user credentials?

Here is the list of the default user profiles:

Operator User (Limited Privileges)

  • Login: ngrt4n_op
  • Password: ngrt4n_op

Administrator User (Full Privileges)

  • Login: ngrt4n_adm
  • Password: ngrt4n_adm

How to change my password?

Run the RealOpInsight Operations Console and go to the menu Monitoring Settings -> Change Password.

How to enable MKLivestatus over a Xinetd TCP socket?

Create the appropriate xinetd configuration in /etc/xinet.d/livestatus and restart xinetd. This configuration should look as follows:

service livestatus
{
    type = UNLISTED
    port = 6557
    socket_type = stream
    protocol = tcp
    wait = no
    cps = 100 3
        instances = 500
        per_source = 250
    flags = NODELAY
    user = nagios
    server = /usr/bin/unixcat
    server_args = /var/lib/nagios/rw/live
    disable = no
}

Basically, this means that the service shall listen on the port 6557 and shall forward requests to the UNIX socket located in /var/lib/nagios/live (server_args), which is assumed to be the path of the native socket managed by the Livestatus NEB. For more details, see the official documentation of MKLivestatus.

Additionally, replace /usr/bin/unixcat in the line server = /usr/bin/unixcat with the real path of the unixcat utility provided by MK Livestatus. You may also need to change in the line user = nagios according to your system. For Icinga for example, user is often named icinga instead of nagios.

How to enable Shinken Livestatus API over a TCP socket?

Add the following lines in your Shinken configuration file (shinken- specific.cfg), and restart Shinken.

define module {
  module_name Livestatus
  module_type livestatus
  host *
  port 50000
  socket /usr/local/shinken/var/rw/live
}

In short, this means that the service shall listen on any network interfaces (see the wild card * in line host *) on port 50000 on the Shinken server. For more details, see the official documentation of Shinken.

I got SSL error: Unable to init SSL Context

Often occurring on Windows operating systems, this means that your system lack some SSL library dependencies.

To fix that, following the steps described below:

I got SSL error: SSL handshake failed

This error generally occurs when your monitoring server relies on a self-signed certificate or a non-valid certificate regarding hostname, domain, etc.

To solve it, you have two options:

  • Either to fix your certificate,
  • Or disable SSL peer verification in RealOpInsight. The RealOpInsight Configuration Manager provides a checkbox to enable this option. WARNING: USE THIS OPTION AT YOUR OWN RISK. Even if enabling this option doesn’t compromise the cyphering of communication between RealOpInsight and the monitoring server, it disables many SSL controls, including the verification of the certificate hostname.