Thread: RE: [EXTERNAL] Re: Case 120011521001709 - Issues connecting to postgreSQL server

Hi Bhavika, thanks for the email. I’m including you and your team in this email thread for reference.

 

Hello PostgreSQL team,

 

I’m having difficulties connecting to our postgresql database through SSH tunneling when using the ODBC driver. I know my database connection credentials are correct because I’m able to connect to the database in DBeaver. The Microsoft team suspects an issues with postgresql and suggested I reach out. I’m ultimately trying to import data into Microsoft’s Power BI tool but it seems I need to be able to establish a connection with ODBC first.

 

Keith

 

From: Bhavika Padidala (MINDTREE LIMITED) [mailto:v-bhpadi@microsoft.com]
Sent: Friday, January 17, 2020 11:25 AM
To: Keith Yanase <keith.yanase@soterawireless.com>; Prashanth Reddy Kalvakuntla (MINDTREE LIMITED) <v-prkalv@microsoft.com>
Cc: support <support@mail.support.microsoft.com>; Vikram Ramagiri (MINDTREE LIMITED) <v-virama@microsoft.com>
Subject: RE: [EXTERNAL] Re: Case 120011521001709 - Issues connecting to postgreSQL server

 

Hello Keith,

 

I hope you are doing good J.

 

I tried calling you at +16196002517, but had no luck reaching you.

 

 As written in my previous email I just wanted to follow up with you once again, we discussed your issue with our product team and they confirmed that the issue is from PostgreSQL side, you need to get connected to ODBC Driver using SSH from PostgreSQL in order to connect to Power BI and they suggested you to raise a PostgreSQL ticket. I thought of discussing this with you over call but unfortunately couldn’t able to reach you.

 

Let me know your thoughts on this.

 

Looking forward to hearing back from you.

 

If you have any questions or concerns, please reply to this email thread.

 

 

Best Regards

Bhavika Padidala

Engineer - Microsoft Business Intelligence

Time Zone :-Pacific Standard Time

Hours of Operation: Mon - Fri 9 AM – 6 PM

Email: v-bhpadi@microsoft.com

cid:image001.png@01D59F06.51B5D970

If delay in response to your email, kindly notify to the below Operations Manager’s team for immediate attention.

MT-BAP-OM-TA@microsoft.com

 

 

From: Ankit Gawde (MINDTREE LIMITED)
Sent: Thursday, January 16, 2020 3:50 PM
To: Keith Yanase <keith.yanase@soterawireless.com>; Bhavika Padidala (MINDTREE LIMITED) <v-bhpadi@microsoft.com>; Prashanth Reddy Kalvakuntla (MINDTREE LIMITED) <v-prkalv@microsoft.com>
Cc: support <support@mail.support.microsoft.com>
Subject: RE: [EXTERNAL] Re: Case 120011521001709 - Issues connecting to postgreSQL server

 

Hello Keith,

 

Sorry for the delayed response. We were having a discussion with my Technical Advisor and we were looking in the Desktop logs. As Technical Advisor suggested, the PostGre SQL should be able to connect to the ODBC Driver without which the Power BI won’t be able to get the data. They said to reach out to PostGre SQL Team and explaining the scenario of PostGre SQL not connecting to ODBC Driver using SSH.

 

Best Regards  

Ankit Gawde

Microsoft Business Intelligence 

Time Zone:  PST (US & Canada)

Hours: 9 AM – 6 PM 

Email : v-angawd@microsoft.com 

Manager: Rizwan UL Moin Mohammed (v-momoin@microsoft.com) 

In case of any delay in response to your email or immediate assistance needed, kindly notify to the Operations Manager’s team for immediate attention. MT-BAP-OM-TA@microsoft.com 

 

