Wasp•16mo ago

Wasp can't run PostgreSQL dev database for you since port 5432 is already in use.

When i do wasp start db, it gives the following error

Wasp can't run PostgreSQL dev database for you since port 5432 is already in use.

Wasp can't run PostgreSQL dev database for you since port 5432 is already in use.

Wasp can't run PostgreSQL dev database for you since port 5432 is already in use.

Wasp can't run PostgreSQL dev database for you since port 5432 is already in use.

How come that, could i be a different wasp project that i also had which took that port?

kapa.ai•9/10/24, 4:18 PM

Hi @Sven. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

kapa.ai•9/10/24, 4:18 PM

----------------------
Yes, it's possible that the port 5432 is already occupied by another Wasp app or some other process. When Wasp runs a managed dev database (e.g., via wasp start dbwasp start db), it will run it on port 5432 by default. If that port is already in use, starting the database will fail [source (https://github.com/wasp-lang/wasp/issues/1049)].

To check what is running on port 5432, you can use the command lsof -i tcp:5432lsof -i tcp:5432 [source (🙋questionsSchedule email with sendgrid)].

Currently, Wasp does not provide an out-of-the-box solution to specify a different port for the managed dev database. However, there are discussions about potential solutions, such as offering the user the ability to specify on which port the managed dev database should start, or having Wasp automatically try different ports until one of them is free [source (https://github.com/wasp-lang/wasp/issues/1049)].

In the meantime, you can manually stop the process that is occupying port 5432 or use a different port for that process to free up port 5432 for Wasp.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•9/10/24, 4:18 PM

Sorry @Sven, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

SvenOP•9/10/24, 4:23 PM

SOLVED!

SvenOP•9/10/24, 4:23 PM

It was docker running on that port from a different project.

Filip•9/11/24, 8:50 AM

@martinsos For when you get back from vacation.

Don't know if we've already considered this, but 5432 is PSQL server's default port and is bound to cause clashes with most of the folks that use Postgres for other projects.

Would we be better off running wasp start dbwasp start db on a different port?

@Sven Thanks for the report!

SvenOP•9/11/24, 8:51 AM

No worries, maybe post questoins to often but when i solve them i try to explain how i did such that other community members can learn from it!

Mrr•9/13/24, 6:01 PM

@Wasp Team what to do if I want to work with two different projects at same time?? Any way to change the port number??

MEE6•9/13/24, 6:01 PM

Wohooo @Mrr, you just became a Waspeteer level 2!

MMrr @Wasp Team what to do if I want to work with two different projects at same time...

martinsos•9/13/24, 6:43 PM

Nope, not at the moment! You could set up your own local postgres database though and use that as a database -> so without wasp start dbwasp start db as help. We will add cusotmization of port for wasp start dbwasp start db but not yet there.

FFilip @martinsos For when you get back from vacation. Don't know if we've already con...

martinsos•9/13/24, 6:45 PM

@sodic I added the suggestion to https://github.com/wasp-lang/wasp/issues/1049 . It makes sense although I would be tempted then to solve it properly.

Mmartinsos @sodic I added the suggestion to https://github.com/wasp-lang/wasp/issues/1049 ...

Filip•9/13/24, 6:46 PM

Even for when we solve it properly (allow configuring the port), I'd still vote for a different default than 5432

FFilip Even for when we solve it properly (allow configuring the port), I'd still vote ...

martinsos•9/13/24, 6:53 PM

Makes sense to me! I guess I just copied the PG behaviour, but now when you say it, I don't see why it would have to be 5432. Ok maybe in general because by default tools that work with pg like pgadmin would expect it on port 5432. But that doesn't feel like good enough argument and this is not a "default" postgres db but a quiet specific one so specific port makes sense, yeah.

Wasp can't run PostgreSQL dev database for you since port 5432 is already in use.

Similar Threads

Similar Threads

Similar Threads