Chapter 88 SFG (Safeguard) Messages

The messages in this chapter are sent by the Safeguard (SFG) subsystem. The subsystem ID displayed by these messages includes SFG as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

process-name: NonStop Kernel/Safeguard versions (K-version/SFG-version) are incompatible

`process-name`	is the name of a Safeguard process.
`K-version`	is the version of the HP NonStop Kernel operating system.
`SFG-version`	is the version of the Safeguard subsystem.

Cause The NonStop Kernel and Safeguard versions do not match.

Effect The $ZSMP process abends. Because this error is detected before the backup process is started, no takeover occurs.

Recovery Ensure that compatible versions of the operating system and Safeguard exist. Use the VPROC program to determine the release level of the SAFECOM, OSMP, and OSMON processes, and compare them with the current operating system version.

process-name: created Safeguard file: filename

filename

is the name of a Safeguard file.

Cause The Safeguard file filename was created.

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name:Created Safeguard process:proc-start

proc-start

is either the process name of a Safeguard SMON (Security Monitor) or the process name of a Safeguard Event-Exit Process. An Event-Exit Process is a customized security process managed by the Safeguard subsystem.

Cause The Safeguard process proc-start was started normally.

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name:Stopped Safeguard process:proc-stop by user at terminal terminal

`proc-stop`	is either the process name of a Safeguard Security Monitor (SMON) or the name of a Safeguard Event-Exit Process.
`user`	is the name of a valid user on the system.
`terminal`	is a valid terminal name.

Cause The Safeguard process proc-stop was stopped normally by the user at the specified terminal.

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name: Safeguard configuration token token changed from prev-val to new-val by user at terminal terminal

`token`	is a Safeguard configuration attribute.
`prev-val`	is the previous value of the Safeguard configuration attribute.
`new-val`	is the new value of the Safeguard configuration attribute.
`user`	is the name of a valid user on the system.
`terminal`	is a valid terminal name.

Cause The token was altered by the user at the specified terminal.

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name: Audit file file1 has been closed; audits are now directed to file2.

`file1`	is the name of an audit file that was closed.
`file2`	is the name of an audit file that was opened.

Cause An audit file rollover has occurred. file1 was closed and file2 was opened.

Effect Audit records are now directed to file2. Depending on the security policy, file1 is available for backup, then released back into the audit pool.

Recovery Informational message only; no corrective action is needed.

process-name: Safeguard audit state change. Previous state: prev-state Current state: cur-state

`prev-state`	is the previous state of the Safeguard audit service.
`cur-state`	is the current state of the Safeguard audit service.

Cause The state of the Safeguard audit service changed from prev-state to cur‑state because of operator action, an audit-pool-full condition, or a system failure.

Effect None.

Recovery Depending on the security policy and the audit state change involved, select a new current-audit-pool subvolume or a new next-audit-pool subvolume.

process-name: The last audit file aud-file of audit pool subvol-name is now in use. Current state: cur-state Pending state: pend-state

`aud-file`	is the name of a Safeguard audit file.
`subvol-name`	is the name of the subvolume containing the audit pool.
`cur-state`	is the current state of the Safeguard audit service.
`pend-state`	is the pending state of the Safeguard audit service.

Cause An audit state change from cur-state to pend-state is imminent unless operator action is taken.

Effect None.

Recovery Depending on the security policy and the audit state change involved, do one of the following:

Select a new current-audit-pool subvolume or a new next-audit-pool subvolume.
Release an audit file to free space within the audit pool.
Increase the MAXFILES attribute of the pool in order to create additional files.

process-name: The last audit file aud-file of audit pool subvol-name is now pcnt percent filled. Current state: cur-state Pending state: pend-state

`aud-file`	is the name of a Safeguard audit file.
`subvol-name`	is the name of the subvolume containing the audit pool.
`pcnt`	is a value representing a percentage.
`cur-state`	is the current state of the Safeguard audit service.
`pend-state`	is the pending state of the Safeguard audit service.

