s.PGSQL.5432 file issue is the root cause of your problem, specifying the socket file location on the psql command-line is probably the most straightforward workaround. A tool like locate, find, etc., may be used in conjunction with sudo or by the root user. If unix_socket_directory is pointing somewhere other than /tmp, then various workarounds exist.Īlternatively, and presuming that the server is running, one might try to locate the socket file without looking in the nf file, though this might make it a bit harder to address permissions, port, etc. Since the error message referenced specifically mentions the socket file, look most closely at unix_socket_directory, unix_socket_group, and unix_socket_permissions. It may be wise to open your nf file and see if the listen_addresses, port, unix_socket_directory, unix_socket_group, and unix_socket_permissions settings might be a source of issues. Do not remove the postmaster.pid file without making sure the database is not running, and note that removing the postmaster.pid file without starting the database is pointless.
If the postmaster is not running, remove the postmaster.pid file and restart the database. Use a command like ( netstat -ln ps -ef ) | egrep '(postgres)|(postmaster)|(5432)' to try to determine whether or not an instance of the postgres server is running.
0 kommentar(er)
