[CB-lug] configurare postgres
angelo morrone
angelomorr@gmail.com
Dom 14 Ott 2007 14:46:14 CEST
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?
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?
createlang: impossibile connettersi al database promogest_nightly:
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
2007/10/14, angelo morrone <angelomorr@gmail.com>:
>
> dopo un po di prove ho scoperto che posgresql è sempre in esecuzione 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:
> #
> # local DATABASE USER METHOD [OPTION]
>
> linux-suse promogest_nightly promoadmin 192.168.1.14 255.255.255.254trust
> - Mostra testo tra virgolette -
>
> # 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
> # IPv4 local connections:
> host all all 127.0.0.1/32 ident sameuser
> # IPv6 local connections:
> host all all ::1/128 ident sameuser
>
> # 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 [OPTION]
>
> linux-suse promogest_nightly promoadmin 192.168.1.14 255.255.255.254trust
> - Mostra testo tra virgolette -
>
> # 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
> # IPv4 local connections:
> host all all 127.0.0.1/32 ident sameuser
> # IPv6 local connections:
> host all all ::1/128 ident sameuser
>
> # 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 [OPTION]
>
> linux-suse promogest_nightly promoadmin 192.168.1.14 255.255.255.254trust
> segue ---->
>
> 2007/10/13, angelo morrone < angelomorr@gmail.com>:
> >
> > dopo un po di prove ho scoperto che posgresql è sempre in esecuzione
> > 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:
> > #
> > # local DATABASE USER METHOD [OPTION]
> >
> > linux-suse promogest_nightly promoadmin 192.168.1.14 255.255.255.254trust
> > # 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
> > # IPv4 local connections:
> > host all all 127.0.0.1/32 ident sameuser
> > # IPv6 local connections:
> > host all all ::1/128 ident sameuser
> >
> > # 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 [OPTION]
> >
> > linux-suse promogest_nightly promoadmin 192.168.1.14 255.255.255.254trust
> > # 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
> > # IPv4 local connections:
> > host all all 127.0.0.1/32 ident sameuser
> > # IPv6 local connections:
> > host all all ::1/128 ident sameuser
> >
> > # 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 [OPTION]
> >
> > linux-suse promogest_nightly promoadmin 192.168.1.14 255.255.255.254trust
> > # 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
> > # IPv4 local connections:
> > host all all 127.0.0.1/32 ident sameuser
> > # IPv6 local connections:
> > host all all ::1/128 ident sameuser
> >
> > 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?
> > 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?
> > createlang: impossibile connettersi al database promogest_nightly:
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> > 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?
> >
> >
> > e poi lancio ./install
> > Il 12/10/07, angelo morrone < angelomorr@gmail.com> ha scritto:
> > >
> > > Stranissimo ho provato #/etc/init.d/postgresql stop, start ma la cosa
> > > strana che quando #/etc/init.d/postgresql status mi dice che è in esecuzione
> > > boooo. con #/etc/init.d/postgresql stop Shutting down PostgreSQLserver
> > > stopped
> > >
> > > done
> > >
> > > /etc/init.d/postgresql status
> > > Checking for PostgreSQL:
> > > running
> > > strano si comporta cosi perchè ho aggiornato sia il kernel che il
> > > server x?
> > > forse sono installati i pacchetti sbagliati?
> > > aiutooooooooo!!!!
> > >
> > > Il 12/10/07, Francesco Steno < overdrive@linux.it > ha scritto:
> > > >
> > > >
> > > > Il giorno 11/ott/07, alle ore 22:45, angelo morrone ha scritto:
> > > >
> > > > > Nuovo problema dopo inserito la riga linux-suse promogest_db
> > > > > promoadmin
> > > > > 192.168.1.14 255.255.255.255 trust in /var/lib/pgsql/data/
> > > > > pg_hba.conf non
> > > > > mi parte più /etc/init.d/postgresql start
> > > > > Starting PostgreSQLcould not start server
> > > > > provo cosi local promogest_db promoadmin 192.168.1.14
> > > > > 255.255.255.255 trust
> > > > > e mi dice /etc/init.d/postgresql start
> > > > > Starting PostgreSQLpg_ctl: another server may be running;
> > > > > trying to start server anyway
> > > > > pg_ctl: could not start server
> > > > > Examine the log output.
> > > >
> > > > > f
> > > > > ailed
> > > > > Come si fò?
> > > >
> > > > vuol dire che devi prima fermare il server che sta girando, e poi lo
> > > >
> > > > fai ripartire....
> > > >
> > > > #/etc/init.d/postgresql stop (ferma il server)
> > > > #/etc/init.d/postgresql start (fa partire il server)
> > > > #/etc/init.d/postgresql status (ti dice se il server e' in
> > > > esecuzione, oppure se e' fermo)
> > > > #/etc/init.d/postgresql restart (nel caso sia in esecuzione, lo
> > > > ferma
> > > > e lo fa ripartire)
> > > >
> > > > Prova cosi e fammi sapere
> > > >
> > > >
> > > > 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
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Mailing list info: http://lists.linux.it/listinfo/lugcb
> > > >
> > >
> > >
> >
>
-------------- parte successiva --------------
Un allegato HTML è stato rimosso...
URL: http://lists.linux.it/pipermail/lugcb/attachments/20071014/3ae15cb0/attachment-0001.htm
Maggiori informazioni sulla lista
Lugcb