Cause An audit state change from cur-state to pend-state is imminent.

Effect None.

Recovery Depending on the security policy and the audit state change involved, do one of the following:

Select a new current-audit-pool subvolume or a new next-audit-pool subvolume.
Release an audit file to free space within the audit pool.
Increase the MAXFILES attribute of the pool in order to create additional files.
NOTE: Inaction can result in the recycling of audit files, suspension of audit, or denial of access.

process-name: Safeguard audit file aud-file has been released for later reuse

aud-file

is the name of a Safeguard audit file.

Cause The Safeguard audit file aud-file was released (purged and reestablished).

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name: Safeguard audit file aud-file has been recycled for reuse

aud-file

is the name of a Safeguard audit file.

Cause The Safeguard audit file aud-file was recycled in order to satisfy an audit rollover.

Effect None.

Recovery No corrective action is needed if the security policy is to recycle audit files. Otherwise, do one of the following:

Select a new current-audit-pool subvolume or a new next-audit-pool subvolume.
Release an audit file to free space within the audit pool.
Increase the MAXFILES attribute of the pool in order to create additional files.

Safeguard OSMON was started with wrong name

Cause An attempt was made to start the Safeguard software with a RUN command that specifies the $SYSTEM.SYSnn.OSMON object file. The RUN command must specify the OSMP object file.

Effect The command is rejected.

Recovery Start the Safeguard software with a RUN command that specifies the $SYSTEM.SYSnn.OSMP object file.

process-name: Unusable Safeguard file:filename filerole

`filename`	is the name of the unusable Safeguard file.
`filerole`	indicates the purpose of the unusable Safeguard file.

Cause A Safeguard file is in error because of an unexpected attribute (file type or file code). This is a critical event.

Effect The Safeguard Manager Process (SMP) abends.

Recovery Rename or purge the unusable Safeguard file, then restart the Safeguard subsystem.

process-name: process SEEP-proc terminated abnormally

SEEP-proc

is the process name of the Safeguard Event Exit.

Cause The Safeguard Event-Exit Process SEEP-proc abends.

Effect The Safeguard Manager Process (SMP) attempts to restart the Event-Exit Process, as long as the ENABLED attribute in the Event-Exit Process configuration record is ON.

Recovery Contact the creator of the Event-Exit program to determine recovery action.

process-name: Event-Exit-Process SEEP-name configuration token token changed from old-val to new-val by user at terminal terminal

`SEEP-name`	is the name of the Safeguard Event-Exit configuration record.
`token`	is an Event-Exit configuration attribute.
`old-val`	is the previous value of the configuration attribute.
`new-val`	is the new value of the configuration attribute.
`user`	is the name of a valid user on the system.
`terminal`	is a valid terminal name.

Cause The token has been changed by the user at the specified terminal.

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name: Stopping process SEEP-proc not started by Safeguard

SEEP-proc

is the process name of the Safeguard Event Exit.

Cause The Safeguard Manager Process (SMP) detected a running process with the same process name as an enabled Safeguard Event Exit.

Effect The SMP attempts to kill the running process to guard against attempted security attacks.

Recovery If the running process is valid, change the process name for the Event Exit. Otherwise, investigate the running process to determine if it is part of a security attack.

process-name: Event-Exit-Process SEEP-name (SEEP-proc) message reply EE^HDR^ERROR errno

`SEEP-name`	is the name of the Safeguard Event-Exit configuration record.
`SEEP-proc`	is the process name of the Safeguard Event Exit.
`errno`	is the number of the file system error encountered by the Event-Exit Process.

Cause The Safeguard Event-Exit Process returned an error in the message header.

Effect The effect varies according to the design of the Event-Exit program.

Recovery Contact the creator of the Event-Exit program to determine recovery action.

process-name: Event-Exit-Process SEEP-name (SEEP-proc) message reply is invalid, reason:reason

