On Sun, 9 Sep 2018 08:32:17 -0700 Chris Bennett <cpb_m...@bennettconstruction.us> wrote:
> On Sun, Sep 09, 2018 at 05:10:51AM +0000, Timo Myyrä wrote: > > Chris Bennett <cpb_m...@bennettconstruction.us> writes: > > > > > I know that PostgreSQL can be accessed via a socket or through > > > 127.0.0.1. > > I read your mail and I still don't know what you are trying to > > accomplish. Could you give a more specific questions so they are > > easier to answer. > > OK, I am assuming that just working through 127.0.0.1 will be OK. > I just want to be sure that there are not any special issues I need to > know using base httpd. > There may not be anything I need to know, so then this is more than > anything else, just possibly "noise" as far as that. httpd doesn't usually listen on the port PostgreSQL typically uses (5432). If your web application uses Unix sockets you probably should set “unix_socket_directories” in postgresql.conf to a directory inside the httpd chroot. Also carefully consider the other unix_socket options. (more below) > > However, I have run into this weird problem. > After starting up PostgreSQL while not using any network, or today > when I am connected to WiFi though my phone hotspot, no problems > > However, yesterday when I was using my hotspot I got the following: > > /var/postgresql/logfile: > > > 2018-09-08 12:34:45.209 PDT [32845] LOG: listening on IPv4 address > "127.0.0.1", port 5432 2018-09-08 12:34:45.210 PDT [32845] LOG: > listening on IPv6 address "::1", port 5432 2018-09-08 12:34:45.210 > PDT [32845] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" > 2018-09-08 12:34:45.282 PDT [6899] LOG: database system was shut > down at 2018-09-08 12:34:30 PDT 2018-09-08 12:34:45.286 PDT [32845] > LOG: database system is ready to accept connections 2018-09-08 > 17:26:18.201 PDT [32845] LOG: received fast shutdown request > 2018-09-08 17:26:18.203 PDT [32845] LOG: aborting any active > transactions 2018-09-08 17:26:18.208 PDT [32845] LOG: worker > process: logical replication launcher (PID 48119) exited with exit > code 1 2018-09-08 17:26:18.209 PDT [34232] LOG: shutting down > 2018-09-08 17:26:18.230 PDT [32845] LOG: database system is shut > down 2018-09-08 17:32:51.693 PDT [62478] LOG: listening on IPv4 > address "127.0.0.1", port 5432 2018-09-08 17:32:51.711 PDT [62478] > LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" 2018-09-08 > 17:36:37.361 PDT [62478] LOG: received SIGHUP, reloading > configuration files 2018-09-08 17:36:37.364 PDT [61376] LOG: > database system was shut down at 2018-09-08 17:26:18 PDT 2018-09-08 > 17:36:37.420 PDT [62478] LOG: database system is ready to accept > connections 2018-09-08 19:31:21.875 PDT [62478] LOG: received fast > shutdown request 2018-09-08 19:31:21.878 PDT [62478] LOG: aborting > any active transactions 2018-09-08 19:31:21.883 PDT [62478] LOG: > worker process: logical replication launcher (PID 84341) exited with > exit code 1 2018-09-08 19:31:21.883 PDT [96335] LOG: shutting down > 2018-09-08 19:31:21.901 PDT [62478] LOG: database system is shut > down 2018-09-09 01:13:49.070 PDT [11789] LOG: listening on IPv4 > address "127.0.0.1", port 5432 2018-09-09 01:13:49.087 PDT [11789] > LOG: listening on IPv6 address "::1", port 5432 2018-09-09 > 01:13:49.088 PDT [11789] LOG: listening on Unix socket > "/tmp/.s.PGSQL.5432" 2018-09-09 01:13:49.272 PDT [60464] LOG: > database system was shut down at 2018-09-08 19:31:21 PDT 2018-09-09 > 01:13:49.449 PDT [11789] LOG: database system is ready to accept > connections 2018-09-09 01:13:49.862 PDT [11789] LOG: received > SIGHUP, reloading configuration files 2018-09-09 01:15:55.172 PDT > [11789] LOG: received fast shutdown request 2018-09-09 01:15:55.174 > PDT [11789] LOG: aborting any active transactions 2018-09-09 > 01:15:55.177 PDT [11789] LOG: worker process: logical replication > launcher (PID 71619) exited with exit code 1 2018-09-09 01:15:55.177 > PDT [84731] LOG: shutting down 2018-09-09 01:15:55.235 PDT [11789] > LOG: database system is shut down > > End of all OK, then this: > > 2018-09-09 05:39:00.886 PDT [1208] LOG: could not bind IPv4 address > "198.105.244.104": Can't assign requested address 2018-09-09 > 05:39:00.886 PDT [1208] HINT: Is another postmaster already running > on port 5432? If not, wait a few seconds and retry. 2018-09-09 > 05:39:00.902 PDT [1208] LOG: could not bind IPv4 address > "198.105.254.104": Can't assign requested address 2018-09-09 > 05:39:00.902 PDT [1208] HINT: Is another postmaster already running > on port 5432? If not, wait a few seconds and retry. 2018-09-09 > 05:39:00.902 PDT [1208] WARNING: could not create listen socket for > "localhost" 2018-09-09 05:39:00.902 PDT [1208] FATAL: could not > create any TCP/IP sockets 2018-09-09 05:39:00.903 PDT [1208] LOG: > database system is shut down 2018-09-09 08:03:01.936 CDT [73639] > LOG: could not bind IPv4 address "198.105.244.104": Can't assign > requested address 2018-09-09 08:03:01.936 CDT [73639] HINT: Is > another postmaster already running on port 5432? If not, wait a few > seconds and retry. 2018-09-09 08:03:01.936 CDT [73639] LOG: could > not bind IPv4 address "198.105.254.104": Can't assign requested > address 2018-09-09 08:03:01.936 CDT [73639] HINT: Is another > postmaster already running on port 5432? If not, wait a few seconds > and retry. 2018-09-09 08:03:01.937 CDT [73639] WARNING: could not > create listen socket for "localhost" 2018-09-09 08:03:01.937 CDT > [73639] FATAL: could not create any TCP/IP sockets 2018-09-09 > 08:03:01.937 CDT [73639] LOG: database system is shut down > 2018-09-09 11:36:54.299 CDT [50112] LOG: could not bind IPv4 address > "198.105.254.104": Can't assign requested address 2018-09-09 > 11:36:54.299 CDT [50112] HINT: Is another postmaster already running > on port 5432? If not, wait a few seconds and retry. 2018-09-09 > 11:36:54.315 CDT [50112] LOG: could not bind IPv4 address > "198.105.244.104": Can't assign requested address 2018-09-09 > 11:36:54.315 CDT [50112] HINT: Is another postmaster already running > on port 5432? If not, wait a few seconds and retry. 2018-09-09 > 11:36:54.315 CDT [50112] WARNING: could not create listen socket for > "localhost" 2018-09-09 11:36:54.315 CDT [50112] FATAL: could not > create any TCP/IP sockets 2018-09-09 11:36:54.316 CDT [50112] LOG: > database system is shut down > > Huh?? See whois below > > Today: > > 2018-09-09 12:15:00.146 CDT [28563] LOG: listening on IPv4 address > "127.0.0.1", port 5432 2018-09-09 12:15:00.146 CDT [28563] LOG: > listening on IPv6 address "::1", port 5432 2018-09-09 12:15:00.147 > CDT [28563] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" > 2018-09-09 12:15:00.367 CDT [94897] LOG: database system was shut > down at 2018-09-09 03:15:55 CDT 2018-09-09 12:15:00.436 CDT [28563] > LOG: database system is ready to accept connections > > Perfect. > > > whois 198.105.254.104: > > > > # Query terms are ambiguous. The query is assumed to be: > # "n 198.105.254.104" > # > # Use "?" to get help. > # > > NetRange: 198.105.240.0 - 198.105.255.255 > CIDR: 198.105.240.0/20 > NetName: SEARCHGUIDE > NetHandle: NET-198-105-240-0-1 > Parent: NET198 (NET-198-0-0-0-0) > NetType: Direct Assignment > OriginAS: > Organization: Search Guide Inc (SG-63) > RegDate: 2012-07-10 > Updated: 2012-07-10 > Ref: https://rdap.arin.net/registry/ip/198.105.240.0 > > > OrgName: Search Guide Inc > OrgId: SG-63 > Address: 1942 Broadway > Address: Suite 319 > City: Boulder > StateProv: CO > PostalCode: 80302 > Country: US > RegDate: 2012-06-26 > Updated: 2012-06-26 > Comment: Standard NOC hours are 7am to 6pm EST > Ref: https://rdap.arin.net/registry/entity/SG-63 > > > OrgAbuseHandle: NETWO5248-ARIN > OrgAbuseName: Network Operations > OrgAbusePhone: +1-857-285-9173 > OrgAbuseEmail: n...@searchguideinc.com > OrgAbuseRef: https://rdap.arin.net/registry/entity/NETWO5248-ARIN > > OrgNOCHandle: NETWO5248-ARIN > OrgNOCName: Network Operations > OrgNOCPhone: +1-857-285-9173 > OrgNOCEmail: n...@searchguideinc.com > OrgNOCRef: https://rdap.arin.net/registry/entity/NETWO5248-ARIN > > OrgTechHandle: NETWO5248-ARIN > OrgTechName: Network Operations > OrgTechPhone: +1-857-285-9173 > OrgTechEmail: n...@searchguideinc.com > OrgTechRef: https://rdap.arin.net/registry/entity/NETWO5248-ARIN > > > Umm, what the heck is this and how could it happen? > It wouldn't be your IP address, by chance? Dunno how this happens, but if you're only using 127.0.0.1 for PostgreSQL connections, set “listen_addresses” in postgresql accordingly (e.g. “listen_addresses = localhost” -- or 127.0.0.1). WRT to your original mail, Unix sockets are “supposed” to be faster wrt to less context switches and stuff, though it might not matter iffen you haven't too much of connections. Best regards Robert
