[CB-lug] configurare postgres
Francesco Steno
overdrive@linux.it
Dom 14 Ott 2007 16:22:40 CEST
Il giorno 14/ott/07, alle ore 14:46, angelo morrone ha scritto:
> avvio su postgres /install_db.sh
>
> psql: impossibile connettersi al server: Connessione rifiutata
> Controllare che il server all'indirizzo "linux-suse" sia in
> funzione
> e che accetti connessioni TCP/IP sulla porta 5432?
[cut]
mi mandi l'output di:
ifconfig
e del comando:
hostname
??
grazie
> dopo un po di prove ho scoperto che posgresql è sempre in esecuzione
puoi essere piu' preciso ?
cosa ti fa pensare che sia sempre in esecuzione?
se stoppi il server, non ottieni il risultato voluto ???
>
> cosi ho continuato a provare e riprovare per far funzionare promogest
> cosi apro gedit conf.sh
> #!/bin/sh
>
> # Temporary directory
> TMP=/tmp
> CAT=/bin/cat
> # Postgres createlang command
> CREATELANG=/usr/bin/createlang
> # Postgres client sql
> PSQL=/usr/bin/psql
> # Default database user
> DB_USER=promoadmin
> # Default user password
> DB_PASS=admin
> # user "postgres" password
> ADMIN_PASSWORD=
> # Database server address
> DB_HOST=linux-suse
> # Database name
> DB_NAME=promogest_nightly
>
> poi apro gedit /var/lib/pgsql/data/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:
[cut]
inserisci in questo file, la seguente riga:
linux-suse promogest_nightly promoadmin 192.168.1.14/32 trust
> #
> # local DATABASE USER METHOD [OPTION]
>
> linux-suse promogest_nightly promoadmin 192.168.1.14
> 255.255.255.254 trust
cancella questa riga (questa sopra :) )
>
> # 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", "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", "crypt", "password",
> # "krb5", "ident", "pam" or "ldap". 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
> # "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.
> #
>
>
>
> # TYPE DATABASE USER CIDR-ADDRESS METHOD
>
> # "local" is for Unix domain socket connections only
> local all all ident sameuser
queta riga commentala (aggiungendo un # )
> # IPv4 local connections:
> host all all 127.0.0.1/32 ident sameuser
commenta anche questa
> # IPv6 local connections:
> host all all ::1/128 ident sameuser
e questa
>
> # PostgreSQL Client Authentication Configuration File
> # ===================================================
questo cose' ? un altro file ???
oppure la continua? del precedente ???
> # Refer to the "Client Authentication" section in the
> # PostgreSQL documentation for a complete description
> # of this file. A short synopsis follows.
[cut]
....
sostituisci la riga che ti ho detto.
riavvia il server
e lancia l'installer.
Saluti
Francesco Steno aka "oVERDRIVE"
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-generated by /dev/over-=-=-=-=-=-=-=-=-=-=
oVERDRIVE
<overdrive@OpenGeeks.it><overdrive@BitchX.it><overdrive@Linux.it>
GnuPG Public Key: http://cb.linux.it/lug/key/overdrive.asc
Key Fingerprint: 146A E13D 9E68 3B96 40FB 11F5 9A10 2D1F 3973 C203
Maggiori informazioni sulla lista
Lugcb