Had same problem with psql via command line connecting and. PostgreSQL listen on your LAN instead of just on . TCP/IP connections on port 54? Port 54is bound to 127. From now on Local Address ” for port 54should change to 0. This is a typical problem when using hand-compiled or third-party. As we can see above port 54is bound to 127.
Connection refused telnet: Unable to connect to remote host. You have to configure the following two files. L 54:localhost:54someAccountname@someIPaddress sleep. Still the main problem was that I accidently changed the ports in the . Looks like postgres is only listening on localhost on ipv4/6.
LISTEN - -- tcp::1: 54:::* LISTEN. Any idea why sometimes port 54is already in used while I stopped postresql sooner in dependencies section? Change 22in your ssh invocation to some other port which is not in use. SSH port forwarding: bind: Cannot assign requested address.
Apache listening on it, and . OSError: Cannot assign requested address Freelance Python Developer. HINT: Is another postmaster already running on port 54?
No comments:
Post a Comment
Note: only a member of this blog may post a comment.