Thanks Tom. found the problem. On Tue, Mar 7, 2023 at 8:28 PM Tom Lane <t...@sss.pgh.pa.us> wrote:
> Siddharth Jain <siddh...@gmail.com> writes: > > But when I try to start the server I get this: > > > 2023-03-07 17:16:43.228 PST [25925] LOG: could not bind IPv6 address > > "::1": Address already in use > > 2023-03-07 17:16:43.228 PST [25925] HINT: Is another postmaster already > > running on port 5432? If not, wait a few seconds and retry. > > 2023-03-07 17:16:43.228 PST [25925] LOG: could not bind IPv4 address > > "127.0.0.1": Address already in use > > 2023-03-07 17:16:43.228 PST [25925] HINT: Is another postmaster already > > running on port 5432? If not, wait a few seconds and retry. > > That's pretty clear I think: the ports are already bound. > > > I ran: > > netstat -ln -p tcp | grep 5432 > > and there is no output. > > This is the wrong incantation for this purpose. Try > > netstat -an -p tcp | grep 5432 > > I expect you'll see a couple of ports in LISTEN state. Unfortunately, > netstat is not much help at locating the processes listening to such > ports. This might be more help: > > lsof -n | grep 5432 > > regards, tom lane >
