<?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 REBOOTING in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/server-rebooting/m-p/2554299#M28542</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I think your problem is not the SIZE of the swap but rather a bad (or at least bad sectors) on the swap disk itself. When you increased memory, the box no longer had to swap&lt;BR /&gt;and the problem seemed to go away. As soon as load increases and swapping starts the problem will reappear. If this is a critical server, then I would install Mirror/UX and mirror my boot/swap disks so that a disk problem would not be a serious issue.&lt;BR /&gt;This box probably survived burn-in because the tests dis not induce much swapping.&lt;BR /&gt;&lt;BR /&gt;Hope this helps, Clay</description>
    <pubDate>Wed, 18 Jul 2001 14:09:34 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2001-07-18T14:09:34Z</dc:date>
    <item>
      <title>SERVER REBOOTING</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-rebooting/m-p/2554298#M28541</link>
      <description>HAI ALL,&lt;BR /&gt;        Iam facing a serious issue of server rebooting in a critical server in a bank. Tjis happened after the smps has burnt in that server. It is a D220, hpux 10.2 server.It has sybase appl. The memory was 64 MB.&lt;BR /&gt;&lt;BR /&gt;The server main board, processor card and smps was changed. In shutdown log it is giving Swap Device Error.&lt;BR /&gt;I increased Device swap space. still it persisted. but when I increased the server memory to 128 MB the rebooting suddenly stopped. But it is a temp . solution becuase the memory is of another cust.&lt;BR /&gt;&lt;BR /&gt;pls give solutions on this isssue..&lt;BR /&gt;&lt;BR /&gt;thanking you all  BINUKUTTAN</description>
      <pubDate>Wed, 18 Jul 2001 13:57:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-rebooting/m-p/2554298#M28541</guid>
      <dc:creator>BINUKUTTAN_1</dc:creator>
      <dc:date>2001-07-18T13:57:52Z</dc:date>
    </item>
    <item>
      <title>Re: SERVER REBOOTING</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-rebooting/m-p/2554299#M28542</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I think your problem is not the SIZE of the swap but rather a bad (or at least bad sectors) on the swap disk itself. When you increased memory, the box no longer had to swap&lt;BR /&gt;and the problem seemed to go away. As soon as load increases and swapping starts the problem will reappear. If this is a critical server, then I would install Mirror/UX and mirror my boot/swap disks so that a disk problem would not be a serious issue.&lt;BR /&gt;This box probably survived burn-in because the tests dis not induce much swapping.&lt;BR /&gt;&lt;BR /&gt;Hope this helps, Clay</description>
      <pubDate>Wed, 18 Jul 2001 14:09:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-rebooting/m-p/2554299#M28542</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-07-18T14:09:34Z</dc:date>
    </item>
    <item>
      <title>Re: SERVER REBOOTING</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/server-rebooting/m-p/2554300#M28543</link>
      <description>You can check if it is the swap area which is reporting disk problems by doing a dd on it;&lt;BR /&gt;&lt;BR /&gt;dd if=/dev/vg00/rlvol2 of=/dev/null bs=64k&lt;BR /&gt;&lt;BR /&gt;This is presuming a standard install where primary swap is lvol2. Obviously, do this out of hours in case it does cause a crash. If it does, or reports I/O error, then you have a filesystem block problem as Clay suggests, which will involve rebuilding your system as the only real way to fix a bad block is mediainit (low level format) the disk. If dd report X blocks in+out then its fine, you have another problem. Ive seen Sybase cause spirrious crashes before, especially with so little memory (64 MB!).&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Jul 2001 14:20:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/server-rebooting/m-p/2554300#M28543</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2001-07-18T14:20:36Z</dc:date>
    </item>
  </channel>
</rss>