From: Keith Yanase <keith.yanase@soterawireless.com>
Sent: Thursday, January 16, 2020 1:47 PM
To: Bhavika Padidala (MINDTREE LIMITED) <v-bhpadi@microsoft.com>; Prashanth Reddy Kalvakuntla (MINDTREE LIMITED) <v-prkalv@microsoft.com>; Ankit Gawde (MINDTREE LIMITED) <v-angawd@microsoft.com>
Cc: support <support@mail.support.microsoft.com>
Subject: RE: [EXTERNAL] Re: Case 120011521001709 - Issues connecting to postgreSQL server

 

I’m still unable to generate an ODBC log file with the tracing feature. Please let me know how to resolve this so I can provide the requested log files.

 

Keith

 

From: Keith Yanase [mailto:keith.yanase@soterawireless.com]
Sent: Thursday, January 16, 2020 11:55 AM
To: 'Bhavika Padidala (MINDTREE LIMITED)' <v-bhpadi@microsoft.com>; 'Prashanth Reddy Kalvakuntla (MINDTREE LIMITED)' <v-prkalv@microsoft.com>; 'Ankit Gawde (MINDTREE LIMITED)' <v-angawd@microsoft.com>
Cc: 'support' <support@mail.support.microsoft.com>
Subject: RE: [EXTERNAL] Re: Case 120011521001709 - Issues connecting to postgreSQL server

 

Hi everyone,

 

I’m having issues locating the SQL32 and SQL64 log files. When I attempted to recreate the log files I confirmed that they aren’t being generated.

Do you know why that’s happening?

 

Keith

 

-----Original Appointment-----
From: Bhavika Padidala (MINDTREE LIMITED) [mailto:v-bhpadi@microsoft.com]
Sent: Thursday, January 16, 2020 11:00 AM
To: Keith Yanase; Prashanth Reddy Kalvakuntla (MINDTREE LIMITED); Ankit Gawde (MINDTREE LIMITED)
Cc: support
Subject: [EXTERNAL] Re: Case 120011521001709 - Issues connecting to postgreSQL server
When: Thursday, January 16, 2020 11:00 AM-11:30 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Microsoft Teams Meeting

 

Hello Keith,

 

I hope you are doing good J.

 

As per our discussion, I am scheduling a teams meeting tomorrow at 11:00 AM PST.

 

Please click on the invite below to join the meeting.

 

If you have any questions or concerns, please reply to this Email thread.

________________________________________________________________________________

+1 323-849-4874   United States, Los Angeles (Toll)

Conference ID: 989 264 882#

________________________________________________________________________________

 

Best Regards

Bhavika Padidala

Engineer - Microsoft Business Intelligence

Time Zone :-Pacific Standard Time

Hours of Operation: Mon - Fri 9 AM – 6 PM

Email: v-bhpadi@microsoft.com

cid:image001.png@01D59F06.51B5D970

If delay in response to your email, kindly notify to the below Operations Manager’s team for immediate attention.

MT-BAP-OM-TA@microsoft.com

 

_____________________________________________
From: Keith Yanase [mailto:keith.yanase@soterawireless.com]
Sent: Wednesday, January 15, 2020 5:10 PM
To: Bhavika Padidala (MINDTREE LIMITED) <v-bhpadi@microsoft.com>
Cc: Vikram Ramagiri (MINDTREE LIMITED) <v-virama@microsoft.com>; support <support@mail.support.microsoft.com>
Subject: Re: [EXTERNAL] Re: Case 120011521001709 - Issues connecting to postgreSQL server

 

Yeah absolutely. I will wait for your call tomorrow.

 

Keith

 

On Wed, Jan 15, 2020 at 4:40 PM Bhavika Padidala (MINDTREE LIMITED) <v-bhpadi@microsoft.com> wrote:

Hi Keith,

 

Is it ok if I schedule a call tomorrow at 11:00 AM PST?

 

Looking forward to hearing back from you.

 

If you have any questions or concerns, please reply to this Email thread.

 

Best Regards

Bhavika Padidala

Engineer - Microsoft Business Intelligence

