Troubleshooting

General info

Here on this page you can find information about resolving known errors. Start with the relevant guide below, then create a new issue on GitHub if you still need help.

Logs

If you encounter an error, refer to the logs first. All logs are stored in the Admin area → Internal logs section. See the Internal logs guide for the available log types.

Check logs of the service in which the error has been detected (*Service name*-Logs in the left panel). For detailed information refer to the logs of RMON and to the error log as well.

Go to TOP

"Cannot update version" message when logging in

If you cannot log in and see the "Cannot update message" message in the right upper corner of the login page, you might have a problem with the database owner. This error occurs if the database was created manually and the owner was not changed. Set the correct database owner to resolve it: apache (in CentOS) or www-data (in Debian and Ubuntu).

Review the database installation settings before changing the database owner.

Go to TOP

Errors that occur when starting RMON services

If you cannot start a service and find no corresponding messages in the logs, try to check its state first:

For more information you may also refer to the system logs: /var/log/messages (in CentOS) and /var/log/syslog (in Ubuntu).

See RMON services for the services documented on this site.

If referring to the logs does not help, try to run the service manually:

Go to TOP

Errors that occur when updating RMON

If any errors occur when updating RMON via the web interface, try to update it via the command line:

Follow the current Update guide and check the Changelog before retrying an update.

Go to TOP

Internal server error during the first start or after update

If you see the Internal server error when launching RMON for the first time, open Apache error log, most likely some modules are missing. If so, install requirements from GitHub. Also review the Installation guide for the current installation steps.

Go to TOP

Error that occurs during the installation via Ansible

During the installation via Ansible you may encounter the following error:

This a known Ansible bug. To resolve it update Ansible to version 2.9.8 or newer.

For the supported package installation workflow, see the Installation guide.

You may also receive the following error message during the installation via Ansible:

This is a known bug of the NGINX official repository. It might be resolved soon. Now the only possible solution is to update Ansible at least to version 2.12.

On some Ubuntu installation could be:

It would appear because there is no needed package. Install it:

Go to TOP

Error when downloading metadata in course of installation

In the course of installation of RMON you may encounter the following error:

In order to resolve this problem, open the /etc/yum.repo.d/rmon.repo file and replace $ostype with el in the line, which begins with $baseurl.

Compare the repository configuration with the current RPM installation instructions.

Go to TOP