Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1630528 - PostgreSQL log is missing timestamps, making debugging harder
Summary: PostgreSQL log is missing timestamps, making debugging harder
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.4.0
Assignee: Chris Roberts
QA Contact: Sanket Jagtap
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-18 20:38 UTC by Jan Hutař
Modified: 2019-11-05 23:35 UTC (History)
9 users (show)

Fixed In Version: foreman-installer-1.18.0.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 18:57:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24998 0 Normal Closed PostgreSQL log is missing timestamps, making debugging harder 2020-10-14 13:20:42 UTC

Description Jan Hutař 2018-09-18 20:38:07 UTC 
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
Comment 7 Sanket Jagtap 2018-09-24 10:21:03 UTC 
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"
Comment 8 Bryan Kearney 2018-10-16 18:57:42 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.