Unable to connect to Workgroup database for "What's Going On" TabMon dashboard

[sanjeevsuri]

Hello !

I am fairly new to this environment...so, please bear with me :) I installed TabMon on one of our distributed(clustered) Tableau Dev servers (Windows 10) and could get through the PostgresSQL (TabMon) connection but the PostgresSQL (Server Auditing) connection is failing. Server : localhost, Port: 8060 Database: workgroup Username: readonly Password: readonly

I did create the user prior to installing TabMon and restarted the services too tabadmin dbpass --username readonly readonly

The error I am getting is "could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 8060? could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 8060?"

I did follow the leads online and on Github pertaining to modifying the pg_hba.conf and postgres.sql files under the C:\ProgramData\Tableau\Tableau Server\data\tabsvc\config but am just not able to identify the issue.

Under Local Connections, I have these entries. host all rails 127.0.0.1/32 md5 host all tblwgadmin 127.0.0.1/32 md5 host all tableau 127.0.0.1/32 md5 host all readonly 127.0.0.1/32 md5 host all all 127.0.0.1/32 md5 host all rails 0:0:0:0:0:0:0:1/128 md5 host all tblwgadmin 0:0:0:0:0:0:0:1/128 md5 host all tableau 0:0:0:0:0:0:0:1/128 md5 host all readonly 0:0:0:0:0:0:0:1/128 md5 host all all 0:0:0:0:0:0:0:1/128 md5

Included the following line in postgressql.conf listen_addresses = '*'

Any guidance is appreciated.

Best Sanjeev

[ghost]

TabMon is installed on the same server as Tableau Server and Tableau Server is otherwise functioning correctly? If so, looks like that should work.

Are there any server firewall rules that may be blocking the traffic? Based on the error, it looks like it’s a connection issue getting to the database, so changes to pg_hba.conf shouldn’t be a factor yet. On Tue, May 22, 2018 at 3:43 PM sanjeevsuri notifications@github.com wrote:

Hello !

I am fairly new to this environment...so, please bear with me :) I installed TabMon on one of our distributed(clustered) Tableau Dev servers (Windows 10) and could get through the PostgresSQL (TabMon) connection but the PostgresSQL (Server Auditing) connection is failing. Server : localhost, Port: 8060 Database: workgroup Username: readonly Password: readonly

I did create the user prior to installing TabMon and restarted the services too tabadmin dbpass --username readonly readonly

The error I am getting is "could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 8060? could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 8060?"

I did follow the leads online and on Github pertaining to modifying the pg_hba.conf and postgres.sql files under the C:\ProgramData\Tableau\Tableau Server\data\tabsvc\config but am just not able to identify the issue.

Under Local Connections, I have these entries. host all rails 127.0.0.1/32 md5 host all tblwgadmin 127.0.0.1/32 md5 host all tableau 127.0.0.1/32 md5 host all readonly 127.0.0.1/32 md5 host all all 127.0.0.1/32 md5 host all rails 0:0:0:0:0:0:0:1/128 md5 host all tblwgadmin 0:0:0:0:0:0:0:1/128 md5 host all tableau 0:0:0:0:0:0:0:1/128 md5 host all readonly 0:0:0:0:0:0:0:1/128 md5 host all all 0:0:0:0:0:0:0:1/128 md5

Included the following line in postgressql.conf listen_addresses = '*'

Any guidance is appreciated.

Best Sanjeev

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tableau/TabMon/issues/178, or mute the thread https://github.com/notifications/unsubscribe-auth/ATUUxgjMdxKTyn3hU5oF_m0LwETB-GzRks5t1Hh1gaJpZM4UJW_b .

[sanjeevsuri]

Thanks for the response. TabMon is installed on the same system as the Tableau server and yes, it is otherwise functioning correctly. I can access the other dashboards in TabMon except "What's going on Dashboard?" I'll double check the firewall rules but am doubtful that we have anything inhibiting those connections but I might be wrong. Do I need to check port 8060 in particular ?

Thanks again for getting back. Appreciate it.

[ghost]

Correct, it is TCP 8060 and should be from 127.0.0.1 -> 127.0.0.1 and/or ::1 -> ::1 given the way I am reading your current config correctly and the report is already published to Tableau Server, or you are using Tableau Desktop installed on the same server.

FYI: When you start to actually get a connection to the server, you should either connect successfully or your errors will change to something like: 'psql: FATAL: password authentication failed for user readonly' or 'psql: FATAL: no pg_hba.conf entry for host "", user "readonly", database "workgroup", SSL off'

[sanjeevsuri]

As a matter of fact I did install Tableau Desktop on the same system where I have Tableau Server installed. So I have TabMon, Tableau Desktop and Tableau Server, all installed on the same server. I did add a Firewall rule to allow TCP connections on port 8060 from "Any" application Rebooted the machine, started the services and still getting

could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 8060? could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 8060?

[sanjeevsuri]

I figure this is not a TabMon issue per say. I'll try coordinating with Tableau support to resolve the connection issue. Thank you for your help.

[sanjeevsuri]

Just a quick update. Since we are in a clustered environment, I figured the postgres repository sits on one of the worker nodes. In order to access "What's going on" Dashboard, the connection had to be directed to the worker node instead of the primary node. That resolved the issue.

[danjrahm]

Hello,

Thanks for the update! I'm glad you were able to resolve the issue. If you have any other questions or issues please let me know!

Thanks, Dan