SMIserver crashes

[Piet Timmers_1]

Hello everybody,

Sometimes, and sometimes very often, the smiserver process is gone.
Is there a way to get a dump or logging information, so we can send this to HP.

Greetings,

Piet

[Jim_McKinney]

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.

[Hoff]

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.

ANALYZE/PROCESS SYS$SYSTEM:SMISERVER.DMP, IIRC.

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.

[Dean McGorrill]

gone or not responding. curious what version of vms. in the early days we
had a lot of problems with sysman hanging on
wedged smi processes on nodes. I've included
some dcl to fix that one for older vms versions. Dean

[Andy Bustamante]

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?

Andy