Time Zone :-Pacific Standard Time

Hours of Operation: Mon - Fri 9 AM – 6 PM

Email: v-bhpadi@microsoft.com

cid:image001.png@01D59F06.51B5D970

If delay in response to your email, kindly notify to the below Operations Manager’s team for immediate attention.

MT-BAP-OM-TA@microsoft.com

 

From: Keith Yanase [mailto:keith.yanase@soterawireless.com]
Sent: Wednesday, January 15, 2020 4:33 PM
To: Bhavika Padidala (MINDTREE LIMITED) <
v-bhpadi@microsoft.com>
Subject: [EXTERNAL] Re: Case 120011521001709 - Issues connecting to postgreSQL server

 

Hi Bhavika and thanks for the quick response. I just left work but I will be available tomorrow for a screen share session. You can call me at +16196002517 

 

I will be in the office between 9am to 4pm pacific time tomorrow. If I don’t pick up please leave a message and I will call you back.

 

Looking forward to resolving this with you.

 

Keith

 

On Wed, Jan 15, 2020 at 4:25 PM Bhavika Padidala (MINDTREE LIMITED) <v-bhpadi@microsoft.com> wrote:

Hello Keith,

Thank you for contacting Microsoft Support.

My name is Bhavika Padidala and I am the Microsoft Support Engineer who will be working with you on support request 120011521001709. You can reach me using the contact information in my signature. 

I hope you’re doing well J.

I tried calling you at 8584274620, but it is asking me for extension. Could you please provide me with your extension?

From the description in the support ticket, I see that you are unable to connect to a PostgreSQL server through OpenSSH..

Could you please let me know your availability for a screen share session where we can discuss more about the issue and look for an optimal way to resolve this issue as early as possible.

I’ll be looking forward to your response.

If you have any questions or concerns, please reply to this Email thread.

 

 

Best Regards

Bhavika Padidala

Engineer - Microsoft Business Intelligence

Time Zone :-Pacific Standard Time

Hours of Operation: Mon - Fri 9 AM – 6 PM

Email: v-bhpadi@microsoft.com

cid:image001.png@01D59F06.51B5D970

If delay in response to your email, kindly notify to the below Operations Manager’s team for immediate attention.

MT-BAP-OM-TA@microsoft.com

 

Attachment

Re: [EXTERNAL] Re: Case 120011521001709 - Issues connecting topostgreSQL server

From
Clemens Ladisch
Date:
Keith Yanase wrote:
> I’m having difficulties connecting to our postgresql database through
> SSH tunneling when using the ODBC driver.

Do you mean SSH or SSL?

psqlODBC has no built-in support for SSH tunneling.

I would recommend to use SSL.  But if the server allows only SSH, then
you have to manually create an SSH tunnel with OpenSSH, and tell
psqlODBC to connect to that port on localhost.

> I’m able to connect to the database in DBeaver.

As far as I can see, DBeaver's SSH support is separate from the
database drivers, i.e., DBeaver creates the SSH tunnel by itself,
and then hands off that port to the database driver.


Regards,
Clemens



Re: [EXTERNAL] Re: Case 120011521001709 - Issues connecting topostgreSQL server

From
Keith Yanase
Date:
The server only allows SSH tunneling. I’m able to establish the SSH tunnel with the command: ssh jupyter
but how do I tell psqlODBC to connect to that port?
I used pgAdmin 4 and was able to connect to the database, so I feel like I’m missing something basic. 

I’m ultimately trying to import data from the server over SSH into Microsoft’s Power BI app using its native postgresql or odbc plugin.

On Sat, Jan 18, 2020 at 2:56 AM Clemens Ladisch <clemens@ladisch.de> wrote:
Keith Yanase wrote:
> I’m having difficulties connecting to our postgresql database through
> SSH tunneling when using the ODBC driver.

Do you mean SSH or SSL?

psqlODBC has no built-in support for SSH tunneling.

