On 8/13/21 1:36 PM, ourdiaspora wrote:
‐‐‐ Original Message ‐‐‐
On Wednesday, August 11th, 2021 at 3:13 PM, Adrian Klaver
wrote:
Are you using some form of container/VM on the machine for either server?
The machine is a chromebook, GNU/Linux via 'crouton' chroot. Is this the
po
‐‐‐ Original Message ‐‐‐
On Wednesday, August 11th, 2021 at 3:13 PM, Adrian Klaver
wrote:
>
> Are you using some form of container/VM on the machine for either server?
>
The machine is a chromebook, GNU/Linux via 'crouton' chroot. Is this the
potential cause of blockage of port 5432
On 8/11/21 10:02 AM, ourdiaspora wrote:
On Wednesday, August 11th, 2021 at 3:09 PM, Adrian Klaver
wrote:
Is the Web server/PHP app on the same machine as the Postgres server?
All programs about this question are installed on a single computer; the
intention is to test and learn first on
On Wednesday, August 11th, 2021 at 3:09 PM, Adrian Klaver
wrote:
>
> Is the Web server/PHP app on the same machine as the Postgres server?
>
All programs about this question are installed on a single computer; the
intention is to test and learn first on a local machine.
> If it is on the sa
‐‐‐ Original Message ‐‐‐
On Wednesday, August 11th, 2021 at 2:10 PM, rob stone
wrote:
>
> the call to pg_connect as a try . . . catch block so that the exact
>
Sorry but do not understand "try catch block"
>
> Are you sure postgres is configured to use port 5432?
No, but the impres
On 8/11/21 7:09 AM, Adrian Klaver wrote:
On 8/11/21 4:09 AM, ourdiaspora wrote:
‐‐‐ Original Message ‐‐‐
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 cpacw
On 8/11/21 6:10 AM, rob stone wrote:
Hello,
Why are you starting postgres with a -c option and no parameters
following?
I see:
/usr/lib/postgresql/9.6/bin/postgres -D /var/lib/postgresql/9.6/main -c
config_file=/etc/postgresql/9.6/main/postgresql.conf
This is standard for the Ubuntu pac
On 8/11/21 4:09 AM, ourdiaspora wrote:
‐‐‐ Original Message ‐‐‐
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
ourdiaspora writes:
> Installed 'nftables'.
If you didn't have nftables installed already, then it's likely that
packet filtering is being controlled by some other userland API.
Can't help you much on what that is.
regards, tom lane
Hello,
On Wed, 2021-08-11 at 11:09 +, ourdiaspora wrote:
>
>
> The connection to postgresql seems OK now (thank you), but the php
> web page continues to fail to connect to the database:
>
> "
>
>
> Generic CPAC database
>
>
>
‐‐‐ Original Message ‐‐‐
On Tuesday, August 10th, 2021 at 3:44 PM, Adrian Klaver
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/
‐‐‐ Original Message ‐‐‐
On Tuesday, August 10th, 2021 at 2:14 PM, Tom Lane wrote:
> The postgres process is listening, but this has nothing to do with
>
> whether the kernel will allow any packets to arrive there.
>
Installed 'nftables'. According to the documentation
(https://wiki.de
On 8/10/21 1:59 AM, ourdiaspora wrote:
On Sunday, August 8th, 2021 at 1:51 AM, Adrian Klaver
wrote:
1. Get rid of the first local line .
2. Then for the remaining local line below change peer to trust and
restart Postgres.
Thank you, but repeat error occurred:
sudo sudo service po
ourdiaspora writes:
> A quick ddg search revealed:
> sudo ss -tulpn
> Netid State Recv-Q Send-Q Local Address:Port Peer
> Address:Port
> tcpLISTEN 0 128 ::1:5432 :::*
>users:(("postgres",pid=21794,fd=3))
> Is the correct c
On Sunday, August 8th, 2021 at 2:15 AM, Tom Lane wrote:
> ourdiaspora ourdiasp...@protonmail.com writes:
>
> > psql -d cpacweb -U cpaca
> >
> > psql: FATAL: Peer authentication failed for user "cpaca"
>
> It's a gold
>
> plated certainty that the default packet filter configuration
>
> wouldn
On Sunday, August 8th, 2021 at 1:51 AM, Adrian Klaver
wrote:
> 1. Get rid of the first local line .
> 2. Then for the remaining local line below change peer to trust and
>
> restart Postgres.
Thank you, but repeat error occurred:
sudo sudo service postgresql restart
[ ok ] Restarting P
ourdiaspora writes:
> psql -d cpacweb -U cpaca
> psql: FATAL: Peer authentication failed for user "cpaca"
The reason that's able to make a connection to the PG server
is that it's not going through TCP at all, but a Unix socket.
I'd guess at this point that your configuration never worked
for
On 8/7/21 5:36 PM, ourdiaspora wrote:
On Sunday, August 8th, 2021 at 1:02 AM, Adrian Klaver
wrote:
What did you change listen_addresses from?
New line; same line had hash (#) to comment out.
What if you do?:
psql -d cpacweb -U cpaca
psql -d cpacweb -U cpaca
psql: FATAL: Peer authen
On Sunday, August 8th, 2021 at 1:02 AM, Adrian Klaver
wrote:
> What did you change listen_addresses from?
>
New line; same line had hash (#) to comment out.
> What if you do?:
>
> psql -d cpacweb -U cpaca
>
psql -d cpacweb -U cpaca
psql: FATAL: Peer authentication failed for user "cpaca"
On 8/7/21 4:11 PM, ourdiaspora wrote:
On Saturday, August 7th, 2021 at 11:20 PM, Adrian Klaver
wrote:
psql -d cpacweb -h 127.0.0.1 -U cpaca
psql: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on
On Saturday, August 7, 2021, ourdiaspora wrote:
>
> On Sunday, August 8th, 2021 at 12:50 AM, David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
> > On Saturday, August 7, 2021, ourdiaspora
> wrote:
> >
> > > SHOW hba_file;
> > >
> > > /etc/postgresql/9.6/main/pg_hba.conf
> >
> >
On Sunday, August 8th, 2021 at 12:50 AM, David G. Johnston
wrote:
> On Saturday, August 7, 2021, ourdiaspora wrote:
>
> > SHOW hba_file;
> >
> > /etc/postgresql/9.6/main/pg_hba.conf
>
> Please post the contents of this file. The one shown at the link is invalid.
local all
On Sunday, August 8th, 2021 at 12:26 AM, Tom Lane wrote:
>
> Hm --- this suggests that you've got a kernel packet filter (i.e.
>
> software firewall) that is not passing traffic for 5432.
Don't know anything about that, so perhaps it can be assumed unchanged from
whatever the default system con
On Saturday, August 7, 2021, Tom Lane wrote:
> ourdiaspora writes:
> > psql -d cpacweb -h 127.0.0.1 -U cpaca
> > psql: could not connect to server: Connection refused
> > Is the server running on host "127.0.0.1" and accepting
> > TCP/IP connections on port 5432?
>
> Hm --- this sugg
On Saturday, August 7, 2021, ourdiaspora wrote:
>
> SHOW hba_file;
> /etc/postgresql/9.6/main/pg_hba.conf
>
>
Please post the contents of this file. The one shown at the link is
invalid.
David J.
ourdiaspora writes:
> psql -d cpacweb -h 127.0.0.1 -U cpaca
> psql: could not connect to server: Connection refused
> Is the server running on host "127.0.0.1" and accepting
> TCP/IP connections on port 5432?
Hm --- this suggests that you've got a kernel packet filter (i.e.
software f
On Sunday, August 8th, 2021 at 12:11 AM, Tom Lane wrote:
>
> If php is trying to connect to something else, like say the
>
> machine's external IP address, that could be your issue.
Excuse the ignorance, but if the instruction in the php file is:
"
...$dbconn = pg_connect("dbname=cpacweb user=cp
On Saturday, August 7th, 2021 at 11:20 PM, Adrian Klaver
wrote:
>
> 1. OS and version?
Same local machine as described
> 2. The contents of /etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
>
ourdiaspora writes:
> The postgresql server was restarted, successfully.
> listen_addresses = 'localhost'
I believe on most machines, that would result in the postmaster
only listening on 127.0.0.1, and ::1 if you're IPv6-enabled.
If php is trying to connect to something else, like say the
machin
On 8/7/21 3:15 PM, ourdiaspora wrote:
On Saturday, August 7th, 2021 at 10:17 PM, Adrian Klaver
wrote:
On 8/7/21 1:09 PM, ourdiaspora wrote:
On Saturday, August 7th, 2021 at 8:23 PM, Adrian Klaver
adrian.kla...@aklaver.com wrote:
Changes were made to the function 'listen_addressess' to
On Saturday, August 7th, 2021 at 10:17 PM, Adrian Klaver
wrote:
> On 8/7/21 1:09 PM, ourdiaspora wrote:
>
> > On Saturday, August 7th, 2021 at 8:23 PM, Adrian Klaver
> > adrian.kla...@aklaver.com wrote:
>
> > Changes were made to the function 'listen_addressess' to the configuration
> > file
On 8/7/21 1:09 PM, ourdiaspora wrote:
On Saturday, August 7th, 2021 at 8:23 PM, Adrian Klaver
wrote:
Changes were made to the function 'listen_addressess' to the configuration file
shown in above.
I should have asked in previous post, what was 'listen_addresses'
changed to?
--
A
On 8/7/21 1:09 PM, ourdiaspora wrote:
On Saturday, August 7th, 2021 at 8:23 PM, Adrian Klaver
wrote:
Since further configuration, remain unable to connect to the php database.
Further configuration of what?
The postgresql configuration file:
SHOW hba_file;
/etc/postgresql/9.6/m
On Saturday, August 7th, 2021 at 8:23 PM, Adrian Klaver
wrote:
> > Since further configuration, remain unable to connect to the php database.
>
> Further configuration of what?
>
The postgresql configuration file:
SHOW hba_file;
/etc/postgresql/9.6/main/pg_hba.conf
SHOW config_file;
On 8/7/21 11:46 AM, ourdiaspora wrote:
Readers,
Background: http://news-web.php.net/php.general/327600
Since further configuration, remain unable to connect to the php database.
Further configuration of what?
After the configuration change did you restart the server?
Is the pg_hba.conf file
Readers,
Background: http://news-web.php.net/php.general/327600
Since further configuration, remain unable to connect to the php database.
Software system is debian, xfce, postgresql, php. Database created on local
machine with directory of web server content in extant normal user account.
The
36 matches
Mail list logo
