<?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: SMIserver crashes in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989445#M83480</link>
    <description>Check ACCOUNTNG.DAT for the exit status of the SMISERVER. That might yeild some clues. The SMISERVER process changes its personna so any problems with the target account will manifest themselves in the behavior of the server. For example, if a job running under a username that has become "disusered" invokes SYSMAN to visit a node it will cause the SMISERVER to abort.</description>
    <pubDate>Thu, 26 Apr 2007 09:35:55 GMT</pubDate>
    <dc:creator>Jim_McKinney</dc:creator>
    <dc:date>2007-04-26T09:35:55Z</dc:date>
    <item>
      <title>SMIserver crashes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989444#M83479</link>
      <description>Hello everybody,&lt;BR /&gt;&lt;BR /&gt;Sometimes, and sometimes very often, the smiserver process is gone.&lt;BR /&gt;Is there a way to get a dump or logging information, so we can send this to HP.&lt;BR /&gt;&lt;BR /&gt;Greetings,&lt;BR /&gt;&lt;BR /&gt;Piet</description>
      <pubDate>Thu, 26 Apr 2007 09:24:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989444#M83479</guid>
      <dc:creator>Piet Timmers_1</dc:creator>
      <dc:date>2007-04-26T09:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: SMIserver crashes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989445#M83480</link>
      <description>Check ACCOUNTNG.DAT for the exit status of the SMISERVER. That might yeild some clues. The SMISERVER process changes its personna so any problems with the target account will manifest themselves in the behavior of the server. For example, if a job running under a username that has become "disusered" invokes SYSMAN to visit a node it will cause the SMISERVER to abort.</description>
      <pubDate>Thu, 26 Apr 2007 09:35:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989445#M83480</guid>
      <dc:creator>Jim_McKinney</dc:creator>
      <dc:date>2007-04-26T09:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: SMIserver crashes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989446#M83481</link>
      <description>Do check accounting and process-level security auditing, and there can be process dump files created from various process-level crashes, and do check the ECO level as there have been various fixes for SMI.&lt;BR /&gt;&lt;BR /&gt;ANALYZE/PROCESS SYS$SYSTEM:SMISERVER.DMP, IIRC.&lt;BR /&gt;&lt;BR /&gt;Do consider direct contact with HP services.  This sort of bug-hunting expertise is usually what HP customer support provides.  They have the maps, and access to any existing related customer QuIX reports against SMISERVER, et al.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 26 Apr 2007 10:04:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989446#M83481</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-04-26T10:04:43Z</dc:date>
    </item>
    <item>
      <title>Re: SMIserver crashes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989447#M83482</link>
      <description>gone or not responding. curious what version of vms. in the early days we&lt;BR /&gt;had a lot of problems with sysman hanging on&lt;BR /&gt;wedged smi processes on nodes. I've included&lt;BR /&gt;some dcl to fix that one for older vms versions. Dean</description>
      <pubDate>Thu, 26 Apr 2007 11:42:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989447#M83482</guid>
      <dc:creator>Dean McGorrill</dc:creator>
      <dc:date>2007-04-26T11:42:14Z</dc:date>
    </item>
    <item>
      <title>Re: SMIserver crashes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989448#M83483</link>
      <description>What version of VMS?  There are ECOs out that update the smiserver, are these installed?  When restarted, are you restarting the SMIserver from the system account?  &lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Tue, 01 May 2007 11:55:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smiserver-crashes/m-p/3989448#M83483</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2007-05-01T11:55:00Z</dc:date>
    </item>
  </channel>
</rss>

