Troubleshooting MAG installation

Check that bootstrap and configuration were successful:

If the bootstrap.log does not contain that string, examine the log for any exceptions or errors.

If the status is different, examine the output from report-initconf for any problems. If that is not sufficient, examine the ~/initconf/initconf.log file for any exceptions or errors. If bootstrap and configuration were successful, check the Rhino journalctl logs.

Further information can be found from the MAG logs in /var/log/tas. In particular, the Rhino logs are found in a subdirectory of /var/log/tas with the same name as the Rhino directory has in the home directory, e.g. gaa-4.0.0.0-cluster-110. Similarly, the REM logs are found in /var/log/tas/apache-tomcat.

Connect to REM using a web browser. The connection should be over HTTPS to port 8443 of the management interface, and to the /rem/ page. For example: https://192.168.10.10:8443/rem/

If you connect using a hostname rather than the IP address, be sure that the hostname refers only to a single server in DNS.

If connections to REM fail despite use of the correct hostname/IP and port, try the following:

If any of the above checks fail, try restarting REM with sudo systemctl restart rhino-element-manager. You can also check for errors in the log files in the /var/log/tas/apache-tomcat directory.

When connecting to REM, you should use one of the accounts set up in the mag-vmpool-config.yaml file. The default username/password documented in the REM product documentation is not available on the REM node.

When trying to connect to a Rhino instance, you need to enter the credentials REM can use to connect to Rhino. The Rhino username and password are configured in the VM pool YAML file for the Rhino nodes being monitored.

The mapping from REM users to Rhino users is deployment-specific (for example, you may wish to allocate a separate Rhino user to each REM user, so it is clear in Rhino audit logs which user made a certain change to Rhino configuration). As such, the VM software is unable to set up these credentials automatically.

It is recommended to use the "Save credentials" option so that you only need to specify the Rhino credentials once (per user, per instance).

For known REM issues, refer to the Known issues in REM section in the REM documentation.

The XCAP server and NAF authentication filter are executed as components within REM. Thus, for troubleshooting connection issues, first check you can connect to REM. If not, please refer to the Cannot connect to REM section.

If you can connect to REM but not to the XCAP server or NAF authentication filter, check that you are connecting over the access interface, on port 80 (HTTP) or 8443 (HTTPS).

If connections to the XCAP server or NAF authentication filter fail despite use of the correct IP, try the following:

If any of the above checks fail, try restarting nginx with sudo systemctl restart nginx. You can also check for errors in the log files in the /var/log/tas/nginx directory.

Rhino alarms indicate issues that should be reserved promptly. Rhino alarms can be monitored using MetaView Server or REM on the MAG node. Some common Rhino alarms are described below.