OpenSaas setup 'Role postgres does not exist'
Hi! I'm a bit stuck on the initial steps for openSaaS. Running on a fresh Ubuntu 22.04 VPS and following the Getting Started Docs. When doing 'wasp db migrate-dev' it takes forever(~40min now), I switched to the other terminal running the DB and can see error messages with 'Role postgres does not exist ' and 'password authentication failed for user "Postgres"'. I have done zero modifications, just following along the guide and not sure how to proceed here, new to Wasp and not sure what to adjust. Any tips appreciated - thanks!
36 Replies
Edit: i added the DB log
An update, I did a reboot and restart everything. Now after a few minutes getting a new error, saying
npm install failed: project setup failed with exit code -9
I guess will try to install npm manually?
Wohooo @wacko, you just became a Waspeteer level 1!
Seems npm is already installed, so very confused at this point..
Retried, now getting this
hmm have you checked the Node version?
won't be online now anymore, sorry, but can check more tmrw
Yes it's v18.19.1 .Had installed v14 previously, noticed it needs higher version so installed v18. Used snap to install/update it.
No worries!
Just a final update for today , I wiped the Snap installs of Node and reinstalled it from scratch, also cloned the template in a new directory and followed the Getting Started page again. Still got this:
Is it possible to view more detailed logs or enable debug mode? The
install failed, code -9 is not very helpful. 😕
Btw sorry if I'm spamming too much here, I thought it might be helpful to give as many details as possible, because if this case is fixed it will improve the getting started experience for others as well.@wacko Don't feel like you are spaming when giving use extra info to use to debug! Good job on reporting everything.
Okay, let's try the following list of steps to get more info:
1. Run
wasp clean to remove all the build artefacts
2. Run wasp db migrate-dev and see if that helps
If that doesn't work, let's try running the following:
1. wasp clean
2. wasp compile (internal command which won't start the project)
3. Go into the folder .wasp/out/web-app and run npm install there
4. Go into the folder .wasp/out/server and run npm install there
We are simulating a bit what Wasp is doing usually on its own just to see if we see some more error messages 😄Hi @miho !
Thanks for the tips. I just tried
wasp clean and wasp db migrate-dev and it got stuck on this message repeating for 15min '[ Wasp ] You've been waiting so patiently, just wait a little longer (for the installation to finish)...'
I stopped it, then tried wasp clean again and wasp compile. It was running for 10min, then gave this error message:
Btw meanwhile on my local PC I set up WSL with same ubuntu version as VPS and went the
wasp new -> saas route. And that works perfectly.
Just tried the wasp new -> saas method on the VPS box and getting the same npm install code -9 error.. So the issue must be something specific to my VPS or software config and not the saas template. Tomorrow will try to nuke the VPS and set up a new one and try it there. If there is a way to get more detailed logs than install failed please let me know.