Connection closed unexpectedly by server

[aliarsalankazmi]

Connection closed unexpectedly by server

[aliarsalankazmi]

Finding my feet by debugging as much as I can/looking up more ways to debug S4.
A call to traceback shows this:

[aliarsalankazmi]

After checking with the database admin and IT, I am being advised this might be due to proxy being utilised under the wraps by dbConnect (?)

Trying to debug now to see if this is the case (debugging is more complicated because simply using debug is not very helpful)...

[krlmlr]

Thanks. Can you connect with another client, e.g., the psql command line or a GUI?

[aliarsalankazmi]

Thanks a lot for the message, @krlmlr!

I tried telnet if that counts. I don't have others like PgAdmin just yet, but I will ask for them to be installed so I can check.
Could you also suggest how I can see under the wraps of the dbConnect method? I tried traceback but surely there will be better ways?

[aliarsalankazmi]

@krlmlr , I could not check via a GUI just yet, but I just checked with python using psycopg2.
It threw the same error (perhaps unsurprisingly as it too is based on libpq)

[krlmlr]

Thanks. I've seen cases where psql et al. works but RPostgres doesn't. Unfortunately, if both don't work, I have to ask you to troubleshoot psql or PgAdmin first.

[aliarsalankazmi]

Thanks @krlmlr

I and my IT have not been able to diagnose this issue yet.
Hopefully in the next couple of days IT will have installed a client like PgAdmin or psql for me to check. If not, then I will close this issue.

Many thanks for the patience, BTW!

[aliarsalankazmi]

Turns out the network team had assigned an incorrect security policy to my account due to which I was unable to connect.

Apologies for any hassle!

[krlmlr]

Thanks for the heads-up! Glad it works now for you.