wasp db migrate-dev taking forever!
hello guys , does anyone here have the same problem , after i run the command it's taking hours and still not working?
2 Replies
Hi @bardh. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
It seems you're experiencing an issue with the
wasp db migrate-dev command taking an unusually long time to complete. This is a known issue that some users have encountered. Here are a few potential reasons and solutions based on the information provided:
1. Limited system resources: If you're running this on a machine with limited RAM (like an EC2 micro instance with 1GB of memory), it might cause the process to hang or take an extremely long time. Discord thread (https://discord.com/channels/686873244791210014/1217483832404611195) suggests that 1GB of RAM might not be enough for Wasp, as it runs quite a few things simultaneously.
2. Hanging during SDK building: Some users have reported that the process hangs during the "Building SDK" stage. If this is happening to you, you might need to interrupt the process and try building the SDK directly. Discord thread (https://discord.com/channels/686873244791210014/1217483832404611195)
3. Docker-related issues: The command starts a PostgreSQL database in a Docker container. Make sure Docker is installed and running correctly on your system. Discord thread (https://discord.com/channels/686873244791210014/1223569423177089093)
Here are some steps you can try:
1. Run wasp clean and then try wasp db migrate-dev again. This has helped some users. Github issue (https://discord.com/channels/686873244791210014/1203689209894928404)
2. If you're on a system with limited resources, consider upgrading your machine or using a more powerful instance.
3. Check if there are any processes using port 5432 (the default PostgreSQL port). If so, stop them before running the command.
4. Ensure you're in the correct project directory when running the command.
If the issue persists, you might want to share more details about your system configuration and the exact output you're seeing. This will help the Wasp community provide more specific assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @bardh, 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?We need more information to be able to help you. If I recall correctly, you made another post that mentioned you used WSL?