Bug 183514
Summary: | excess gulm debugging may fill the logs | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Corey Marthaler <cmarthal> |
Component: | gulm | Assignee: | Chris Feist <cfeist> |
Status: | CLOSED NOTABUG | QA Contact: | Cluster QE <mspqa-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4 | CC: | cluster-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-03-01 17:59:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Corey Marthaler
2006-03-01 17:14:14 UTC
I think you're starting up lock_gulmd with verbose options. Can you provide me the logs from when lock_gulmd starts? You may also be using the wrong rpms, can you verify that you're using gulm-1.0.6-0? In the future it makes it easier for the developers if you list the exact version of the rpm you're reporting the problem against. I inheirited these machines from Nate and didn't realize that he had the debug gulm rpm. Closing... |