Subject: Re: Re: ERROR while creating new user - could not open relation
 mapping file global/pg_filenode.map
To: Sribeiro <info@simetriastudio.com>, pgsql-sql@postgresql.org
References: <1449160418085-5876161.post@n5.nabble.com>
 <56607275.4060404@aklaver.com> <1449167361158-5876168.post@n5.nabble.com>
 <56609751.1000500@aklaver.com> <1449171498579-5876183.post@n5.nabble.com>
 <5660A1F3.1080408@aklaver.com> <1449176104539-5876192.post@n5.nabble.com>
 <5660AF6A.50305@aklaver.com> <1449177347696-5876199.post@n5.nabble.com>
 <5660B1E5.6000409@aklaver.com> <1449178022535-5876201.post@n5.nabble.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
Message-ID: <5660B6EF.8040208@aklaver.com>
Date: Thu, 3 Dec 2015 13:41:03 -0800
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <1449178022535-5876201.post@n5.nabble.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

On 12/03/2015 01:27 PM, Sribeiro wrote:
> Running that command I get:
> /psql (9.4.4)
> Type "help" for help.
>
> postgres=#/

Cool, you are connected. From the above psql prompt do:

postgres=#/\du

That will return a list of users(roles) that are set up on the database 
cluster. FYI, users(roles) are global to all databases in a Postgres 
cluster. You should see at least Serge and my guess,  with an attribute 
of Superuser. If that is the case then you can run the Rake command 
again, but be sure to change username: in config/database.yml from serge 
to Serge, usernames are case sensitive.

As to below your authentication is set up as trust across the board, 
that means no password or any other authentication. Not a desirable 
situation long term. For now while you are figuring things out you can 
probably leave alone. If you expose this database to the public I would 
spend some time at the link below before proceeding too much further:

http://www.postgresql.org/docs/9.4/interactive/client-authentication.html
>
> The contents inside the pg_hba.conf file are:
> /# PostgreSQL Client Authentication Configuration File
> # ===================================================
> #
> # Refer to the "Client Authentication" section in the PostgreSQL
> # documentation for a complete description of this file.  A short
> # synopsis follows.
> #
> # This file controls: which hosts are allowed to connect, how clients
> # are authenticated, which PostgreSQL user names they can use, which
> # databases they can access.  Records take one of these forms:
> #
> # local      DATABASE  USER  METHOD  [OPTIONS]
> # host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
> # hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
> # hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
> #
> # (The uppercase items must be replaced by actual values.)
> #
> # The first field is the connection type: "local" is a Unix-domain
> # socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
> # "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
> # plain TCP/IP socket.
> #
> # DATABASE can be "all", "sameuser", "samerole", "replication", a
> # database name, or a comma-separated list thereof. The "all"
> # keyword does not match "replication". Access to replication
> # must be enabled in a separate record (see example below).
> #
> # USER can be "all", a user name, a group name prefixed with "+", or a
> # comma-separated list thereof.  In both the DATABASE and USER fields
> # you can also write a file name prefixed with "@" to include names
> # from a separate file.
> #
> # ADDRESS specifies the set of hosts the record matches.  It can be a
> # host name, or it is made up of an IP address and a CIDR mask that is
> # an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
> # specifies the number of significant bits in the mask.  A host name
> # that starts with a dot (.) matches a suffix of the actual host name.
> # Alternatively, you can write an IP address and netmask in separate
> # columns to specify the set of hosts.  Instead of a CIDR-address, you
> # can write "samehost" to match any of the server's own IP addresses,
> # or "samenet" to match any address in any subnet that the server is
> # directly connected to.
> #
> # METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
> # "ident", "peer", "pam", "ldap", "radius" or "cert".  Note that
> # "password" sends passwords in clear text; "md5" is preferred since
> # it sends encrypted passwords.
> #
> # OPTIONS are a set of options for the authentication in the format
> # NAME=VALUE.  The available options depend on the different
> # authentication methods -- refer to the "Client Authentication"
> # section in the documentation for a list of which options are
> # available for which authentication methods.
> #
> # Database and user names containing spaces, commas, quotes and other
> # special characters must be quoted.  Quoting one of the keywords
> # "all", "sameuser", "samerole" or "replication" makes the name lose
> # its special character, and just match a database or username with
> # that name.
> #
> # This file is read on server startup and when the postmaster receives
> # a SIGHUP signal.  If you edit the file on a running system, you have
> # to SIGHUP the postmaster for the changes to take effect.  You can
> # use "pg_ctl reload" to do that.
>
> # Put your actual configuration here
> # ----------------------------------
> #
> # If you want to allow non-local connections, you need to add more
> # "host" records.  In that case you will also need to make PostgreSQL
> # listen on a non-local interface via the listen_addresses
> # configuration parameter, or via the -i or -h command line switches.
>
> # CAUTION: Configuring the system for local "trust" authentication
> # allows any local user to connect as any PostgreSQL user, including
> # the database superuser.  If you do not trust all your local users,
> # use another authentication method.
>
>
> # TYPE  DATABASE        USER            ADDRESS                 METHOD
>
> # "local" is for Unix domain socket connections only
> local   all             all                                     trust
> # IPv4 local connections:
> host    all             all             127.0.0.1/32            trust
> # IPv6 local connections:
> host    all             all             ::1/128                 trust
> # Allow replication connections from localhost, by a user with the
> # replication privilege.
> #local   replication     Serge                                trust
> #host    replication     Serge        127.0.0.1/32            trust
> #host    replication     Serge        ::1/128                 trust/
>
>
>
>
> --
> View this message in context: http://postgresql.nabble.com/ERROR-while-creating-new-user-could-not-open-relation-mapping-file-global-pg-filenode-map-tp5874842p5876201.html
> Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
>
>


-- 
Adrian Klaver
adrian.klaver@aklaver.com


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql