Обсуждение: postgres and webmin
Greetings, I am trying to setup postgres and postfix using webmin. I am following this guide: http://gentoo-wiki.com/HOWTO_Email:_A_Complete_Virtual_System_-_Postfix_to_Postgres I received the following in the postgres db section of webmin: select * from pg_database order by datname failed : no pg_hba.conf entry for host "[local]", user "postgres", database "template1", SSL off I sadly have no clue on how to go by fixing this. Please help :) It talks about this error in the guide. But it really does not tell you how to fix it specifically. I don't even see a section in the area specified for the authentication they are suggesting. Operating system Gentoo Linux Webmin version 1.350 I believe the problem is in this section. # "local" is for Unix domain socket connections only host all all 10.2.0.202 255.255.255.255 trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: host all all ::1/128 trust I could be wrong. Please help the newb.
2007/6/27, Danyelle Gragsone <ladynikon@gmail.com>:
# 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
# (autovacuum, daily cronjob, replication, and similar tasks).
#
# Database administrative login by UNIX sockets
local all postgres ident sameuser
--
William Leite Araújo
Estudante de paternidade - 13a semana
Greetings,
I am trying to setup postgres and postfix using webmin. I am
following this guide:
http://gentoo-wiki.com/HOWTO_Email:_A_Complete_Virtual_System_-_Postfix_to_Postgres
I received the following in the postgres db section of webmin:
select * from pg_database order by datname failed : no pg_hba.conf
entry for host "[local]", user "postgres", database "template1", SSL
off
I sadly have no clue on how to go by fixing this. Please help :) It
talks about this error in the guide. But it really does not tell you
how to fix it specifically. I don't even see a section in the area
specified for the authentication they are suggesting.
Operating system Gentoo Linux
Webmin version 1.350
I believe the problem is in this section.
# "local" is for Unix domain socket connections only
# 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
# (autovacuum, daily cronjob, replication, and similar tasks).
#
# Database administrative login by UNIX sockets
local all postgres ident sameuser
host all all 10.2.0.202 255.255.255.255 trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
I could be wrong. Please help the newb.
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
--
William Leite Araújo
Estudante de paternidade - 13a semana
I am sorry William but you lost me. I haven't disabled anything have I? On 6/27/07, William Leite Araújo <william.bh@gmail.com> wrote: > 2007/6/27, Danyelle Gragsone <ladynikon@gmail.com>: > > Greetings, > > > > I am trying to setup postgres and postfix using webmin. I am > > following this guide: > > > http://gentoo-wiki.com/HOWTO_Email:_A_Complete_Virtual_System_-_Postfix_to_Postgres > > > > I received the following in the postgres db section of webmin: > > select * from pg_database order by datname failed : no pg_hba.conf > > entry for host "[local]", user "postgres", database "template1", SSL > > off > > > > I sadly have no clue on how to go by fixing this. Please help :) It > > talks about this error in the guide. But it really does not tell you > > how to fix it specifically. I don't even see a section in the area > > specified for the authentication they are suggesting. > > > > Operating system Gentoo Linux > > Webmin version 1.350 > > > > I believe the problem is in this section. > > # "local" is for Unix domain socket connections only > > # 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 > # (autovacuum, daily cronjob, replication, and similar tasks). > # > # Database administrative login by UNIX sockets > local all postgres ident > sameuser > > > > host all all 10.2.0.202 255.255.255.255 trust > > # IPv4 local connections: > > host all all 127.0.0.1/32 trust > > # IPv6 local connections: > > host all all ::1/128 trust > > > > I could be wrong. Please help the newb. > > > > ---------------------------(end of > broadcast)--------------------------- > > TIP 3: Have you checked our extensive FAQ? > > > > http://www.postgresql.org/docs/faq > > > > > > -- > William Leite Araújo > Estudante de paternidade - 13a semana
On 6/28/07, Danyelle Gragsone <ladynikon@gmail.com> wrote: > I am sorry William but you lost me. I haven't disabled anything have I? Hard to say w/o seeing the WHOLE file. You're looking in the wrong section. What you need to make sure is that the line William posted *isn't* commented out. Cheers, Andrej -- Please don't top post, and don't use HTML e-Mail :} Make your quotes concise. http://www.american.edu/econ/notes/htmlmail.htm
BEFORE # TYPE DATABASE USER CIDR-ADDRESS METHOD #"local" is for Unix domain socket connections only host template1 postfix, postfixadmin all 10.2.0.202 255.255.255.0 trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: #host all all ::1/128 trust AFTER # TYPE DATABASE USER CIDR-ADDRESS METHOD "local" is for Unix domain socket connections only host template1 postfix, postfixadmin all 10.2.0.202 255.255.255.0 trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: #host all all ::1/128 trust You mean like this? On 6/27/07, Andrej Ricnik-Bay <andrej.groups@gmail.com> wrote: > On 6/28/07, Danyelle Gragsone <ladynikon@gmail.com> wrote: > > I am sorry William but you lost me. I haven't disabled anything have I? > Hard to say w/o seeing the WHOLE file. You're looking in the > wrong section. > > What you need to make sure is that the line William posted > *isn't* commented out. > > > Cheers, > Andrej > > -- > Please don't top post, and don't use HTML e-Mail :} Make your quotes concise. > > http://www.american.edu/econ/notes/htmlmail.htm >
On 6/28/07, Danyelle Gragsone <ladynikon@gmail.com> wrote: > BEFORE > # TYPE DATABASE USER CIDR-ADDRESS METHOD > > #"local" is for Unix domain socket connections only > host template1 postfix, postfixadmin all 10.2.0.202 255.255.255.0 trust > # IPv4 local connections: > host all all 127.0.0.1/32 trust > # IPv6 local connections: > #host all all ::1/128 trust > > AFTER > > # TYPE DATABASE USER CIDR-ADDRESS METHOD > > "local" is for Unix domain socket connections only > host template1 postfix, postfixadmin all 10.2.0.202 255.255.255.0 trust > # IPv4 local connections: > host all all 127.0.0.1/32 trust > # IPv6 local connections: > #host all all ::1/128 trust > > You mean like this? Firstly I fail to see the difference between the before and after. Secondly you don't have a line that begins with local. Add the following line to your file (was the stuff you just posted the entire file?) and restart postgres. local all postgres ident sameuser Thirdly you're still top-posting :} Cheers, Andrej -- Please don't top post, and don't use HTML e-Mail :} Make your quotes concise. http://www.american.edu/econ/notes/htmlmail.htm
Here is the entire file. # PostgreSQL Client Authentication Configuration File # =================================================== # # Refer to the PostgreSQL Administrator's Guide, chapter "Client # Authentication" for a complete description. 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 [OPTION] # host DATABASE USER CIDR-ADDRESS METHOD [OPTION] # hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION] # hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION] # # (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", "samegroup", 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", "crypt", "password", # "krb4", "krb5", "ident", or "pam". Note that "password" sends passwords # in clear text; "md5" is preferred since it sends encrypted passwords. # # OPTION is the ident map or the name of the PAM service, depending on METHOD. # # Database and user names containing spaces, commas, quotes and other special # characters must be quoted. Quoting one of the keywords "all", "sameuser" or # "samegroup" 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 CIDR-ADDRESS METHOD #local is for Unix domain socket connections only host template1 postfix, postfixadmin all 10.2.0.202 255.255.255.0 trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: #host all all ::1/128 trust Could someone please take a look at this and tell me what I am doing wrong. Apparently I have something commented that I shouldn't but I don't know what that is. Sorry if I sound like a complete moron.. but I am trying to learn. Thanks, Danyelle
On 6/28/07, Danyelle Gragsone <ladynikon@gmail.com> wrote: > Here is the entire file. > Could someone please take a look at this and tell me what I am doing > wrong. Apparently I have something commented that I shouldn't but I > don't know what that is. Sorry if I sound like a complete moron.. but > I am trying to learn. The line you're missing isn't commented out, it's not there at all. Just add it to the file and restart postgres. local all postgres ident sameuser Those lines that have a "local" in them in your file are using IP rather than the unix socket. > Thanks, > Danyelle Cheers, Andrej -- Please don't top post, and don't use HTML e-Mail :} Make your quotes concise. http://www.american.edu/econ/notes/htmlmail.htm
Amazing how one little line.. makes everything sad. Now all I have to do is figure out how to login. My old username and password no longer works.. thanks for helping!
On 6/28/07, Danyelle Gragsone <ladynikon@gmail.com> wrote: > Now all I have to do is figure out how to login. My old username and > password no longer works.. So you were able to connect to the database with webmin before this change? In that case you may want a similar line for your own user account (rather than the postgres one you just added) and make the authorisation whatever you used in the host based statement. > thanks for helping! Cheers, Andrej -- Please don't top post, and don't use HTML e-Mail :} Make your quotes concise. http://www.american.edu/econ/notes/htmlmail.htm
Yes, That was the odd thing about it. All I did was add the ip address. I will have to change my postgres password cause I can't remember it. bleh..
yay its fixed. How do I make the topic solved? Danyelle