cmruncl error---Timer_loop

[ksama]

OS: SLES 9
SG :serviceguard-A.11.16.07-0.product.suse.x86_64.rpm
I have executed the folllowing commands to configure and construct my cluster my cluster

cmquerycl -v -L /dev/sda1 -n node3 -n node4 -C $SGCONF/cluster34.config

I have customize my conf file

cmapplyconf -v -C $SGCONF/cluster34.config

When I try to run my cluster with cmruncl I got the following errors

Nov 8 13:14:40 node4 cmcld[26270]: Timer_loop has been in sigwait since tsb (57521,652379656) for 897s (0,146977656)
Nov 8 13:14:40 node4 cmcld[26270]: Timer_loop's previous check_timers started at tsb (57521,652379656) and lasted 0s (0,0) executed 1 callbacks
Nov 8 13:14:40 node4 cmcld[26270]: Timer_loop's previous sigwait started at tsb (57521,650379960) and lasted 2817s (0,1999696)
Nov 8 13:14:40 node4 cmcld[26270]: Timer_loop's previous cm_lock started at tsb (57521,652379656) and lasted 0s (0,0)
Nov 8 13:14:40 node4 cmcld[26270]: Timer_loop's last timer callback (type=0,id=0) started at tsb (0,0) and lasted 0s (0,0)
Nov 8 13:14:40 node4 cmcld[26270]: Timer_loop's last greater than 1s timer callback (type=0,id=0) started at tsb (0,0) and lasted 0s (0,0)
Nov 8 13:14:50 node4 cmcld[26270]: Assertion failed: (overrun_tsb).tsb_hi == 0, file: cm/timers.c, line: 1495
Nov 8 13:14:50 node4 cmsrvassistd[26297]: The cluster daemon aborted our connection.
Nov 8 13:14:50 node4 cmsrvassistd[26297]: Lost connection with Serviceguard cluster daemon (cmcld): Software caused connection abort
Nov 8 13:14:55 node4 cmclconfd[26269]: The Serviceguard daemon, /opt/cmcluster/bin/cmcld[26270], died upon receiving signal number 6.

Your quick help will be appreciated

[Serviceguard for Linux]

One quick question - are you running SLES9 base or are you running a servicepack? If you are running just the base version, that is not supported.

If you are running a servicepack, then I'd put in a support call.

[Srinivas Krishnappa Sha]

Hi,

I hope you Installed the Patch on top of the MR bits and you did follow the guidelines mentioned in the patch document.