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 1075496 - PostgreSQL DB logging config is missing timestamps making debugging hard
Summary: PostgreSQL DB logging config is missing timestamps making debugging hard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Ondřej Pražák
QA Contact: Kedar Bidarkar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-12 09:34 UTC by Jan Hutař
Modified: 2019-09-26 14:07 UTC (History)
4 users (show)

Fixed In Version: foreman-installer-1.11.0.4-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:08:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5818 0 None None None 2016-04-22 16:19:18 UTC

Description Jan Hutař 2014-03-12 09:34:58 UTC 
Description of problem:
PostgreSQL DB logging config is missing timestamps making debugging hard


Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140305.1


How reproducible:
always


Steps to Reproduce:
1. Check /var/lib/pgsql/data/pg_log/postgresql-*.log


Actual results:
No timestamp at the beginning of the file


Expected results:
Timestamp should be there
Comment 1 RHEL Program Management 2014-03-12 09:36:53 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Dominic Cleal 2014-05-20 13:03:19 UTC 
Created redmine issue http://projects.theforeman.org/issues/5818 from this bug
Comment 4 Bryan Kearney 2016-04-05 12:03:35 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/5818 has been closed
-------------
Dominic Cleal
Fixed in https://github.com/puppetlabs/puppetlabs-postgresql/pull/754.
Comment 5 Kedar Bidarkar 2016-05-24 15:30:42 UTC 
We can see now timestamps in the log file, /var/lib/pgsql/data/pg_log/postgresql-*.log

2016-05-19 10:18:21 EDT LOG:  received fast shutdown request
2016-05-19 10:18:21 EDT LOG:  aborting any active transactions
2016-05-19 10:18:21 EDT LOG:  autovacuum launcher shutting down
2016-05-19 10:18:21 EDT LOG:  shutting down
2016-05-19 10:18:21 EDT LOG:  database system is shut down
2016-05-19 10:18:29 EDT LOG:  database system was shut down at 2016-05-19 10:18:21 EDT
2016-05-19 10:18:29 EDT LOG:  autovacuum launcher started
2016-05-19 10:18:29 EDT LOG:  database system is ready to accept connections


VERIFIED With sat62-snap12.1
Comment 6 Bryan Kearney 2016-07-27 11:08:44 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/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.