"Vizql Sessions" page is showing "Ouch" error in RMT installed on RHEL-like Linux distributions

Published: 14 Jun 2021
Last Modified Date: 16 Jun 2021


Upon clicking "Vizql Sessions" page under "Activity" in Resource Monitoring Tool shows the error:
Ouch - Something just went sideways. 

tabrmt log shows "System.UnauthorizedAccessException" error with 500 HTTP return code when opening "Vizql Sessions" page with hyper subfolder under RMT Master log directory.


  • Tableau Resource Monitoring Tool with versions earlier than 2021.2.1
  • RHEL-like Linux distributions


  1. Manually create hyper subfolder under Resource Monitoring Tool Master log folder. By default, RMT Master log folder is /var/opt/tableau/tabrmt/master/logs/.
  2. Change the permission and owner of the hyper subfolder. Make sure that this subfolder has same permission as other subfolders under RMT log folder.
  3. Restart RMT Master and RMT Agent


This is a known issue that is being addressed by Tableau development. 
This issue only happens in ".rpm" RMT installer with versions earlier than 2021.2.1 and it's not happening in ".deb" RMT installers. 

Additional Information

tabrmt log has addtional logging:
{"Timestamp":"2021-06-02T10:04:09.6119921+08:00","Level":"Error","MessageTemplate":"An unhandled exception has occurred while executing the request.","RenderedMessage":"An unhandled exception has occurred while executing the request.","Exception":"System.UnauthorizedAccessException: Access to the path '/var/opt/tableau/tabrmt/master/logs/hyper' is denied.\n ---> System.IO.IOException: Permission denied\n --- End of inner exception stack trace ---\n at System.IO.FileSystem.CreateDirectory(String fullPath)\n at System.IO.Directory.CreateDirectory(String path)\n at Tableau.PowerTools.Server.Master.Reporting.HyperFactory..ctor(IPowerToolsStartupConfiguration startupConfig)\n at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)\n at
{"Timestamp":"2021-06-02T10:04:09.6215803+08:00","Level":"Information","MessageTemplate":"{HostingRequestFinishedLog:l}","RenderedMessage":"Request finished in 21.2935ms 500 text/html;
Did this article resolve the issue?