Bug 183514

Summary: excess gulm debugging may fill the logs
Product: [Retired] Red Hat Cluster Suite Reporter: Corey Marthaler <cmarthal>
Component: gulmAssignee: Chris Feist <cfeist>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: low    
Version: 4CC: 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
Description of problem:
Mar  1 11:10:55 morph-03 lock_gulmd_core[27789]: Got heartbeat from morph-01 at
1141233055298022 (last:10000481 max:3297015203 avg:35680318)
Mar  1 11:10:56 morph-03 lock_gulmd_core[27789]: Got heartbeat from morph-02 at
1141233056674460 (last:10000499 max:3296338080 avg:16364497)
Mar  1 11:10:56 morph-03 lock_gulmd_core[27789]: Got heartbeat from morph-04 at
1141233056696449 (last:10001127 max:10001123 avg:9930763)
Mar  1 11:11:04 morph-03 lock_gulmd_core[27789]: Got heartbeat from morph-03 at
1141233064668781 (last:10001480 max:3293579954 avg:22827268)
Mar  1 11:11:05 morph-03 lock_gulmd_core[27789]: Got heartbeat from morph-01 at
1141233065298539 (last:10000517 max:3297015203 avg:22840399)
Mar  1 11:11:06 morph-03 lock_gulmd_core[27789]: Got heartbeat from morph-02 at
1141233066674957 (last:10000497 max:3296338080 avg:13182498)
Mar  1 11:11:06 morph-03 lock_gulmd_core[27789]: Got heartbeat from morph-04 at
1141233066697442 (last:10000993 max:10001127 avg:9965945)
Mar  1 11:11:14 morph-03 lock_gulmd_core[27789]: Got heartbeat from morph-03 at
1141233074670260 (last:10001479 max:3293579954 avg:16414374)


Version-Release number of selected component (if applicable):
[root@morph-03 ~]# uname -ar
Linux morph-03 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 i686 i386 GNU/Linux

Comment 1 Chris Feist 2006-03-01 17:33:48 UTC
I think you're starting up lock_gulmd with verbose options.  Can you provide me
the logs from when lock_gulmd starts?

Comment 2 Chris Feist 2006-03-01 17:53:56 UTC
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.

Comment 3 Corey Marthaler 2006-03-01 17:59:04 UTC
I inheirited these machines from Nate and didn't realize that he had the debug
gulm rpm. Closing...