Waiting for postgres to be available.

pi-node / instructions

266 stars 190 forks source link

Waiting for postgres to be available. #128

Closed remzicirit closed 3 years ago

remzicirit commented 3 years ago

I see in the logs it is repeating this message and Node troubleshooting page show this

Nothing is written postgres logs

I am not sure if it is running

ihatejam commented 3 years ago

Install it on Windows 10 (latest build). I don't know anyone who got past the point you're at on Windows Server. There are historical issues with running a Linux container under Docker on Windows Server. You really don't need a server class setup for this.

remzicirit commented 3 years ago

I finally gave up on windows 2019 server and switched to Windows 10 pro. I made it work in windows 2019 server by installing docker first , like you said it is unstable.

remzicirit commented 3 years ago

jus quick question after reinstall with windows 10 Pro, all previous settings are gone. Previous availability rest to zero and restoring user.conf should I just wait for consensus container to to be downloaded and run Thanks

ihatejam commented 3 years ago

I'd go through the port checker process again, step-by-step just to be sure - Cos, if you're already a node candidate, when you click to move on after the port-check, it should request a download of the consensus container at that point as far as I can remember. Also would not hurt to check with ipfingerprints to see if your port-forwarding is fine.

If you've already done that, then try leaving it as-is for a few days (in case you're back to having to show your availability as a possible node), in which case the consensus container will be dropped onto your setup later on.

remzicirit commented 3 years ago

Thank you interesting Jfingerprints shows port is open

and container shows they are open

but port check randomly fails, it speins and spins forever and sometimes comes back says 1 or 2 ports not open as you can see , ifingerprinets and netstat container status all says it is open

nathusius commented 3 years ago

I could never get any results at all from the ports checker, just two ticks and a continuously spinning arrow for pinging, but I am now running the node just fine! If ipfingerprints says all ports are open then you are all good, just leave it running (24/7 if possible) and hope to get picked up soon. Node diagnostics are very suspect and can seem to imply that you have a problem which isn't actually there, so do yourself a BIG favour and just ignore that, as I wasted literally days trying to figure out a non-exisitent issue, doh!! ;-)