New message in PostgreSQL log regarding socket for statistics collector
| От | Hilbert, Karin |
|---|---|
| Тема | New message in PostgreSQL log regarding socket for statistics collector |
| Дата | |
| Msg-id | MN2PR02MB6829D0F6C05E5FBC779032CA89489@MN2PR02MB6829.namprd02.prod.outlook.com обсуждение исходный текст |
| Ответы |
Re: New message in PostgreSQL log regarding socket for statistics collector
(Christoph Moench-Tegeder <cmt@burggraben.net>)
|
| Список | pgsql-general |
I'm working on an implementation of PostgreSQL 13.8 on a Linux RHEL8 sandbox environment.
Thanks, Karin
The server & PostgreSQL have all been configured.
I started PostgreSQL & got the following messages in the log file:
2022-09-16 02:00:16 EDT [1918984]: [3-1] db=,user= LOG: starting PostgreSQL 13.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10), 64-bit
2022-09-16 02:00:16 EDT [1918984]: [4-1] db=,user= LOG: listening on IPv4 address "0.0.0.0", port 5432
2022-09-16 02:00:16 EDT [1918984]: [5-1] db=,user= LOG: listening on IPv6 address "::", port 5432
2022-09-16 02:00:16 EDT [1918984]: [6-1] db=,user= LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-09-16 02:00:16 EDT [1918984]: [7-1] db=,user= LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
2022-09-16 02:00:17 EDT [1918984]: [8-1] db=,user= LOG: test message did not get through on socket for statistics collector
2022-09-16 02:00:17 EDT [1918984]: [9-1] db=,user= LOG: trying another address for the statistics collector
2022-09-16 02:00:17 EDT [1918986]: [1-1] db=,user= LOG: database system was shut down at 2022-09-14 17:26:53 EDT
2022-09-16 02:00:17 EDT [1918984]: [10-1] db=,user= LOG: database system is ready to accept connections
I'm concerned about the "test message did not get through on socket for statistics collector" & "trying another address for the statistics collector" messages.
I've never seen these before & wasn't able to find anything about them via a Google search. What I did find, talked about the unix socket directories. I left that parameter at the default setting:
#unix_socket_directories = '/var/run/postgresql, /tmp' # comma-separated list of directories
I checked both of those locations & found the following entries:
[postgres@xxxxxx ~]$ ls -al /var/run/postgresql/
total 4
drwxr-xr-x 2 postgres postgres 80 Sep 16 02:00 .
drwxr-xr-x 30 root root 900 Aug 31 13:17 ..
srwxrwxrwx 1 postgres postgres 0 Sep 16 02:00 .s.PGSQL.5432
-rw------- 1 postgres postgres 67 Sep 16 02:00 .s.PGSQL.5432.lock
[postgres@xxxxxx ~]$ cat /var/run/postgresql/.s.PGSQL.5432.lock
1918984
/var/lib/pgsql/13/data
1663308016
5432
/var/run/postgresql
[postgres@xxxxxx ~]$ ls -al /tmp/ | grep .s.PGSQL
srwxrwxrwx 1 postgres postgres 0 Sep 16 02:00 .s.PGSQL.5432
-rw------- 1 postgres postgres 52 Sep 16 02:00 .s.PGSQL.5432.lock
[postgres@xxxxxx ~]$ cat /tmp/.s.PGSQL.5432.lock
1918984
/var/lib/pgsql/13/data
1663308016
5432
/tmp
Is there anything that I should be concerned about regarding these messages or are they normal?
Also, should I change the unix_socket_directories parm to just have one directory? In past versions of PostgreSQL, we've just had one directory:
#unix_socket_directories = '/tmp'
Karin Hilbert
Database Administration
Pennsylvania State University
В списке pgsql-general по дате отправления: