estão com senha sim......no termial psql esta assim
postgres=# \du
Lista de roles
Nome da role | Atributos | Membro de
--------------+---------------+-----------
postgres | Super-usuário | {}
: Cria role
: Cria BD
remessa | | {}
Em 3 de maio de 2010 14:02, <[email protected]> escreveu:
> Anderson
>
> O seu usuario postgresql tem senha no banco?
> pois o tipo e md5, o que requer a senha
>
> se nao tem, vc pode fazer o seguinte
>
> altere o metodo para trust
> reinicie o servico
> logue-se no banco e atribua uma senha ao usuario postgresql,
> altere novamente de trust para md5
> reinicie o banco
>
> []s
> Luiz
>
> > segue o pg_hba.conf
> >
> >
> > # 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 CIDR-ADDRESS METHOD [OPTIONS]
> > # hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
> > # hostnossl DATABASE USER CIDR-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", a database name, or
> > # a comma-separated list thereof.
> > #
> > # 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.
> > #
> > # CIDR-ADDRESS specifies the set of hosts the record matches.
> > # 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. Alternatively, you can
> > write
> > # an IP address and netmask in separate columns to specify the set of
> > hosts.
> > #
> > # METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
> > "krb5",
> > # "ident", "pam", "ldap" 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"
> > or
> > # "samerole" 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.
> > #
> >
> >
> >
> >
> > # DO NOT DISABLE!
> > # If you change this first entry you will need to make sure that the
> > # database
> > # super user can access the database using some other method.
> > # Noninteractive
> > # access to all databases is required during automatic maintenance
> > # (custom daily cronjobs, replication, and similar tasks).
> > #
> >
> > # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
> > local all all md5
> > host all all 127.0.0.1 255.255.255.255 md5
> > host remessa remessa 10.14.219.158 255.255.255.255 md5
> >
> > # IPv4-style local connections:
> > host all all 127.0.0.1 255.255.255.255 md5
> > host remessa remessa 10.14.219.158 255.255.255.255 md5
> >
> > # IPv6-style local connections:
> >
> >
> > Em 3 de maio de 2010 13:53, Danilo [INFORTECH]
> > <[email protected]>escreveu:
> >
> >> Como está configurado o pg_hba.conf?
> >>
> >> ----- Original Message -----
> >> *From:* Anderson <[email protected]>
> >> *To:* Comunidade PostgreSQL
> >> Brasileira<[email protected]>
> >> *Sent:* Monday, May 03, 2010 1:43 PM
> >> *Subject:* [pgbr-geral] usuário postgres no ubuntu não acessa base
> >>
> >> pessoal boa tarde, utilizo o postgres no debian sem problemas, faço
> >> minhas
> >> aplicação se conectarem ao banco através do usuário postgres, porem com
> >> a
> >> instalação no ubuntu tive os seguintes problemas:
> >>
> >>
> >> Warning: pg_connect(): Unable to connect to PostgreSQL server: FATAL:
> >> nenhuma entrada no pg_hba.conf para m?quina "::1", usu?rio "remessa",
> >> banco
> >> de dados "remessa", SSL habilitado FATAL: nenhuma entrada no pg_hba.conf
> >> para m?quina "::1", usu?rio "remessa", banco de dados "remessa", SSL
> >> desabilitado in /var/www/remessa/SQL/coneccao.php on line 3
> >>
> >> configuração:
> >> versão: 8.4
> >> ubuntu 10.4
> >> apache 2.2
> >> php 5
> >>
> >>
> >> nem imagino onde possa estar o erro, se alguém puder me dar uma luz
> >> agradeço de coração.
> >>
> >> Anderson.
> >>
> >> ------------------------------
> >>
> >> _______________________________________________
> >> pgbr-geral mailing list
> >> [email protected]
> >> https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
> >>
> >>
> >> _______________________________________________
> >> pgbr-geral mailing list
> >> [email protected]
> >> https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
> >>
> >>
> > _______________________________________________
> > pgbr-geral mailing list
> > [email protected]
> > https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
> >
>
>
> _______________________________________________
> pgbr-geral mailing list
> [email protected]
> https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
>
_______________________________________________
pgbr-geral mailing list
[email protected]
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
