cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BTP PostgreSQL instance not reachable

Steven_UM
Contributor
0 Kudos
754

Hi,

Recently my EU trial account expired so I had to create a new one - US based now. When I tried to create a new postgresql trial instance then I got some failure error that the service could not be created. I waited a couple of days and retried and was then able to create an instance.

Now when I try to deploy my MTA - including cds-dbm deploy - then the deploy service fails with a 'TCP time out connection error' - it seems not able to connect.

When I try to connect myself using an 'adminer' instance then I am getting the same error - 'SQLSTATE[08006] [7] connection to server at "postgres-....cqryblsdrbcs.us-east-1.rds.amazonaws.com" (10.16.70.139), port 4397 failed: Connection refused Is the server running on that host and accepting TCP/IP connections?'.

I deleted and recreated already an instance. Checked all documentation but I can't find any reason why it should not work.

I have a colleague who did exactly the same and there is works ( EDIT - he has an existing instance that was created like a month ago - the problem seems to happen only for newly created instances ). Anyone any clues ?

Thanks,

Steven

gregorw
Active Contributor

Hi Steven,

I've just tried in a freshly created trial subaccount and I face the same issue:

[cds-dbm] - starting delta database deployment of service db
cds-dbm deploy [services]
Dynamically identifies changes in your cds data model and deploys them to the
database
Options:
--help           Show help                                       [boolean]
--version        Show version number                             [boolean]
-s, --service                                                [default: ["db"]]
-a, --auto-undeploy
-d, --dry
-l, --load-via
-c, --create-db
Error: connect ETIMEDOUT 10.16.50.120:4402
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1237:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '10.16.50.120',
port: 4402
}
npm notice
npm notice New minor version of npm available! 8.12.1 -> 8.19.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
npm notice Run `npm install -g npm@8.19.2` to update!
npm notice
Exit status 1

the issue was also reported as an issue for my pg-beershop project:

Deploying to BTP Trial Account #323

Hope that manjunath.baburao can jump in here and does the needful to get the firewall issue fixed.

Best Regards
Gregor

manjunath_b
Advisor
Advisor

Hi abhik.gupta,

Can someone from the team take a look and support colleagues with the issue?

Best regards,

Manju

Steven_UM
Contributor
0 Kudos

Cheers gregor.wolf for trying this out as well 🙂

Steven_UM
Contributor
0 Kudos

Hi manjunath.baburao, any potential updates at SAP about this issue ? We are a week further and still no access ... thanks. Steven

manjunath_b
Advisor
Advisor

Hi Steven,

Apologies for the delay. I am trying to get the relevant team involved to investiage and provide right guidance.

Best regards,

Manju

View Entire Topic
0 Kudos

Hi Steven and Gregor,

We expect to fix the connectivity issues on trial by end of the day. Please check and let us know if your application can connect to the Postgres instance after a day or so.

Thanks

Abhik

Steven_UM
Contributor

Hi abhik.gupta

I removed my existing Postgresql instance, created a new one and redeployed.

I can confirm that it works now ... thanks !

Kr,

Steven