SEEP-name

is the name of the Safeguard Event-Exit configuration record.

SEEP-proc

is the process name of the Safeguard Event Exit.

reason

is one of the following

reply too short

event type invalid

header status invalid

data offset out of bounds

challenge out of bounds

pswd rsp out of bounds

Cause The Safeguard Event-Exit Process returned an invalid message reply.

Effect The effect varies according to the design of the Event-Exit program.

Recovery Contact the creator of the Event-Exit program to determine recovery action.

process-name: Cannot determine audit file name from $ZSMP. No auditing will be done until after $ZSMP opens a new audit file. Deny Grants will be enforced if configured.

process-name

is the name of the Safeguard Monitor Process ($ZSxx, where xx is the processor number in which the monitor process resides).

Cause The monitor process is attempting to communicate with the Safeguard Management Process ($ZSMP) to determine the name of the next audit file to use. $ZSMP is not responding.

Effect The monitor process issues this message and continues processing requests. However, the monitor process will be unable to audit any access attempts on which it rules. In addition, if the audit service recovery action is DENY GRANTS, the monitor process rejects all access attempts.

Recovery The EMS event log or a previous operator message will contain an indication of the file-system error returned to the monitor process from $ZSMP before this event occurred. (See Appendix B, for descriptions of file‑system errors.) The most likely cause is a failure of the primary processor for $ZSMP, which results in an error 201. Another possible cause is an error 40 timeout.

If $ZSMP has been delayed in responding to the monitor process, it may return to normal without being restarted. Check the operator messages for a message from $ZSMP indicating that auditing has been directed to a new audit file. This message indicates a return to normal processing. As an additional check, execute a FUP LISTOPENS command for the new audit file, and verify that it has been opened by all monitor processes, specifically those that reported this event.

If $ZSMP is no longer running, the Safeguard subsystem must be restarted.

process-name: SAFEGUARD configured with CMON=ON but $CMON not running.

process-name

is the name of the Safeguard Manager Process ($ZSMP).

Cause The $ZSMP process attempted to communicate with the $CMON process because the Safeguard configuration setting instructed it to do so. But, a process named $CMON could not be found. Either the $CMON process has failed, or the Safeguard configuration setting for CMON has been set ON incorrectly.

Effect The Safeguard subsystem recovers from this communication failure according to its configuration setting for CMONERROR. $ZSMP issues this message only once until $CMON becomes available again.

Recovery Restart the $CMON process, or use the ALTER SAFEGUARD command to change the Safeguard configuration setting to CMON OFF.

process-name: Due to an error errno on SAFEGUARD file: filename (physical name: phys-name) no file access allowed on this virtual disk.

`process-name`	is the name of the Safeguard monitor process ($ZS`nn`, where `nn` is the CPU number.).
`errno`	is the number of the file system error returned during an attempt to access a Safeguard file.
`filename`	is the name of the Safeguard file in which the error occurred. This file is on a virtual disk.
`phys-name`	is the underlying physical name of the Safeguard file in error. The physical disk name is included in this name.

Cause A file system error was returned on an attempt to access a Safeguard system file on a virtual disk.

Effect All subsequent attempts to access the files on this virtual disk are denied.

Recovery Follow the recovery action given for the underlying file system error as shown for operator message -32755. (See “COM-KRNL (Common) Messages” in this manual for a description of this error.) The error may be on the physical disk indicated by phys-name in this message.

process-name: Lock found on SAFEGUARD file: filename Lock details: description

process-name

is the name of the Safeguard monitor process ($ZSnn, where nn is the CPU number.).

filename

is the name of the Safeguard file in which the error occurred.

description

is the detailed description of the lock found on the Safeguard file. Lock description would be in the following format:

File/Record,[Generic,] Granted/Waiting, [Intent,] by process system name.process name, program file program file name.

