Description of problem: PostgreSQL log is missing timestamps, making debugging harder Version-Release number of selected component (if applicable): satellite-6.4.0-14.el7sat.noarch snap 22 (updated from snap 17) How reproducible: always Steps to Reproduce: 1. Check PostgreSQL log at /var/lib/pgsql/data/pg_log/postgresql-Tue.log Actual results: Log format is missing timestamp Expected results: Timestamp should be there
Build:Satellite 6.4.0 snap 23 LOG:/var/lib/pgsql/data/pg_log tail -f postgresql-Sat.log 2018-09-22 01:55:03 EDT LOG: aborting any active transactions 2018-09-22 01:55:03 EDT LOG: autovacuum launcher shutting down 2018-09-22 01:55:05 EDT LOG: shutting down 2018-09-22 01:55:05 EDT LOG: database system is shut down 2018-09-22 01:56:04 EDT LOG: database system was shut down at 2018-09-22 01:55:05 EDT 2018-09-22 01:56:04 EDT LOG: database system is ready to accept connections 2018-09-22 01:56:04 EDT LOG: autovacuum launcher started 2018-09-22 01:56:48 EDT ERROR: duplicate key value violates unique constraint "dynflow_coordinator_records_pkey" 2018-09-22 01:56:48 EDT DETAIL: Key (id, class)=(delayed-executor, Dynflow::Coordinator::DelayedExecutorLock) already exists. 2018-09-22 01:56:48 EDT STATEMENT: INSERT INTO "dynflow_coordinator_records" ("data", "id", "owner_id", "class") VALUES ('{"class":"Dynflow::Coordinator::DelayedExecutorLock","owner_id":"world:812f0aea-3001-4824-a218-a03cf4910db6","world_id":"812f0aea-3001-4824-a218-a03cf4910db6","id":"delayed-executor"}', 'delayed-executor', 'world:812f0aea-3001-4824-a218-a03cf4910db6', 'Dynflow::Coordinator::DelayedExecutorLock') RETURNING "id"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927