<?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: congealed server? problems in server in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054375#M813441</link>
    <description>It looks like you have networking problems.  Have you checked your router or switch and make sure it is OK?</description>
    <pubDate>Thu, 21 Aug 2003 20:24:22 GMT</pubDate>
    <dc:creator>Patrick Wallek</dc:creator>
    <dc:date>2003-08-21T20:24:22Z</dc:date>
    <item>
      <title>congealed server? problems in server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054372#M813438</link>
      <description>hello my server its online suddenly lost conecction ssh, all services , console, &lt;BR /&gt;only have ping .&lt;BR /&gt;the leds ok run ok attention none faild none&lt;BR /&gt;no response my shell ,no respond nothing.&lt;BR /&gt;&lt;BR /&gt;send to signal via gsp rst .&lt;BR /&gt;the server dmes ok syslog nothing , only logs of chasis stmm :&lt;BR /&gt;-rw-r--r--   1 root       root        110288 Aug 21 10:34 ccbootlog.36&lt;BR /&gt;-rw-r--r--   1 root       root          6912 Aug 21 12:46 ccbootlog.37&lt;BR /&gt;-rw-r--r--   1 root       root         69196 Aug 21 16:55 memlog&lt;BR /&gt;-rw-r--r--   1 root       root          7184 Aug 21 16:55 ccbootlog.38&lt;BR /&gt;-rw-r--r--   1 root       sys          41312 Aug 21 16:55 ccerrlog&lt;BR /&gt;-rw-r--r--   1 root       root          6768 Aug 21 17:31 ccbootlog&lt;BR /&gt;as it can be the problem&lt;BR /&gt;the server model is: &lt;BR /&gt;nms1 # model&lt;BR /&gt;9000/800/L1000-36&lt;BR /&gt;software AND services: NNM,ITO,DNS,Omniback,NETRANGE,ids,agent the ciscoworks, mwa,pv,&lt;BR /&gt;thanks</description>
      <pubDate>Thu, 21 Aug 2003 19:40:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054372#M813438</guid>
      <dc:creator>Jairo Campana</dc:creator>
      <dc:date>2003-08-21T19:40:35Z</dc:date>
    </item>
    <item>
      <title>Re: congealed server? problems in server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054373#M813439</link>
      <description>I would be quite suspicious of this situation.&lt;BR /&gt;&lt;BR /&gt;It would appear that someone has taken this box and brought it down to run level 1 or 2.&lt;BR /&gt;&lt;BR /&gt;I'd think maybe an internal disk failed, but those L class boxes generally ship with one or two disks, so there'd be no system if the disk went.  I generally mirror from one disk to another.&lt;BR /&gt;&lt;BR /&gt;So the question is, who had access and what did they do?&lt;BR /&gt;&lt;BR /&gt;I have seen NIC failures that work like this. The card is alive but will only answer ping.&lt;BR /&gt;&lt;BR /&gt;Diagnostic steps:&lt;BR /&gt;&lt;BR /&gt;1) get on the console and run who -r what is the run level. &lt;BR /&gt;&lt;BR /&gt;2) ps -ef | grep ssh  see if secure shell is still running.&lt;BR /&gt;&lt;BR /&gt;3) dmesg look for hardware problems related to the NIC.&lt;BR /&gt;&lt;BR /&gt;4) Reboot the system, shutdown -ry now its not doing anything useful anyway.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 21 Aug 2003 19:48:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054373#M813439</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-08-21T19:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: congealed server? problems in server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054374#M813440</link>
      <description>nms1 # who -r&lt;BR /&gt;   .       run-level 3  Aug 21 16:52    3    0    S&lt;BR /&gt;&lt;BR /&gt;nms1 # ps -ef|grep sshd&lt;BR /&gt;    root  1330     1  0 16:55:26 ?         0:02 /opt/openssh2/sbin/sshd&lt;BR /&gt;    root  1947  1330  0 16:56:38 ?         0:02 sshd: CampanaJ@0&lt;BR /&gt;    root 27403  2012  0 18:12:46 pts/0     0:00 grep sshd&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;btlan3: NOTE: MII Link Status Not OK - Switch Connection to AUI at 0/0/0/0....&lt;BR /&gt;&lt;BR /&gt;btlan: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/4/0/0/5/0....&lt;BR /&gt;&lt;BR /&gt;btlan: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/4/0/0/6/0....&lt;BR /&gt;&lt;BR /&gt;btlan3: Reset looper timeout: DMA timeout occurred at 0/0/0/0&lt;BR /&gt;&lt;BR /&gt;btlan3: reset state is 550 at 0/0/0/0....&lt;BR /&gt;&lt;BR /&gt;btlan3: WARNING: AUI Loopback Failed at 0/0/0/0....&lt;BR /&gt;&lt;BR /&gt;btlan: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/4/0/0/6/0....&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 21 Aug 2003 20:18:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054374#M813440</guid>
      <dc:creator>Jairo Campana</dc:creator>
      <dc:date>2003-08-21T20:18:06Z</dc:date>
    </item>
    <item>
      <title>Re: congealed server? problems in server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054375#M813441</link>
      <description>It looks like you have networking problems.  Have you checked your router or switch and make sure it is OK?</description>
      <pubDate>Thu, 21 Aug 2003 20:24:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/congealed-server-problems-in-server/m-p/3054375#M813441</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2003-08-21T20:24:22Z</dc:date>
    </item>
  </channel>
</rss>