I would recommend to use SSL.  But if the server allows only SSH, then
you have to manually create an SSH tunnel with OpenSSH, and tell
psqlODBC to connect to that port on localhost.

> I’m able to connect to the database in DBeaver.

As far as I can see, DBeaver's SSH support is separate from the
database drivers, i.e., DBeaver creates the SSH tunnel by itself,
and then hands off that port to the database driver.


Regards,
Clemens

Re: [EXTERNAL] Re: Case 120011521001709 - Issues connecting topostgreSQL server

From
Clemens Ladisch
Date:
Keith Yanase wrote:
> The server only allows SSH tunneling. I’m able to establish the SSH tunnel with the command: ssh jupyter
> but how do I tell psqlODBC to connect to that port?

Run "ssh -L bindaddress:localport:remoteserver:remoteport sshserver", where
"remoteserver" is the host name you want to connect to, from the point of
view of the SSH server.

So run "ssh -L localhost:5432:localhost:5432 jupyter", and tell psqlODBC to
connect to localhost:5432.


Regards,
Clemens



Re: [EXTERNAL] Re: Case 120011521001709 - Issues connecting topostgreSQL server

From
Keith Yanase
Date:
I ran the command and when I tel psqlODBC to connect to localhost:5432 I get this message in the terminal:
Channel 3: open failed: connect failed: connection refused

Are my connection settings in psqlODBC correct?
Data Source: PostgreSQL30
Database: database
Server: localhost
Port: 5432

I didn’t enter credentials (un/pw) since I’m connecting to localhost - is that a correct assumption? 

On Sun, Jan 19, 2020 at 10:58 AM Clemens Ladisch <clemens@ladisch.de> wrote:
Keith Yanase wrote:
> The server only allows SSH tunneling. I’m able to establish the SSH tunnel with the command: ssh jupyter
> but how do I tell psqlODBC to connect to that port?

Run "ssh -L bindaddress:localport:remoteserver:remoteport sshserver", where
"remoteserver" is the host name you want to connect to, from the point of
view of the SSH server.

So run "ssh -L localhost:5432:localhost:5432 jupyter", and tell psqlODBC to
connect to localhost:5432.


Regards,
Clemens

Re: [EXTERNAL] Re: Case 120011521001709 - Issues connecting topostgreSQL server

From
Clemens Ladisch
Date:
Keith Yanase wrote:
> I ran the command and when I tel psqlODBC to connect to localhost:5432 I get this message in the terminal:
> Channel 3: open failed: connect failed: connection refused

Does the PostgreSQL server run on the "jupyter" host?

Is the database configured to listen on "localhost" or "127.0.0.1"?
In the latter case, use "ssh -L localhost:5432:127.0.0.1:5432 jupyter".


Regards,
Clemens



Re: [EXTERNAL] Re: Case 120011521001709 - Issues connecting topostgreSQL server

From
Keith Yanase
Date:
The PostgreSQL server runs on amazon cloud server (RDS). Jupyter hosts the SSH tunnel.

I tried the following:
ssh -L localhost:5432:127.0.01:5432 jupyter

Still getting this error when attempting to connect to localhost:5432 in psqlODBC.
channel 3: open failed: connect failed: Connection refused

The database resides in amazon, which is accessed on my computer through an SSH tunnel hosted on jupyter.
I don't have access to the database configurations, but is there a way I can find out what the database is configured to listen on?

On Sun, Jan 19, 2020 at 12:41 PM Clemens Ladisch <clemens@ladisch.de> wrote:
Keith Yanase wrote:
> I ran the command and when I tel psqlODBC to connect to localhost:5432 I get this message in the terminal:
> Channel 3: open failed: connect failed: connection refused

Does the PostgreSQL server run on the "jupyter" host?

Is the database configured to listen on "localhost" or "127.0.0.1"?
In the latter case, use "ssh -L localhost:5432:127.0.0.1:5432 jupyter".


Regards,
Clemens