Cause A file system error FELOCKED was returned on an attempt to access a Safeguard system file on a virtual disk.

Effect Safeguard will retry for a maximum of three times to access information from the concerned file. If the lock still exists, security violation or similar message would be returned back to the application/user.

Recovery Analyze the EMS message generated and take steps to remove the concerned lock. If the lock is held by a system process and not by a user process, contact the Global Mission Critical Solution Center (GMCSC).

process-name: Pattern database cache error from SEGMENT_ALLOCATE_ Returned Error = errno, Error-detail = error-detail Extended Data Seg ID: id, Seg Addr: addr, Seg Size: size

`process-name`	is the name of the Safeguard monitor process ($ZS`nn`, where `nn` is the CPU number.).
`errno`	is the error returned.
`error-detail`	is the error detail.
`id`	is the extended data segment identification.
`addr`	is the segment address.
`size`	is the segment size.

Cause A file system error occurred while creating or accessing the flat segment.

Effect All pattern matching requests will be handled using file system I/O rather than using the application cache.

Recovery Follow the recovery action given for the underlying file system error (SEGMENT_ALLOCATE_). Possible recovery may include increasing the amount of free space on the volume; using NSKCOM to specify swap space; or increasing swap space. Use the information provided in the EMS message from errno and error-detail, and compare that information with the SEGMENT_ALLOCATE_ of the Guardian Procedure Calls Reference Manual for guidance on proper recovery.

process-name: Pattern database cache error from POOL_DEFINE_ Returned Error = errno Extended Data Seg Id: id, Seg Addr: addr, Seg Size: size

`process-name`	is the name of the Safeguard monitor process ($ZS`nn`, where `nn` is the CPU number.).
`errno`	is the error returned.
`id`	is the extended data segment identification.
`addr`	is the segment address.
`size`	is the segment size.

Cause A file system error occurred while designating a memory pool with the POOL_DEFINE_ procedure in the flat segment.

Effect All pattern matching requests will be handled using file system I/O rather than using the application cache.

Recovery Follow the recovery action given for the underlying file system error (POOL_DEFINE_). This error is not likely to occur, as most errors are caused by programmatic problems, not system resource problems. Use the information provided in the EMS message from errno and compare that information with the POOL_DEFINE_ of the Guardian Procedure Calls Reference Manual for guidance on proper recovery.

process-name: Pattern database cache error from POOL_GETSPACE_ Returned errno Extended Data Seg Id: id, Seg Addr: addr, Seg Size: size Pool address: address

`process-name`	is the name of the Safeguard monitor process ($ZS`nn`, where `nn` is the CPU number.).
`errno`	is the error returned.
`id`	is the extended data segment identification.
`addr`	is the segment address.
`size`	is the segment size.
`address`	is the pool address.

Cause A file system error occurred while requesting space from the memory pool.

Effect All pattern matching requests will be handled using file system I/O rather than using the application cache.

Recovery Follow the recovery action given for the underlying file system error (POOL_GETSPACE_). This error is likely caused by corruption in the pool header, or the number of pool entries requested has exceeded the system limits. If the limit has been exceeded, notify the Global NonStop Solution Center (GNSC) this error occurred. Try to reduce the number of pattern-based protection records located on this CPU, either by reducing the number of pattern-based protection records or moving disk volumes to other CPUs. Use the information provided in the EMS message from errno and compare that information with the POOL_GETSPACE_ of the Guardian Procedure Calls Reference Manual for guidance on proper recovery.

Number of concurrent USER_AUTHENTICATE_ requests that can be serviced - Maximum Limit: number

number

The maximum number of concurrent USER_AUTHENTICATE_ requests that can be serviced.

Effect None.

Recovery Informational message only; no corrective action is needed.

Number of concurrent USER_AUTHENTICATE_ requests number exceeds the maximum limit.

number

The number of concurrent USER_AUTHENTICATE_ requests at the time the maximum limit was exceeded.

