Re: php connection failure

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Tuesday, August 10th, 2021 at 3:44 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

> 1.  There is another local line with peer that you missed.
> 2.  You changed the wrong pg_hba.conf file.
>
Frow within postgresql 'psql' terminal:
SHOW hba_file;
    /etc/postgresql/9.6/main/pg_hba.conf

>     What was the path of the file you changed?
>
SHOW config_file;
    /etc/postgresql/9.6/main/postgresql.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  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.




# DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database superuser 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).
#
# Database administrative login by Unix domain socket
#local   all             postgres                                peer

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
#local   all             all                                     peer
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                peer
#host    replication     postgres        127.0.0.1/32            md5
#host    replication     postgres        ::1/128                 md5
local    cpacweb    cpaca        trust


>     What is returned when you do?:
>
>     ps ax | grep postgres
>

ps ax | grep postgres
 5844 pts/6    S+     0:00 sh -c lynx 'http://www.mail-archive.com/pgsql-general@lists.postgresql.org/msg26968.html'
 5845 pts/6    S+     0:00 lynx http://www.mail-archive.com/pgsql-general@lists.postgresql.org/msg26968.html
29573 ?        S      0:00 /usr/lib/postgresql/9.6/bin/postgres -D /var/lib/postgresql/9.6/main -c
config_file=/etc/postgresql/9.6/main/postgresql.conf
29575 ?        Ss     0:00 postgres: 9.6/main: checkpointer process
29576 ?        Ss     0:00 postgres: 9.6/main: writer process
29577 ?        Ss     0:00 postgres: 9.6/main: wal writer process
29578 ?        Ss     0:00 postgres: 9.6/main: autovacuum launcher process
29579 ?        Ss     0:00 postgres: 9.6/main: stats collector process
30245 pts/11   S+     0:00 grep postgres

>     What do you see in:
>
>     sudo vi /var/log/postgresql/postgresql-9.6-main.log
>
>     when you do a restart?
>

For sign-in today via commands below, the log file shows nothing new, only the old errors:
"
psql -d cpacweb -U cpacapsql (9.6.16)
Type "help" for help.

cpacweb=> \q
psql -d cpacweb -h localhost -U cpaca Password for user cpaca:
psql (9.6.16)
SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off)
Type "help" for help.

cpacweb=> \q
"

The connection to postgresql seems OK now (thank you), but the php web page continues to fail to connect to the
database:

"
<html>
    <head>
        Generic CPAC database
    </head>
    <body>
        <?php
            $dbconn = pg_connect("dbname=cpacweb user=cpaca host=localhost") or die("Could not connect");
            $stat = pg_connection_status($dbconn);
     if ($stat === PGSQL_CONNECTION_OK) {
         echo 'Connection status ok';
     } else {
         echo 'Connection status bad';
     }
        ?>
    </body>
</html>
"
Returns:

"
Generic CPAC database Could not connect
"