Re: databases/postgresl13-server issue: micsompilation on IvyBridge arch?
On Mon, 9 Aug 2021 08:40:04 -0400 Zaphod Beeblebrox wrote: > IIRC, isn't the postgresql-server's default install on FreeBSD, from ports, > have TCP turned off? IE: try editing the config (in the database > directory) to uncomment the listen directive? Hello and thank you very much for responding. I do not understand what you mean by "editing the config (in the database directory). Do you mean by that the postgresql.conf file? Well, this file is proper set and has been, the installation has worked well once until May the 26th. I try out to figure out what happened to CURRENT that time. In the meanwhile, I tried to rebuild CURRENT from scratch with WITHOUT_OPENSSL_KTLS set, avoiding any CPU optimization during compilation of world and postgresql - but without any effect. The pain is, that two boxes ofthe same CPU arch affected the same way, no matter what I do. > > On Sun, Aug 8, 2021 at 5:21 AM FreeBSD User wrote: > > > Hello, > > > > on all(!) of my home systems based on Intel's IvyBridge CPU architecture > > > > a) CPU microcode: updated from 0x1f to 0x21 > >CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (3200.09-MHz K8-class CPU) > > > > b) CPU microcode: updated from 0x1f to 0x21 > >CPU: Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz (3400.09-MHz K8-class > > CPU) > > > > I face a severe and nasty problem: > > > > database/postgresql12-server, database/postgresql13-server, > > database/postgresql14-server, when > > installed, do not allow any kind of tcp/ip connections, even on ::1 or > > 127.0.0.1 (localhost). > > All systems in question are dual stack and fully configured using IPv6. > > Firewall is FreeBSD > > standard IPFW running from /etc/rc.conf (port 5432/tcp is open and > > listening as one can check > > via sockstat -4 or sockstat -6). > > > > The hosts in question do run 14-CURRENT (with customized kernels). > > > > Phenomenon: > > > > Login locally via "psql -U postgres -d postgres" via socket works for ALL > > DB users on all > > configured to access databases as expected. Login via "psql -U postgres -d > > postgres -h > > localhost" (or any form of an IP if access tried from another remote host, > > even locally via > > 127.0.0.1 or ::1) does result in: > > > > : psql -U postgres -d postgres -h localhost > > psql: error: server closed the connection unexpectedly > > This probably means the server terminated abnormally > > before or while processing the request. > > > > On the server's postgresql log I always see connection attempts like: > > > > [...] > > 2021-08-08 08:56:57.601 GMT [42987] LOG: connection received: > > host=localhost port=12340 > > > > but nothing more, no error message or any kind of timeout message. > > > > I tried to raise the log level to debug, but it is always nothing shown > > execept the initial > > connection attempt. > > > > What I tried so far: > > I used either self compiled ports or packages taken via pkg fetch from the > > official FreeBSD > > pkg repos. I had LLVM suspected to miscompile something on IvyBridge. No > > different result so > > far. Postgres 12, 13 14 fail the same way. > > > > I installed with the above strategy vanilla databases. That includes a > > pg_hba.conf with the > > follwoing lines (as anybody can proof): > > > > [...] > > # TYPE DATABASEUSERADDRESS METHOD > > > > # "local" is for Unix domain socket connections only > > local all all trust > > # IPv4 local connections: > > hostall all 127.0.0.1/32trust > > # IPv6 local connections: > > hostall all ::1/128 trust > > hostall all 0.0.0.0/32 trust > > hostall all ::/128 trust > > > > > > That should grant access via "localhost" and, for test purposes, access > > from any other machine > > in our LAN for any user to any database. > > > > Also, I configured postgresql13-server's postgresql.conf with following > > additions: > > > > log_destination = 'syslog,stderr' > > log_min_messages = debug5 > > log_min_error_statement = debug5 > > > > debug_print_parse = on > > debug_print_rewritten = on > > debug_print_plan = on > > debug_pretty_print = on > > log_checkpoints = on > > log_connections = on > > log_disconnections = on > > log_duration = on > > log_error_verbosity = verbose # terse, default, or verbose messages > > log_hostname = on > > > > Trying again a login from localhost via the psql command show above, gives > > this : > > > > > > [...] > > 2021-08-08 09:12:12.999 GMT [55664] DEBUG: 0: forked new backend, > > pid=55673 socket=12 > > > > 2021-08-08 09:12:12.999 GMT [55664] LOCATION: BackendStartup, > > postmaster.c:4232 > > > > 2021-08-08 09:12:13.000 GMT [55673] LOG: 0: connection received: > > host=localhost > > port=42708 > > > > 2021-08-08 09:12:13.000 GMT [55673] LOCATION:
Re: databases/postgresl13-server issue: micsompilation on IvyBridge arch?
IIRC, isn't the postgresql-server's default install on FreeBSD, from ports, have TCP turned off? IE: try editing the config (in the database directory) to uncomment the listen directive? On Sun, Aug 8, 2021 at 5:21 AM FreeBSD User wrote: > Hello, > > on all(!) of my home systems based on Intel's IvyBridge CPU architecture > > a) CPU microcode: updated from 0x1f to 0x21 >CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (3200.09-MHz K8-class CPU) > > b) CPU microcode: updated from 0x1f to 0x21 >CPU: Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz (3400.09-MHz K8-class > CPU) > > I face a severe and nasty problem: > > database/postgresql12-server, database/postgresql13-server, > database/postgresql14-server, when > installed, do not allow any kind of tcp/ip connections, even on ::1 or > 127.0.0.1 (localhost). > All systems in question are dual stack and fully configured using IPv6. > Firewall is FreeBSD > standard IPFW running from /etc/rc.conf (port 5432/tcp is open and > listening as one can check > via sockstat -4 or sockstat -6). > > The hosts in question do run 14-CURRENT (with customized kernels). > > Phenomenon: > > Login locally via "psql -U postgres -d postgres" via socket works for ALL > DB users on all > configured to access databases as expected. Login via "psql -U postgres -d > postgres -h > localhost" (or any form of an IP if access tried from another remote host, > even locally via > 127.0.0.1 or ::1) does result in: > > : psql -U postgres -d postgres -h localhost > psql: error: server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > > On the server's postgresql log I always see connection attempts like: > > [...] > 2021-08-08 08:56:57.601 GMT [42987] LOG: connection received: > host=localhost port=12340 > > but nothing more, no error message or any kind of timeout message. > > I tried to raise the log level to debug, but it is always nothing shown > execept the initial > connection attempt. > > What I tried so far: > I used either self compiled ports or packages taken via pkg fetch from the > official FreeBSD > pkg repos. I had LLVM suspected to miscompile something on IvyBridge. No > different result so > far. Postgres 12, 13 14 fail the same way. > > I installed with the above strategy vanilla databases. That includes a > pg_hba.conf with the > follwoing lines (as anybody can proof): > > [...] > # TYPE DATABASEUSERADDRESS METHOD > > # "local" is for Unix domain socket connections only > local all all trust > # IPv4 local connections: > hostall all 127.0.0.1/32trust > # IPv6 local connections: > hostall all ::1/128 trust > hostall all 0.0.0.0/32 trust > hostall all ::/128 trust > > > That should grant access via "localhost" and, for test purposes, access > from any other machine > in our LAN for any user to any database. > > Also, I configured postgresql13-server's postgresql.conf with following > additions: > > log_destination = 'syslog,stderr' > log_min_messages = debug5 > log_min_error_statement = debug5 > > debug_print_parse = on > debug_print_rewritten = on > debug_print_plan = on > debug_pretty_print = on > log_checkpoints = on > log_connections = on > log_disconnections = on > log_duration = on > log_error_verbosity = verbose # terse, default, or verbose messages > log_hostname = on > > Trying again a login from localhost via the psql command show above, gives > this : > > > [...] > 2021-08-08 09:12:12.999 GMT [55664] DEBUG: 0: forked new backend, > pid=55673 socket=12 > > 2021-08-08 09:12:12.999 GMT [55664] LOCATION: BackendStartup, > postmaster.c:4232 > > 2021-08-08 09:12:13.000 GMT [55673] LOG: 0: connection received: > host=localhost > port=42708 > > 2021-08-08 09:12:13.000 GMT [55673] LOCATION: BackendInitialize, > postmaster.c:4385 > > 2021-08-08 09:12:19.994 GMT [55667] DEBUG: 0: snapshot of 0+0 running > transaction ids > (lsn 0/15FF178 oldest xid 487 latest complete 486 next xid 487) > 2021-08-08 09:12:19.994 GMT [55667] LOCATION: LogCurrentRunningXacts, > standby.c:1124 > 2021-08-08 09:13:04.988 GMT [55669] DEBUG: 0: StartTransaction(1) > name: unnamed; > blockState: DEFAULT; state: INPROGRESS, xid/subid/cid: 0/1/0 > 2021-08-08 09:13:04.988 GMT [55669] LOCATION: ShowTransactionStateRec, > xact.c:5358 > 2021-08-08 09:13:04.988 GMT [55669] DEBUG: 0: CommitTransaction(1) > name: unnamed; > blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0 > 2021-08-08 09:13:04.988 GMT [55669] LOCATION: ShowTransactionStateRec, > xact.c:5358 > 2021-08-08 09:13:04.988 GMT [55670] DEBUG: 0: received inquiry for > database 0 > 2021-08-08 09:13:04.988 GMT [55670] LOCATION: pgstat_recv_inquiry,
databases/postgresl13-server issue: micsompilation on IvyBridge arch?
Hello, on all(!) of my home systems based on Intel's IvyBridge CPU architecture a) CPU microcode: updated from 0x1f to 0x21 CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (3200.09-MHz K8-class CPU) b) CPU microcode: updated from 0x1f to 0x21 CPU: Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz (3400.09-MHz K8-class CPU) I face a severe and nasty problem: database/postgresql12-server, database/postgresql13-server, database/postgresql14-server, when installed, do not allow any kind of tcp/ip connections, even on ::1 or 127.0.0.1 (localhost). All systems in question are dual stack and fully configured using IPv6. Firewall is FreeBSD standard IPFW running from /etc/rc.conf (port 5432/tcp is open and listening as one can check via sockstat -4 or sockstat -6). The hosts in question do run 14-CURRENT (with customized kernels). Phenomenon: Login locally via "psql -U postgres -d postgres" via socket works for ALL DB users on all configured to access databases as expected. Login via "psql -U postgres -d postgres -h localhost" (or any form of an IP if access tried from another remote host, even locally via 127.0.0.1 or ::1) does result in: : psql -U postgres -d postgres -h localhost psql: error: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. On the server's postgresql log I always see connection attempts like: [...] 2021-08-08 08:56:57.601 GMT [42987] LOG: connection received: host=localhost port=12340 but nothing more, no error message or any kind of timeout message. I tried to raise the log level to debug, but it is always nothing shown execept the initial connection attempt. What I tried so far: I used either self compiled ports or packages taken via pkg fetch from the official FreeBSD pkg repos. I had LLVM suspected to miscompile something on IvyBridge. No different result so far. Postgres 12, 13 14 fail the same way. I installed with the above strategy vanilla databases. That includes a pg_hba.conf with the follwoing lines (as anybody can proof): [...] # TYPE DATABASEUSERADDRESS METHOD # "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: hostall all 127.0.0.1/32trust # IPv6 local connections: hostall all ::1/128 trust hostall all 0.0.0.0/32 trust hostall all ::/128 trust That should grant access via "localhost" and, for test purposes, access from any other machine in our LAN for any user to any database. Also, I configured postgresql13-server's postgresql.conf with following additions: log_destination = 'syslog,stderr' log_min_messages = debug5 log_min_error_statement = debug5 debug_print_parse = on debug_print_rewritten = on debug_print_plan = on debug_pretty_print = on log_checkpoints = on log_connections = on log_disconnections = on log_duration = on log_error_verbosity = verbose # terse, default, or verbose messages log_hostname = on Trying again a login from localhost via the psql command show above, gives this : [...] 2021-08-08 09:12:12.999 GMT [55664] DEBUG: 0: forked new backend, pid=55673 socket=12 2021-08-08 09:12:12.999 GMT [55664] LOCATION: BackendStartup, postmaster.c:4232 2021-08-08 09:12:13.000 GMT [55673] LOG: 0: connection received: host=localhost port=42708 2021-08-08 09:12:13.000 GMT [55673] LOCATION: BackendInitialize, postmaster.c:4385 2021-08-08 09:12:19.994 GMT [55667] DEBUG: 0: snapshot of 0+0 running transaction ids (lsn 0/15FF178 oldest xid 487 latest complete 486 next xid 487) 2021-08-08 09:12:19.994 GMT [55667] LOCATION: LogCurrentRunningXacts, standby.c:1124 2021-08-08 09:13:04.988 GMT [55669] DEBUG: 0: StartTransaction(1) name: unnamed; blockState: DEFAULT; state: INPROGRESS, xid/subid/cid: 0/1/0 2021-08-08 09:13:04.988 GMT [55669] LOCATION: ShowTransactionStateRec, xact.c:5358 2021-08-08 09:13:04.988 GMT [55669] DEBUG: 0: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0 2021-08-08 09:13:04.988 GMT [55669] LOCATION: ShowTransactionStateRec, xact.c:5358 2021-08-08 09:13:04.988 GMT [55670] DEBUG: 0: received inquiry for database 0 2021-08-08 09:13:04.988 GMT [55670] LOCATION: pgstat_recv_inquiry,
