<?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 INIT in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204469#M673770</link>
    <description>Network problem</description>
    <pubDate>Fri, 16 Oct 2009 14:01:35 GMT</pubDate>
    <dc:creator>Unix Administration</dc:creator>
    <dc:date>2009-10-16T14:01:35Z</dc:date>
    <item>
      <title>Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204461#M673762</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;we experienced a crash of one of our vpars. Crashinfo gives the following informatio:&lt;BR /&gt;&lt;BR /&gt;Note: This is a Service Guard INIT !&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Note: It seems cmcld has been executed within the last 1 second,&lt;BR /&gt;nevertheless the system has been brought down by a INIT through the&lt;BR /&gt;safety timer mechanism.&lt;BR /&gt;Please contact HP support referencing CRASHINFO_NOTE_SG2.&lt;BR /&gt;Please contact HP support referencing CRASHINFO_NOTE_SG3.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Does anybody know what those crashinfo notes mean?</description>
      <pubDate>Thu, 15 Oct 2009 12:14:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204461#M673762</guid>
      <dc:creator>Unix Administration</dc:creator>
      <dc:date>2009-10-15T12:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204462#M673763</link>
      <description>I would call HP support and ask them.&lt;BR /&gt;&lt;BR /&gt;I just did a quick search of the public knowledge base and nothing came up.</description>
      <pubDate>Thu, 15 Oct 2009 12:24:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204462#M673763</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2009-10-15T12:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204463#M673764</link>
      <description>yes, i know. i couldn't find any hint either. I was hoping to get some information on my own. Opening a case is the easiest thing, but I would like to keep this option as the last one.&lt;BR /&gt;&lt;BR /&gt;I'm hoping smbd faced this before and maybe share the information. Anyway, the vpar is up, but the cause still needs to be established</description>
      <pubDate>Thu, 15 Oct 2009 12:57:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204463#M673764</guid>
      <dc:creator>Unix Administration</dc:creator>
      <dc:date>2009-10-15T12:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204464#M673765</link>
      <description>&amp;gt;&amp;gt;Opening a case is the easiest thing, but I would like to keep this option as the last one.&lt;BR /&gt;&lt;BR /&gt;Why?  You pay for support.  This is exactly why!  Use what you have!  Never feel bad about opening a support call!</description>
      <pubDate>Thu, 15 Oct 2009 13:07:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204464#M673765</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2009-10-15T13:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204465#M673766</link>
      <description>if the cmcld was running then check for network problems - syslog, nettl log and frdumps</description>
      <pubDate>Thu, 15 Oct 2009 15:41:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204465#M673766</guid>
      <dc:creator>Anka</dc:creator>
      <dc:date>2009-10-15T15:41:41Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204466#M673767</link>
      <description>&amp;gt;Please contact HP support referencing CRASHINFO_NOTE_SG2&lt;BR /&gt;&lt;BR /&gt;It sounds more like to get the clue from the crash ,you have t execute crashinfo utility and provide the output to HP for analysis. &lt;BR /&gt;&lt;BR /&gt;crashinfo is a HP tool, and available though the HP ftp site , when you open a call.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Do you have latest crash data under /var/adm/crash/ , if yes crashinfo will generate the ouput. &lt;BR /&gt;Also what is the output of /etc/shutdownlog .&lt;BR /&gt;Most of the time the small output (text) file can point to a fault  bad i/o, lan card.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hth,&lt;BR /&gt;Raj.</description>
      <pubDate>Thu, 15 Oct 2009 19:56:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204466#M673767</guid>
      <dc:creator>Raj D.</dc:creator>
      <dc:date>2009-10-15T19:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204467#M673768</link>
      <description>Crashinfo is an internal HP support too and should not be being used without an open support call. These messages refer HP staff to internal HP web sites and so when run outside of HP do not give the internal URLs away, since it would be pointless anyway.</description>
      <pubDate>Fri, 16 Oct 2009 06:52:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204467#M673768</guid>
      <dc:creator>John Bigg</dc:creator>
      <dc:date>2009-10-16T06:52:57Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204468#M673769</link>
      <description>&amp;gt;&amp;gt; crashinfo is a HP tool, and available though the HP ftp site , when you open a call.&lt;BR /&gt;&lt;BR /&gt;I know, this is how I got the information.&lt;BR /&gt;&lt;BR /&gt;Anyway, I managed to find out what hapened. The frdump showed me this was indeed a network problem. &lt;BR /&gt;&lt;BR /&gt;Thanks Anka, for the hint</description>
      <pubDate>Fri, 16 Oct 2009 13:52:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204468#M673769</guid>
      <dc:creator>Unix Administration</dc:creator>
      <dc:date>2009-10-16T13:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard INIT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204469#M673770</link>
      <description>Network problem</description>
      <pubDate>Fri, 16 Oct 2009 14:01:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-init/m-p/5204469#M673770</guid>
      <dc:creator>Unix Administration</dc:creator>
      <dc:date>2009-10-16T14:01:35Z</dc:date>
    </item>
  </channel>
</rss>

