Postgres

This video is great, very helpful. I'm running into an issue when the lesson proceeds to setting up a role for the Vagrant user (~38min the video).

When I enter 'sudo su postgres' I get the following returned: 'Unknown id: postgres'

I've followed all the steps without any major issues up this point, so wondering if I just missed something when setting up Vagrant, but I'm not totally sure. Any suggestions?

Sorry You must be a logged in, registered user to answer a question.

Answers

I ran into the same thing. Turns out that Postgresql was never installed. I had to run the following:

'sudo apt-get install postgresql postgresql-server-dev-9.1'

Jeff Self on
Thanks for the tip Jeff! If I can ever get my VM up and running again, I'll give this a try.
Koji on

I have no idea how you could get the VM without the postgres user. Are there any PostgreSQL processes running (you can check with ps -ef | grep post, you should see at least postman and a few others)? I'm wondering if, perhaps, your VM didn't build correctly.

kennethlove (Staff) on
Yup, looks like my BIOS settings need a change to allow my CPU to allow for VMs. Not sure why that got switched, but seems to have taken care of my main problem (postgres issues were just a symptom)
Koji on
I'm wondering that too, actually. So I decided to get back and start over. Now when I try running 'vagrant up' I get the "VM failed to remain in the 'running' state while attempting to boot" error. So my VM is not loading up anymore, which is weird because it ran fine the first time. I've tried uninstalling and realoading the VM, but it's still giving me the error. It makes me thing something changed on my system (Windows 7), but not sure what that could be.
Koji on