<?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: Automatic rebooting of K200 server in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523594#M23968</link>
    <description>you should also take a look at the /var/tombstones/&lt;LAST one=""&gt;  look at the HPMC chassis codes for a hint of the type of failures it is recording.&lt;/LAST&gt;</description>
    <pubDate>Wed, 02 May 2001 14:12:43 GMT</pubDate>
    <dc:creator>boley janowski</dc:creator>
    <dc:date>2001-05-02T14:12:43Z</dc:date>
    <item>
      <title>Automatic rebooting of K200 server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523589#M23963</link>
      <description>Hi all &lt;BR /&gt;&lt;BR /&gt; I am having a k200 server . which is automatically  rebooting almost every day . and it is not making any entries in syslog. but in /etc/shutdownlog it is giving the following message&lt;BR /&gt;07:53  Wed May 02 2001.  Reboot after panic: ialloc: dup alloc&lt;BR /&gt;&lt;BR /&gt;what does it means .. and how do i solve this issue .&lt;BR /&gt;&lt;BR /&gt;thanks in advance&lt;BR /&gt;&lt;BR /&gt;shajith.t&lt;BR /&gt;</description>
      <pubDate>Wed, 02 May 2001 02:07:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523589#M23963</guid>
      <dc:creator>SHAJITH_2</dc:creator>
      <dc:date>2001-05-02T02:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic rebooting of K200 server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523590#M23964</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;may be some file system corrupt, boot to single user and fsck all file system.&lt;BR /&gt;in vxfs please also use option -o full</description>
      <pubDate>Wed, 02 May 2001 02:57:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523590#M23964</guid>
      <dc:creator>Printaporn_1</dc:creator>
      <dc:date>2001-05-02T02:57:02Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic rebooting of K200 server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523591#M23965</link>
      <description>Another thing to establish is does the reboot happen at the same time every day or is it random. What do you have running on the system? &lt;BR /&gt;&lt;BR /&gt;Have you made any changes to the system recently like new hardware/software or kernel changes?</description>
      <pubDate>Wed, 02 May 2001 06:39:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523591#M23965</guid>
      <dc:creator>Barry O Flanagan</dc:creator>
      <dc:date>2001-05-02T06:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic rebooting of K200 server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523592#M23966</link>
      <description>Verify SCSI termination and PIN of cables.</description>
      <pubDate>Wed, 02 May 2001 08:33:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523592#M23966</guid>
      <dc:creator>Vincenzo Restuccia</dc:creator>
      <dc:date>2001-05-02T08:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic rebooting of K200 server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523593#M23967</link>
      <description>the message Reboot after panic: ialloc: dup alloc &lt;BR /&gt;&lt;BR /&gt;indicates you have a duplicate inode allocation being attempted, which is illegal and causes the system to panic.&lt;BR /&gt;If the dump is analysed, you will be able to tell which file system is causing the corruption (because this is what is the usual cause).&lt;BR /&gt;Failing that, reboot the system to single user mode and do an fsck -o full on ALL file systems.&lt;BR /&gt;There is also a remot epossibility you have a disc that is dodgy.&lt;BR /&gt;I would get the dump analysed for the best information.</description>
      <pubDate>Wed, 02 May 2001 10:09:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523593#M23967</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-05-02T10:09:16Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic rebooting of K200 server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523594#M23968</link>
      <description>you should also take a look at the /var/tombstones/&lt;LAST one=""&gt;  look at the HPMC chassis codes for a hint of the type of failures it is recording.&lt;/LAST&gt;</description>
      <pubDate>Wed, 02 May 2001 14:12:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-rebooting-of-k200-server/m-p/2523594#M23968</guid>
      <dc:creator>boley janowski</dc:creator>
      <dc:date>2001-05-02T14:12:43Z</dc:date>
    </item>
  </channel>
</rss>

