Resource Monitoring Tool Upgrade FAQs
Find answers to commonly asked questions during upgrade.
Can I run the scripts without root/Administrator privileges?
When scripts run automatically via the installer, the installer has the required privileges. For manual execution, you need root (Linux) or Administrator (Windows) because the scripts inspect service status, file permissions, and run commands as the RMT service account.
What if I don't know the database password?
All PostgreSQL-dependent checks are skipped with WARN. The script still runs all other checks. Contact Tableau Support for the password.
How to retrieve the password for the tabrmtdb database user?
You can retrieve the credentials by navigating to the RMT Server directory and running the command appropriate for your operating system:
For Windows:
.\rmtadmin get db:username db:password
For Linux:
rmtadmin get db:username db:password
Can I run the pre-upgrade check while RMT is in use?
Yes. The script is read-only and safe to run on a production system at any time.
What happens if the post-upgrade check finds failures?
The post-upgrade check never blocks the installer. Failures are surfaced in the report. Some (like "Broker unreachable") are transient and resolve on their own.
Are the scripts compatible with external PostgreSQL / RabbitMQ?
Yes. The post-upgrade script auto-detects external configuration and skips local checks appropriately. The pre-upgrade script's DB checks require --db-password regardless since it connects to the internal RMT database.
Can I run the scripts on both RMT Server and Agent machines?
Yes. Use --component master on the RMT Server and --component agent on Agents. If unspecified, the script auto-detects.
What does InstallerContext mean in the report?
When the pre-upgrade check runs automatically during a Windows MSI upgrade, the -InstallerContext option is set. This relaxes service and port checks — which may report stopped/Disabled because the installer has already disrupted services — to WARN, and skips the stranded-process gate (#38a) so the installer can manage process lifecycle itself. When you run the script manually, these checks use their normal severity.