wasp start db hanging
Hi 🙂
I'm trying to start the database for the first time but the
wasp start db
command hangs:
wasp verison
0.13.2
MacOS platform
Any tips?4 Replies
Hi @Bonza. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hello! The
wasp start db
command starts a PostgreSQL database in a Docker container. If it's hanging, there could be a few reasons for this. Here are some steps you can take to troubleshoot:
1. Check if Docker is installed and running: You can do this by running docker -v
and docker info
in your terminal. If Docker is not installed, you can download it from the official Docker website (https://www.docker.com/get-started).
2. Check if port 5432 is already in use: Wasp uses port 5432 for the database. If another application is using this port, it could cause the command to hang. You can check if the port is in use and which application is using it by following the instructions in this guide (https://www.cyberciti.biz/faq/unix-linux-check-if-port-is-in-use-command/).
3. Restart Docker and your terminal: Sometimes, simply restarting Docker and your terminal can resolve the issue. If that doesn't work, you might want to try restarting your computer.
If none of these steps work, it would be helpful to know if there are any error messages being displayed in your terminal when you run the wasp start db
command. This could provide more insight into what's causing the issue.
Also, please note that there is an open issue on the Wasp GitHub page about improving the error message when the Docker daemon is not running. You can follow the progress of this issue here (https://github.com/wasp-lang/wasp/issues/1135).
I hope this helps! Let me know if you have any other questions.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Bonza, 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?Further info: docker is installed, and 5432 is not in use
the idea is actually that "wasp db start" hangs in your terminal, as long as the db is running. If you try opening another terminal window and run "wasp start" does it work?
True, but you should be getting more output after this, basically logs from the database, a bunch of them, almos immediatelly of after a couple of secs. It can take a bi tlonger if it is downlaoding postgres docker image though, so mabye that was it? @Bonza do you get any output after this, and how long have you tried waiting?