Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1282600 +++
Description of problem:
Now that rpc.gssd is the critical path of every
NFS mount, any favored mount, I thought I would
take a crack at making the daemon a bit more
debuggable by making the logging more readable.
The first level of debugging (-v) will only log
errors and warnings that are not normally logged.
I'm thinking this might be a good level to run
at a customer's site.
I also thought about changing the majority of the
printerr(0) which always log to printerr(1)s. I
decided not to since I figured more info is
better.
Note, I didn't remove any of the messages, I just pushed
them back to other debug levels.
I trimmed down the second level of debugging (-vv)
by again moving them back to other levels.
The third level (-vvv) is basically the same.
Using the fourth level (-vvvv) to enable all the logging
that old level three did.
--- Additional comment from Steve Dickson on 2015-11-16 15:52:18 EST ---
Needed upstream commits:
commit 217a0ef3126ceb1126e3492e7b35cbb5596e13f6
Author: Steve Dickson <steved>
Date: Sat Nov 7 12:51:37 2015 -0500
gssd: reworked second level of debugging
commit 210a728b1ce99a6e59ed0d994eabc8ea90158729
Author: Steve Dickson <steved>
Date: Sat Nov 7 11:31:40 2015 -0500
gssd: log all fatal errors
commit 4eb495c8eeb2dd3183b4dbc0a238c8e0e76e9237
Author: Steve Dickson <steved>
Date: Sat Nov 7 11:24:30 2015 -0500
gssd: reworked first level of debugging
--- Additional comment from Steve Dickson on 2015-11-16 16:12:04 EST ---
(In reply to Steve Dickson from comment #1)
> Needed upstream commits:
These are the real commits ids:
commit be40202f194877306c19929479114b90a08363c1
Author: Steve Dickson <steved>
Date: Sat Nov 7 12:51:37 2015 -0500
gssd: reworked second level of debugging
commit f1172857775d7be47b9ffb51825001cf39e23e70
Author: Steve Dickson <steved>
Date: Sat Nov 7 11:31:40 2015 -0500
gssd: log all fatal errors
When gssd exist ensure a error message is logged.
Signed-off-by: Steve Dickson <steved>
commit 329d4685ace7659a50517cc2f4d8c926d6aec500
Author: Steve Dickson <steved>
Date: Sat Nov 7 11:24:30 2015 -0500
gssd: reworked first level of debugging