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.
Description of problem:
While trying to debug a startup hang I wanted to use the "-d 2" option to dump debug messages to syslog while starting up as normal. Unfortunately clvmd does not run in the background in this case.
Version-Release number of selected component (if applicable):
lvm2-cluster-2.02.65-1.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. clvmd -d 2
2. clvmd should continue running while returning you to the command prompt.
Actual results:
clvmd runs in the foreground
Expected results:
clvmd run in the background
Additional info:
From the man page for clvmd:
OPTIONS
-d [<value>]
Enable debug logging. Value can be 0, 1 or 2.
0 disables debug logging in a running clvmd
1 sends debug logs to stderr (clvmd will not fork in this case)
2 sends debug logs to syslog
If -d is specified without a value then 1 is assumed if you are
starting a new clvmd, 2 if you are enabling debug in a running
clvmd.
Comment 2Christine Caulfield
2010-05-26 16:17:35 UTC
The real problem is the -d is overloaded. there should be a separate flag to indicate to clvmd that it should not fork.
Can this be fixed as documented so I can debug startup timeouts?
Comment 5RHEL Program Management
2010-06-07 16:04:35 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 6RHEL Program Management
2010-07-15 14:30:11 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
(In reply to comment #0)
> Steps to Reproduce:
> 1. clvmd -d 2
> 2. clvmd should continue running while returning you to the command prompt.
One important note:
Please be aware of the fact that you have to use "clvmd -d2" not "clvmd -d 2" (leave the space out!).
Fix verified in the latest rpms.
* Note: like mentioned in comment #10, "clvmd -d2" not "clvmd -d 2" is what's required for this to work. "clvmd -d 2" evals to no argument, and thus is the same as -d1.
2.6.32-128.el6.x86_64
lvm2-2.02.83-3.el6 BUILT: Fri Mar 18 09:31:10 CDT 2011
lvm2-libs-2.02.83-3.el6 BUILT: Fri Mar 18 09:31:10 CDT 2011
lvm2-cluster-2.02.83-3.el6 BUILT: Fri Mar 18 09:31:10 CDT 2011
udev-147-2.35.el6 BUILT: Wed Mar 30 07:32:05 CDT 2011
device-mapper-1.02.62-3.el6 BUILT: Fri Mar 18 09:31:10 CDT 2011
device-mapper-libs-1.02.62-3.el6 BUILT: Fri Mar 18 09:31:10 CDT 2011
device-mapper-event-1.02.62-3.el6 BUILT: Fri Mar 18 09:31:10 CDT 2011
device-mapper-event-libs-1.02.62-3.el6 BUILT: Fri Mar 18 09:31:10 CDT 2011
cmirror-2.02.83-3.el6 BUILT: Fri Mar 18 09:31:10 CDT 2011
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0772.html