Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting 5000ms Timeout error while connecting Postgres - I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1. #636

Closed
awongCM opened this issue Dec 30, 2023 · 1 comment

Comments

@awongCM
Copy link

awongCM commented Dec 30, 2023

I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1.

I tried downgrading it to 12.16.3 but I'm running into npm build and npm migrate cli errors due to npm versioning compatibility issues. So it's still a chicken-and-egg situation for me right now.

Can anyone shed light on the permanent resolution for it despite using the latest Postgres connector library?

Originally posted by @awongCM in loopbackio/loopback-next#7182 (reply in thread)

@awongCM awongCM changed the title I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1. Getting 5000ms Timeout error while connecting Postgres - I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1. Dec 30, 2023
@awongCM
Copy link
Author

awongCM commented Dec 31, 2023

I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1.

I tried downgrading it to 12.16.3 but I'm running into npm build and npm migrate cli errors due to npm versioning compatibility issues. So it's still a chicken-and-egg situation for me right now.

Can anyone shed light on the permanent resolution for it despite using the latest Postgres connector library?

Originally posted by @awongCM in loopbackio/loopback-next#7182 (reply in thread)

Actually, don't worry about it.

I've figured out where things went wrong.

I found that I must have performed the wrong steps process of install node versioning changes between 12 and 16 on my local dev machine. So I had to redo everything from scratch again. Now the error is gone.

I have a different problem to resolve now, which is the actual db schema migration itself.

This ticket is now a non-issue.

@awongCM awongCM closed this as completed Dec 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant