Troubleshoot Installation and Upgrade
This topic outlines troubleshooting steps for issues you may encounter when installing or upgrading Moogsoft Onprem.
moog_farmd log
Located in /var/log/moogsoft
As with LAMs, logging is configured via the Log4j based logging (log_config section of the moog_farmd.conf file
Each line references the Moolet or process that wrote the message
![moog_farmd_log.png](image/uuid-dd590177-66cd-cd10-28a0-46a70b140b8d.png)
Yum errors and workarounds
Yum: Incorrect Moogsoft Onprem version
If an incorrect or outdated version is offered when installing Moogsoft Onprem your Yum cache may need cleaning.
Run the following command and then re-attempt the installation:
yum clean all
Yum: HTTP Error 401 - unauthorized
If an attempt to install Moogsoft Onprem fails with an error such as the following, check your username and password credentials are correct in the configured Moogsoft Yum repository.
https://<username>:<password>@speedy.moogsoft.com/repo/aiops/latest/repodata/repomd.xml: [Errno 14] HTTP Error 401 - Unauthorized
Yum: Problem making SSL connection
If an attempt to install Moogsoft Onprem fails with an error such as the following:
https://<username>:<password>@speedy.moogsoft.com/repo/aiops/latest/repodata/repomd.xml: [Errno 14] problem making ssl connection Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: moogsoft-aiops. Please verify its path and try again
You may need to update the NSS packages on your server. Run the following command and then re-attempt the installation.
yum -y update nss
UI errors and workarounds
Cannot access UI
If you cannot access the UI from your host machine, check your firewall and if you're listening on the right ports:
To check if your firewall is enabled:
service firewalld status
This returns the status
disabled
if the firewall is disabled.To disable an active firewall:
service firewalld stop
To check whether a port is open:
firewall-cmd --zone=public --query-port=8443/tcp firewall-cmd --zone=public --query-port=8080/tcp
To open a port:
firewall-cmd --permanent --zone=public --add-port=8080/tcp firewall-cmd --permanent --zone=public --add-port=8443/tcp firewall-cmd --reload
Cannot access UI integrations
If you do not uninstall certain UI integrations before upgrading to Moogsoft Onprem, you may see a 502 gateway error when trying to access integrations in the Moogsoft Onprem UI.
To solve the problem, follow these steps to delete the UI integrations and perform some cleanup tasks.
Run the following SQL against the
moogdb
database:use moogdb DELETE t1 FROM system_config t1 JOIN integration_url_tools t2 ON t1.id = t2.system_config_id; DELETE t1 FROM system_config t1 JOIN integration_moolets t2 ON t1.id = t2.system_config_id; DELETE t1 FROM sitroom_plugins t1 JOIN integration_sitroom_plugins t2 ON t1.id = t2.plugin_id; DELETE t1 FROM link_definitions t1 JOIN integration_link_definitions t2 ON t1.id = t2.link_id; DELETE t1 FROM alert_column_names t1 JOIN integration_custom_fields t2 ON t1.internal_name = CONCAT('custom_info.',t2.field); DELETE t1 FROM situation_column_names t1 JOIN integration_custom_fields t2 ON t1.internal_name = CONCAT('custom_info.',t2.field);
Run the following SQL against the
moog_intdb
database:use moog_intdb DELETE IGNORE FROM integration_migration;
Go to the Integrations tab in the UI and reconfigure your integrations.
Situation Room plugins or Situation client tools to external URLs do not work
A Situation Room plugin or Situation client tool shows an error similar to the following after upgrade:
Refused to frame 'https://site.com/' because it violates the following Content Security Policy directive: "default-src 'self'
This release includes a Content Security Policy that restricts the automatic loading of resources from external domains. You must follow the steps to configure Moogsoft Onprem to allow access to required external domains.
For instructions see RPM Installation or Tarball Installation according to your implementation type.