RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1253055 - Xorg log does not exist in RHEL 7.2
Summary: Xorg log does not exist in RHEL 7.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdm
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
: 1255913 (view as bug list)
Depends On:
Blocks: 1190227
TreeView+ depends on / blocked
 
Reported: 2015-08-12 20:36 UTC by Swapna Krishnan
Modified: 2015-11-19 07:16 UTC (History)
3 users (show)

Fixed In Version: gdm-3.14.2-12.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 07:16:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2216 0 normal SHIPPED_LIVE gnome compositor stack bug fix and enhancement update 2015-11-19 08:26:34 UTC

Description Swapna Krishnan 2015-08-12 20:36:32 UTC
Description of problem:
There's no Xorg logs in RHEL 7.2 in /var/log. However, display driver messages are present in /var/log/messages

Version-Release number of selected component (if applicable):
xorg-x11-drv-qxl-0.1.1-16.el7.x86_64
gdm-3.14.2-10.el7.x86_64
xorg-x11-server-Xorg-1.17.2-5.el7.x86_64

How reproducible:
100%

Comment 2 Tomas Pelka 2015-08-13 06:59:14 UTC
My guess it is because 

root      1798  0.0  0.8 431784 104684 tty1    Ssl+ Aug11   2:12 /usr/bin/Xorg :0 -background none -noreset -audit 4 -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-oTTj9L/database -seat seat0 -nolisten tcp vt1

Is it expected Xorg is running with "-logfile /dev/null"

Comment 3 Ray Strode [halfline] 2015-08-13 15:15:57 UTC
it was an intentional upstream change to move X logging to the journal.  The journal gets mirrored to /var/log/messages by rsyslog in RHEL7 (but we don't use rsyslog in recent versions of fedora).

Whether or not we should keep 7.2 like this, I'm not completely sure.  Customers might get thrown off by the logs moving.  Also in RHEL 6, customers complained when certain GDM logs ended up in syslog ( see bug 834303 )

So I'm thinking we should probably change the logs back to the same locations as 7.1 to be conservative and customer friendly.

Comment 5 Ray Strode [halfline] 2015-08-25 15:43:45 UTC
*** Bug 1255913 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2015-11-19 07:16:37 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://rhn.redhat.com/errata/RHBA-2015-2216.html


Note You need to log in before you can comment on or make changes to this bug.