<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic cmruncl error---Timer_loop in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/cmruncl-error-timer-loop/m-p/3894609#M57329</link>
    <description>OS: SLES 9&lt;BR /&gt;SG :serviceguard-A.11.16.07-0.product.suse.x86_64.rpm&lt;BR /&gt;I have executed the folllowing commands to configure and construct my cluster my cluster&lt;BR /&gt;&lt;BR /&gt;cmquerycl -v -L /dev/sda1 -n node3 -n node4 -C $SGCONF/cluster34.config&lt;BR /&gt;&lt;BR /&gt;I have customize my conf file&lt;BR /&gt;&lt;BR /&gt;cmapplyconf -v -C $SGCONF/cluster34.config&lt;BR /&gt;&lt;BR /&gt;When I try to run my cluster with cmruncl I got the following errors &lt;BR /&gt;&lt;BR /&gt;Nov  8 13:14:40 node4 cmcld[26270]: Timer_loop has been in sigwait since tsb (57521,652379656) for 897s (0,146977656)&lt;BR /&gt;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&lt;BR /&gt;Nov  8 13:14:40 node4 cmcld[26270]: Timer_loop's previous sigwait started at tsb (57521,650379960) and lasted 2817s (0,1999696)&lt;BR /&gt;Nov  8 13:14:40 node4 cmcld[26270]: Timer_loop's previous cm_lock started at tsb (57521,652379656) and lasted 0s (0,0)&lt;BR /&gt;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)&lt;BR /&gt;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)&lt;BR /&gt;Nov  8 13:14:50 node4 cmcld[26270]: Assertion failed: (overrun_tsb).tsb_hi == 0, file: cm/timers.c, line: 1495&lt;BR /&gt;Nov  8 13:14:50 node4 cmsrvassistd[26297]: The cluster daemon aborted our connection.&lt;BR /&gt;Nov  8 13:14:50 node4 cmsrvassistd[26297]: Lost connection with Serviceguard cluster daemon (cmcld): Software caused connection abort&lt;BR /&gt;Nov  8 13:14:55 node4 cmclconfd[26269]: The Serviceguard daemon, /opt/cmcluster/bin/cmcld[26270], died upon receiving signal number 6.&lt;BR /&gt;&lt;BR /&gt;Your quick help will be appreciated</description>
    <pubDate>Wed, 08 Nov 2006 06:57:59 GMT</pubDate>
    <dc:creator>ksama</dc:creator>
    <dc:date>2006-11-08T06:57:59Z</dc:date>
    <item>
      <title>cmruncl error---Timer_loop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cmruncl-error-timer-loop/m-p/3894609#M57329</link>
      <description>OS: SLES 9&lt;BR /&gt;SG :serviceguard-A.11.16.07-0.product.suse.x86_64.rpm&lt;BR /&gt;I have executed the folllowing commands to configure and construct my cluster my cluster&lt;BR /&gt;&lt;BR /&gt;cmquerycl -v -L /dev/sda1 -n node3 -n node4 -C $SGCONF/cluster34.config&lt;BR /&gt;&lt;BR /&gt;I have customize my conf file&lt;BR /&gt;&lt;BR /&gt;cmapplyconf -v -C $SGCONF/cluster34.config&lt;BR /&gt;&lt;BR /&gt;When I try to run my cluster with cmruncl I got the following errors &lt;BR /&gt;&lt;BR /&gt;Nov  8 13:14:40 node4 cmcld[26270]: Timer_loop has been in sigwait since tsb (57521,652379656) for 897s (0,146977656)&lt;BR /&gt;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&lt;BR /&gt;Nov  8 13:14:40 node4 cmcld[26270]: Timer_loop's previous sigwait started at tsb (57521,650379960) and lasted 2817s (0,1999696)&lt;BR /&gt;Nov  8 13:14:40 node4 cmcld[26270]: Timer_loop's previous cm_lock started at tsb (57521,652379656) and lasted 0s (0,0)&lt;BR /&gt;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)&lt;BR /&gt;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)&lt;BR /&gt;Nov  8 13:14:50 node4 cmcld[26270]: Assertion failed: (overrun_tsb).tsb_hi == 0, file: cm/timers.c, line: 1495&lt;BR /&gt;Nov  8 13:14:50 node4 cmsrvassistd[26297]: The cluster daemon aborted our connection.&lt;BR /&gt;Nov  8 13:14:50 node4 cmsrvassistd[26297]: Lost connection with Serviceguard cluster daemon (cmcld): Software caused connection abort&lt;BR /&gt;Nov  8 13:14:55 node4 cmclconfd[26269]: The Serviceguard daemon, /opt/cmcluster/bin/cmcld[26270], died upon receiving signal number 6.&lt;BR /&gt;&lt;BR /&gt;Your quick help will be appreciated</description>
      <pubDate>Wed, 08 Nov 2006 06:57:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cmruncl-error-timer-loop/m-p/3894609#M57329</guid>
      <dc:creator>ksama</dc:creator>
      <dc:date>2006-11-08T06:57:59Z</dc:date>
    </item>
    <item>
      <title>Re: cmruncl error---Timer_loop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cmruncl-error-timer-loop/m-p/3894610#M57330</link>
      <description>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.  &lt;BR /&gt;&lt;BR /&gt;If you are running a servicepack, then I'd put in a support call.</description>
      <pubDate>Thu, 09 Nov 2006 00:49:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cmruncl-error-timer-loop/m-p/3894610#M57330</guid>
      <dc:creator>Serviceguard for Linux</dc:creator>
      <dc:date>2006-11-09T00:49:27Z</dc:date>
    </item>
    <item>
      <title>Re: cmruncl error---Timer_loop</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cmruncl-error-timer-loop/m-p/3894611#M57331</link>
      <description>&lt;!--!*#--&gt;Hi, &lt;BR /&gt;&lt;BR /&gt;I hope you Installed the Patch on top of the MR bits and you did follow the guidelines mentioned in the patch document.</description>
      <pubDate>Thu, 14 Dec 2006 00:41:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cmruncl-error-timer-loop/m-p/3894611#M57331</guid>
      <dc:creator>Srinivas Krishnappa Sha</dc:creator>
      <dc:date>2006-12-14T00:41:45Z</dc:date>
    </item>
  </channel>
</rss>

