psql: FATAL: role "vagrant" does not exist

LogicLooking

I created a vagrant instance and I am getting this error every time I try and do psql in the terminal How would Fix it. the error is as states:

psql: FATAL: role "vagrant" does not exist

I thought vagrant takes care of this? This is my vagrant file:

Vagrant.require_plugin "vagrant-omnibus"
Vagrant.require_plugin "vagrant-berkshelf"

Vagrant.configure(2) do |config|

  # Box config
  config.vm.box = 'precise64'
  config.vm.box_url = 'http://files.vagrantup.com/precise64.box'

  # Plugin config
  config.omnibus.chef_version = :latest
  config.berkshelf.enabled = true

  # Network config
  config.vm.network :forwarded_port, guest: 3000, host: 3000

  # Virtual config
  config.vm.provider(:virtualbox) do |vb|
    vb.customize [
      "modifyvm", :id,
      "--memory", "1024",
      "--cpus",   "4"
    ]
  end

  # Provisioner config
  config.vm.provision :chef_solo do |chef|
    chef.add_recipe 'apt'
    chef.add_recipe 'postgresql::client'
    chef.add_recipe 'postgresql::server'
    chef.add_recipe 'build-essential'
    chef.add_recipe 'rvm::system'
    chef.add_recipe 'git'
    chef.json = {
      :postgresql => {
        :version => '9.3'
      },
      "postgresql" => {
        "password" => {
          "postgres" => "kshgfi3ret3hihjfbkivtbo3ity835"
        }
      },
      "database" => {
        "create" => ["aisisplatform"]
      },
      :git   => {
        :prefix => "/usr/local"
      },
      :rvm => {
        'rubies' => [ 'ruby-2.1.0' ],
        'default_ruby' => 'ruby-2.1.0',
        'vagrant' => {
          :system_chef_solo => '/usr/bin/chef-solo'
        }
      },
    }
  end
end
ivalkeen

You don't have vagrant user in postgres, and when you run psql, it tries to login as vagrant user (the same name as OS user). You may try something like:

psql -U postgres -h localhost

to login as postgres user, with password specified in your Vagrantfile for postgresq user.

Then, you have several options:

  • Export PGUSER and PGHOST environment variables to set user and host (psql without parameters will use these values). You may also want to use .pgpass file to avoid entering password on each psql execute.

  • Modify Vagrantfile to create vagrant user in postgres with password

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

From Dev

psql: FATAL: role "vagrant" does not exist

From Java

psql: FATAL: role "postgres" does not exist

From Dev

Postgresql: FATAL: role does not exist

From Dev

FATAL: role "root" does not exist

From Java

psql: FATAL: database "<user>" does not exist

From Dev

psql: FATAL: database "Morne Nel" does not exist

From Dev

psql: FATAL: database "Morne Nel" does not exist

From Dev

Heroku pg:psql command throwing psql: FATAL: database "'" does not exist

From Dev

PostgreSQL error Fatal: role “username” does not exist

From Java

PostgreSQL error: Fatal: role "username" does not exist

From Dev

PG::ConnectionBad FATAL: role "Myname" does not exist

From Dev

PG::ConnectionBad FATAL: role "Myname" does not exist

From Dev

Import psql file trows "ERROR: role "userabc" does not exist"

From Dev

Could not connect to database postgres: FATAL: role"_postgres" does not exist

From Dev

psql: FATAL: too many connections for role

From Dev

FATAL: database does not exist

From Dev

PSQL Error: function does not exist

From Dev

"/vagrant" shared folder does not exist

From Dev

"/vagrant" shared folder does not exist

From Dev

Fatal: Heroku repository does not exist

From Dev

PSQL: "Error: column x does not exist"

From Dev

Postgres FATAL database does not exist Django

From Dev

Fatal Error: "key does not exist on the server"

From Dev

git clone --bare: fatal: repository does not exist

From Dev

Operational Error: FATAL: database "django" does not exist

From Dev

Postgres FATAL database does not exist Django

From Dev

postgresql jdbc: FATAL: database does not exist

From Dev

role "postgres" does not exist; cannot createuser

From Dev

PostgreSQL: Role clearly exists but does not exist?

Related Related

HotTag

Archive