Cause The number of concurrent USER_AUTHENTICATE_ requests exceeded the maximum limit.

Effect None.

Recovery When the maximum number of concurrent USER_AUTHENTICATE_ requests is reached, wait for two minutes before issuing the next USER_AUTHENTICATE_ request.

Number of concurrent USER_AUTHENTICATE_ requests number exceeds percentage number % maximum limit.

`number`	The number of concurrent USER_AUTHENTICATE_ requests at the time the `percentage number` was exceeded.
`percentage number`	The percentage of the maximum limit for USER_AUTHENTICATE_ requests.

Cause The number of concurrent USER_AUTHENTICATE_ requests exceeds 80%, 90%, or 95% of the maximum limit.

Effect None.

Recovery Informational message only; no corrective action is needed.

Number of concurrent USER_AUTHENTICATE_ requests number now below threshold percentage number % of maximum limit.

`number`	The current number of concurrent USER_AUTHENTICATE_ requests.
`threshold percentage number`	The threshold percentage of the maximum limit for USER_AUTHENTICATE_ requests.

Cause The number of concurrent USER_AUTHENTICATE_ requests is below the threshold of 80% of the maximum limit for concurrent USER_AUTHENTICATE_ requests.

Effect None.

Recovery Informational message only; no corrective action is needed.

Insufficient Memory in System Global Region, Bytes Requested: number required, Bytes Allocated: number allocated.

`number required`	is the number of bytes of system global memory required by Safeguard processes.
`number allocated`	is the number of bytes of system global memory allocated to Safeguard processes.

Cause Insufficient memory available in the system global region.

Effect None

Recovery Informational message only; no corrective action is needed.

process-name: Safeguard configuration token tkn changed from value1 TO value2 by user at terminal terminal-name.

`process-name`	is the Safeguard Manager Process name ($ZSMP).
`tkn`	is the token that is altered.
`value1`	is the initial value before the token is altered.
`value2`	is the new value after the token is altered.
`user`	is the user who makes the configuration change.
`terminal-name`	is the name of the home terminal of the user who makes the configuration change.

Cause A Safeguard configuration attribute is altered.

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name: Safeguard OSHP was started with wrong name.

process-name

is the name of the OSHP process that has the incorrect name.

Cause The Safeguard helper process is started with a process name other than $ZSTnn (where, nn is the CPU number).

Effect The Safeguard helper process does not start.

Recovery Use the correct process name.

process-name SAFEGUARD Error while updating process attributes of user ZSFG-EVT-BAD-PSB.

`process-name`	is the Safeguard helper process name ($ZSTnn).
`user`	is the <user/alias name> whose process attributes have been altered.

Cause Error occurs while updating the process attributes of <user/alias name>.

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name SAFEGUARD successfully updated process attributes of user ZSFG-EVT-PSB-UPDATE-COMPLETE.

`process-name`	is the Safeguard helper process name ($ZSTnn).
`user`	is the <user/alias name> whose process attributes have been altered.

Cause The process attributes of <user/alias name> is successfully altered.

Effect None.

Recovery Informational message only; no corrective action is needed.

process-name CHECK-SQLMX-OWNERSHIP requires SQL/MX R3.3 or later; current version is incompatible.

process-name

is the Safeguard Manager Process name ($ZSMP).

Cause Version of SQL/MX installed on the system is lesser than 3.3.

Effect CHECK-SQLMX-OWNERSHIP option cannot be used with DELETE USER command.

Recovery Install SQL/MX version 3.3 or later.

process-name SQLMX_ANSINAME_MAP_INIT_ error. Error : errno ErrorDetail : error-detail.

process-name

is the Safeguard Manager Process name ($ZSMP).

Cause Error in starting ANSI names server process.

Effect User cannot be deleted when CHECK-SQLMX-OWNERSHIP option is specified in DELETE USER command.

Recovery Correct the specific cause of errno and error-detail.