[Info-vax] SYSMAN - insufficient event flags?
Stephen Hoffman
seaohveh at hoffmanlabs.invalid
Thu Feb 27 21:48:17 EST 2014
On 2014-02-27 23:45:02 +0000, mcleanjoh at gmail.com said:
> Just lately we've been seeing a problem with SYSMAN, a problem that
> returns the message(s) ...
>
> %SYSMAN-I-OUTPUT, command execution on node NODEN2
> %SYSMAN-I-NODERR, error returned from node NODEN2
> -LIB-F-INSEF, insufficient event flags
>
> What's the cause?
Too few event flags, obviously. Use of event flags often being a more
general problem for application development, too.
> What's the cure?
Fix the SYSMAN code (probably not feasible for most folks reading this
newsgroup), or restart the SMI server to paper over the bug.
As for the background...
Tossed the query /SYSMAN LIB-F-INSEF, insufficient event flags/ at the
Bing search engine and that kicked out the following quote: "There is a
known bug ("known limitation") in SYSMAN, still present in 8.4: if one
uses it a lot, one can get the "insufficient event flags" error.
Workaround is to kill the SMI processes, de-assign some logical names
and restart the SMI server." That'll probably show up in a Google
Groups search, as well.
Tried a slightly tailored search /openvms sysman insufficient event
flags/ via the Google search engine and that kicked out the following
HP forums discussion:
<http://h30499.www3.hp.com/t5/System-Management/OpenVMS-v7-3-1-Cluster-SYSMAN-insufficient-event-flags/td-p/5025334>
General recommendation beyond applying patches and related is to
STOP/ID the SMISERVER process on the node that's reported back the
cited INSEF error and then issue the following DCL command on that same
node to restart the SYSMAN daemon: @SYS$SYSTEM:STARTUP SMISERVER
--
Pure Personal Opinion | HoffmanLabs LLC
More information about the Info-vax
mailing list