<?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 Re: Service Guard Troubles in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/service-guard-troubles/m-p/4977686#M57108</link>
    <description>It seemed that the locklun was corrupt, fixed it by applying the config again (when the cluster was down).</description>
    <pubDate>Tue, 16 May 2006 07:40:16 GMT</pubDate>
    <dc:creator>ralfbosz</dc:creator>
    <dc:date>2006-05-16T07:40:16Z</dc:date>
    <item>
      <title>Service Guard Troubles</title>
      <link>https://community.hpe.com/t5/operating-system-linux/service-guard-troubles/m-p/4977684#M57106</link>
      <description>Let me start with the statistics:&lt;BR /&gt;&lt;BR /&gt;OS: Red Hat Enterprise Linux AS release 3 (Taroon Update 5)&lt;BR /&gt;SW: serviceguard-A.11.15.04-0&lt;BR /&gt;&lt;BR /&gt;After some hardware trouble we have problems starting the cluster up. Starting the cluster on one node works fine, but when introducing the second node all fails. I've attached the syslog, due to it's size...&lt;BR /&gt;&lt;BR /&gt;The strangest thing I notice are the lines:&lt;BR /&gt;&lt;BR /&gt;May  5 21:47:35 node2 cmsrvassistd[1419]: The cluster daemon aborted our connection.&lt;BR /&gt;May  5 21:47:35 node2 cmsrvassistd[1419]: Lost connection with ServiceGuard cluster daemon (cmcld): Software caused connection abort&lt;BR /&gt;&lt;BR /&gt;And the mention that it's using a quorom-server, when that's not the case.&lt;BR /&gt;&lt;BR /&gt;Anybody on this forum maybe got a clue where too look?</description>
      <pubDate>Mon, 08 May 2006 04:27:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/service-guard-troubles/m-p/4977684#M57106</guid>
      <dc:creator>ralfbosz</dc:creator>
      <dc:date>2006-05-08T04:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard Troubles</title>
      <link>https://community.hpe.com/t5/operating-system-linux/service-guard-troubles/m-p/4977685#M57107</link>
      <description>It seems your system has had a major problem, as the cmcld died with :&lt;BR /&gt;: The ServiceGuard daemon, /usr/local/cm&lt;BR /&gt;cluster/bin/cmcld[1391], died upon receiving signal number 11.&lt;BR /&gt;You should log a call with your local HP Response Centre to get assistance for this.&lt;BR /&gt;</description>
      <pubDate>Mon, 08 May 2006 04:43:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/service-guard-troubles/m-p/4977685#M57107</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2006-05-08T04:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard Troubles</title>
      <link>https://community.hpe.com/t5/operating-system-linux/service-guard-troubles/m-p/4977686#M57108</link>
      <description>It seemed that the locklun was corrupt, fixed it by applying the config again (when the cluster was down).</description>
      <pubDate>Tue, 16 May 2006 07:40:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/service-guard-troubles/m-p/4977686#M57108</guid>
      <dc:creator>ralfbosz</dc:creator>
      <dc:date>2006-05-16T07:40:16Z</dc:date>
    </item>
  </channel>
</rss>

