Solved: changing the ownership of the custom log in conf.d solved the problem.
Regards Johann On Tue, 3 Dec 2019 at 17:14, Johann Spies <johann.sp...@gmail.com> wrote: > We have upgraded two servers by installing postgresql(pgpd) 12. Both > servers are running Debian Stable. > > On the problem server we have: > pg_lsclusters > Ver Cluster Port Status Owner Data directory Log file > 11 main 5432 online postgres /var/lib/postgresql/11/main > /var/log/postgresql/postgresql-11-main.log > 12 main 5434 online postgres /var/lib/postgresql/12/main > /var/log/postgresql/postgresql-12-main.log > > But nothing gets written to the logfiles. In stead the logs appear on the > console when the user postgresql is connecting to the database. > > On the other server: > $ pg_lsclusters > Ver Cluster Port Status Owner Data directory Log file > 11 main 5433 down postgres /var/lib/postgresql/11/main > /var/log/postgresql/postgresql-11-main.log > 12 main 5432 online postgres /var/lib/postgresql/12/main > /var/log/postgresql/postgresql-12-main.log > > The logging works as expected. > > The postgresql.conf for version 12 is identical on both servers - the > default installed by Debian. > > This is with logging_collector off. > > When switching logging_collector on on the problem server, it logs to > /var/lib/postgresql/11/main/log/. > > Our preference would be to have the logs on both servers in > /var/log/postgresql. > > Where do we look for the cause of this behaviour? On both servers the > configuration for rsyslog seems to be identical. > > Regards. > > Johann > > > > -- > Because experiencing your loyal love is better than life itself, > my lips will praise you. (Psalm 63:3) > -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
