<?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: Server Crash in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588894#M857161</link>
    <description>arvdev is actually the name of the server. I think your probably right. I wonder why it occurs because it just reboots and comes back up and everything is fine for a while.</description>
    <pubDate>Wed, 03 Oct 2001 09:23:52 GMT</pubDate>
    <dc:creator>unixdaddy</dc:creator>
    <dc:date>2001-10-03T09:23:52Z</dc:date>
    <item>
      <title>Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588891#M857158</link>
      <description>One of my servers keeps crashing. In the OLDsyslog.log it gives the information below. Can anyone tell me what it means?&lt;BR /&gt;&lt;BR /&gt;Oct  7 15:26:13 arvdev vmunix:  cdb: 00 00 00 00 00 00&lt;BR /&gt;Oct  7 15:26:13 arvdev vmunix:  status: (02) Check Condition&lt;BR /&gt;Oct  7 15:26:13 arvdev vmunix:  sense data: 70 00 06 00 00 00 00 0e 00 00 00 00 &lt;BR /&gt;29 00 00 00&lt;BR /&gt;Oct  7 15:26:13 arvdev vmunix:              00 00 00 00 00 00&lt;BR /&gt;Oct  7 15:26:13 arvdev vmunix:  sense key: (06) Unit Attention&lt;BR /&gt;Oct  7 15:26:13 arvdev vmunix:  additional sense code: (29)&lt;BR /&gt;Oct  7 15:26:13 arvdev vmunix:  additional sense code qualifier: (00)&lt;BR /&gt;Oct  7 15:26:27 arvdev /usr/sbin/envd[991]: terminated by signal 15&lt;BR /&gt;Oct  7 10:26:37 arvdev inetd[1522]: Going down on signal 15</description>
      <pubDate>Wed, 03 Oct 2001 08:48:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588891#M857158</guid>
      <dc:creator>unixdaddy</dc:creator>
      <dc:date>2001-10-03T08:48:39Z</dc:date>
    </item>
    <item>
      <title>Re: Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588892#M857159</link>
      <description>&lt;BR /&gt;I have no idea what the driver arvdev is, some sort of 3rd part product ?? anyway, the errors you see look like SCSI hardware connection errors pointing to a problem with the device, eventually it causes a crash. Are your patches uptodate ? Keeping your patches uptodate usually stops the crashes, but youve got to investigate the hardware connection problem also.</description>
      <pubDate>Wed, 03 Oct 2001 09:08:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588892#M857159</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2001-10-03T09:08:01Z</dc:date>
    </item>
    <item>
      <title>Re: Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588893#M857160</link>
      <description>Hi, &lt;BR /&gt;There can be other problems (indicated by inetd going down on signal 15), if you have trusted system. If so, try to install also patches for inetd (PHNE_21835).&lt;BR /&gt;&lt;BR /&gt;Later,</description>
      <pubDate>Wed, 03 Oct 2001 09:22:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588893#M857160</guid>
      <dc:creator>Marcin Wicinski</dc:creator>
      <dc:date>2001-10-03T09:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588894#M857161</link>
      <description>arvdev is actually the name of the server. I think your probably right. I wonder why it occurs because it just reboots and comes back up and everything is fine for a while.</description>
      <pubDate>Wed, 03 Oct 2001 09:23:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588894#M857161</guid>
      <dc:creator>unixdaddy</dc:creator>
      <dc:date>2001-10-03T09:23:52Z</dc:date>
    </item>
    <item>
      <title>Re: Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588895#M857162</link>
      <description>are you getting a dump in /var/adm/crash&lt;BR /&gt;when the server reboots.&lt;BR /&gt;&lt;BR /&gt;If so you could run &lt;BR /&gt;# q4 -p /var/adm/crash/crash.X&lt;BR /&gt;q4&amp;gt; run WhatHappened &amp;gt; /tmp/wh.X&lt;BR /&gt;q4&amp;gt; quit&lt;BR /&gt;# vi /tmp/wh.X&lt;BR /&gt;and try to search the patch db for stack trace id's... or send that to your support with an swlist output&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Wed, 03 Oct 2001 10:06:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588895#M857162</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-10-03T10:06:09Z</dc:date>
    </item>
    <item>
      <title>Re: Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588896#M857163</link>
      <description>I'm afraid there is nothing in /var/adm/crash.</description>
      <pubDate>Wed, 03 Oct 2001 11:42:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588896#M857163</guid>
      <dc:creator>unixdaddy</dc:creator>
      <dc:date>2001-10-03T11:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588897#M857164</link>
      <description>Darren-&lt;BR /&gt;&lt;BR /&gt;I don't suppose that you could be lucky and have it always go down at the same time?  You should be able to get times from /etc/shutdownlog.  Also, do you have Online diagnostics installed (stm)?  If not, maybe you should put it on.  It a free download or it's on the application cd.  If there is a hardware issue, it should give some warnings or errors that might help you track it down.&lt;BR /&gt;&lt;BR /&gt;Mark</description>
      <pubDate>Wed, 03 Oct 2001 12:04:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588897#M857164</guid>
      <dc:creator>Mark Vollmers</dc:creator>
      <dc:date>2001-10-03T12:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588898#M857165</link>
      <description>Hi Darren,&lt;BR /&gt;&lt;BR /&gt;Can you attach your OLDsyslog.log file. Let us have a look at that. Seems like you are having a disk problem. Which disk (?) is a big question.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Wed, 03 Oct 2001 12:05:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588898#M857165</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2001-10-03T12:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: Server Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588899#M857166</link>
      <description>Darren,&lt;BR /&gt;&lt;BR /&gt;It may be some change in your computer room temperature.  An envd entry in your log may indicate whatever environmental conditions you have specified in /etc/envd.conf (OVERTEMP) file.  Are you in a hot climate location?&lt;BR /&gt;&lt;BR /&gt;E.</description>
      <pubDate>Wed, 03 Oct 2001 13:51:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-crash/m-p/2588899#M857166</guid>
      <dc:creator>E. Wong</dc:creator>
      <dc:date>2001-10-03T13:51:08Z</dc:date>
    </item>
  </channel>
</rss>

