Operator Messages Manual
Chapter 75 OSS (Open System Services) Messages
The messages in this chapter are issued by processes running
under the Open System Services (OSS) subsystem ID. Such processes
include: The OSS EasySetup utilities, to report processing
status using message 10 An OSS service processor (OSP) server The OSS sockets local server (in systems running AF_UNIX
Release 1 software) The OSS sockets local server 2 (in systems running
AF_UNIX Release 2 software) The OSS terminal helper server Processes running in the OSS environment; in particular,
messages 5 through 12 are used by: Network services servers such as the inetd process
(see message 8) The OSS shell when the logger command is used Applications running in the OSS environment that call
the syslog() function Messages numbered 5 through 12 have
numbers that are assigned by severity level. This chapter documents
the severity level for each message and the basic message format,
but it documents actual message text only for HP programs that use
this feature; site-written OSS applications can also use the syslog()
function.
| | | |  | 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. | | | | |
| -3 object, STATE changed
from old to new reason | | object | is one of the following: | fileset | is the name of a fileset, represented as a subdevice
of the OSS Monitor process $ZPMON. | | process | is the name of the FSCK utility process, represented
as a subdevice of the OSS Monitor process $ZPMON. | | server | is the name of an OSS server process, represented
as a subdevice of the OSS Monitor process $ZPMON. |
| | old | is the previous state of the object. This state depends
on the object. For a fileset, this state is one of the
following: For the FSCK utility or an OSS server, this state is one of
the following: | | new | is the current state of the object. This state depends
on the object. For a fileset, this state is one of the
following: For the FSCK utility or an OSS server, this state is one of
the following: | | reason | explains the cause of the change in state of the object.
This cause is one of the following: |
Cause The OSS Monitor subsystem processed a Subsystem Control Facility
(SCF) command or other event. The object state changed during that
processing. Effect The new state determines the operations that can be performed
on the object. Recovery Informational message only; no corrective action is needed unless
an SCF error message has also been sent to the console. |
| -1 server-name cpu changed
from oo to nn [ cause ] | | server-name | is the process name of the OSS sockets local server
process or OSS name server process reporting this message. | | oo | is the processor number of the old processor. | | nn | is the processor number of the new processor. | | cause | is a description of the reason for the processor change;
this is usually takeover. |
Cause The indicated OSS server process switched processors in response
to a hardware or software failure. Effect The OSS server process now runs on what was previously its backup
processor. Recovery Informational message only; no corrective action is needed. |
| 1 server-name INTERNAL
ERROR - %cs-id.pppppp [ - SAVE - file ] | | server-name | is the process name of the OSS sockets local server
process or OSS name server process in which the internal error occurred. | | cs-id | is the code space ID of the code space where the OSS
server process was executing at the time it detected the error. | | pppppp | is the setting that the P register had when the inconsistency
was detected. | | file | is the Guardian file identifier of the saveabend file,
if any is created. |
Cause The indicated OSS server process detected an internal inconsistency. Effect The OSS server process terminates. For the OSS name server, if the SAVEABEND option is in effect,
a saveabend file is generated in the subvolume where the OSS name
server program file resides. For the OSS sockets local server process, the saveabend file
is generated in the subvolume where the OSS sockets local server program
file resides. Recovery Contact your service provider and provide all relevant information
as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 2 server-name Catalog
I/O Error error-number on filename | | server-name | is the process name of the OSS name server process
in which the error occurred. | | error-number | is the error number of the Guardian file-system error
returned on the fileset catalog operation. | | filename | is the name of the fileset catalog file in which the
error occurred. |
Cause An I/O error occurred on a fileset catalog. The reporting OSS
name server process cannot access at least a portion of one of the
catalog files (PXINODE, PXLINK, or PXLOG) for a fileset, or logic
errors have occurred in the OSS name server process. Effect If the catalog I/O operation was being performed to respond
to an OSS file-system or OSS Monitor request, the OSS name server
process replies to the request with the corresponding error or with
Guardian file-system error 4005. Recovery For a definition of the specified error, see Appendix B. For more detailed
information including recovery actions, see the Guardian
Procedure Errors and Messages Manual for specific information
on the Guardian file-system error. Stop (unmount) the corresponding fileset and repair the fileset
catalog by using the Subsystem Control Facility (SCF) DIAGNOSE FILESET,
REPAIR ALL command on the fileset. If the file-system error number
indicates that a disk-related hardware problem (such as error 120)
has occurred, contact your service provider and provide all relevant
information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 3 server-name Catalog
Error error on Catalog catalog-subvol | | server-name | is the process name of the OSS name server process
reporting the error. | | error | is the fileset catalog error number. Possible values
of error are as follows: | | catalog-subvol | is the name of the subvolume containing the fileset
catalog. |
Cause A logical inconsistency has been detected within a fileset catalog. Effect While accessing fileset catalogs, the reporting OSS name server
process performed consistency checks and one of these checks failed.
The OSS name server process received Guardian file-system error 4201. Recovery Perform the following steps: Stop (unmount) the fileset using the Subsystem Control
Facility (SCF) STOP FILESET command. Repair the fileset catalogs using the SCF DIAGNOSE FILESET,
REPAIR ALL command on the indicated fileset. Start (mount) the fileset again with the SCF START FILESET
command.
|
| 4 server-name SIGNAL signal stack-trace | | server-name | is the process name of the OSS name server process
receiving the signal. | | signal | is the signal number. | | stack-trace | is a stack trace that includes the location where
the inconsistency was detected. |
Cause An internal inconsistency interrupted execution of the indicated
OSS name server process. Effect After generating this error, the OSS name server process (either
the primary or backup process) terminates. If the SAVEABEND option
is in effect, a saveabend file is generated in the same subvolume
where the OSS name server object file resides. Recovery Recovery action depends on the signal number indicated in the
event message, as shown in this table. |
| 5 facility EMERGENCY [,PID = pid] (identity) : text | | facility | is the name of the OSS environment facility associated
with this text message by the OSS application program. The following
names are supported: | | pid | is the OSS process ID for the process reporting the
error. The OSS application program can suppress display of this number. | | identity | is an identifier provided by the issuing program to
indicate the source of the message. Typically this is the filename
of the program file or the effective user ID for the process that
issued the message. If the program provides no identifier, syslog
appears. | | text | is the message text supplied by the OSS application
program. |
Cause A site-written OSS application has sent an OSS operator message.
The cause of the message is application-specific. This message identifies
a severe condition requiring immediate attention. Effect The effect depends on the application. Recovery Contact your application support representative for recovery
information. |
| 6 facility ALERT [,PID = pid] (identity) : text | | facility | is the name of the OSS environment facility associated
with this text message by the OSS application program. The following
names are supported: | | pid | is the OSS process ID for the process reporting the
error. The OSS application program can suppress display of this number. | | identity | is an identifier provided by the issuing program to
indicate the source of the message. Typically this is the filename
of the program file or the effective user ID for the process that
issued the message. If the program provides no identifier, syslog
appears. | | text | is the message text supplied by the OSS application
program. |
Cause A site-written OSS application has sent an OSS operator message.
The cause of the message is application-specific. This message identifies
a condition that should be corrected immediately, such as a corrupted
system database. Effect The effect depends on the application. Recovery Contact your application support representative for recovery
information. |
| 7 facility CRITICAL [,PID = pid] (identity) : text | | facility | is the name of the OSS environment facility associated
with this text message by the OSS application program. The following
names are supported: | | pid | is the OSS process ID for the process reporting the
error. The OSS application program can suppress display of this number. | | identity | is an identifier provided by the issuing program to
indicate the source of the message. Typically this is the filename
of the program file or the effective user ID for the process that
issued the message. If the program provides no identifier, syslog
appears. | | text | is the message text supplied by the OSS application
program. |
Cause A site-written OSS application has sent an OSS operator message.
The cause of the message is application-specific. This message identifies
a critical condition, such as a hard device error. Effect The effect depends on the application. Recovery Contact your application support representative for recovery
information. |
| 8 facility ERROR [,PID = pid] (identity) : text | | facility | is the name of the OSS environment facility associated
with this text message by the OSS application program. The following
names are supported: | | pid | is the OSS process ID for the process reporting the
error. The OSS application program can suppress display of this number. | | identity | is an identifier provided by the issuing program to
indicate the source of the message. Typically this is the filename
of the program file or the effective user ID for the process that
issued the message. If the program provides no identifier, syslog
appears. For the inetd program, this
identifier is inetd. | | text | is the message text supplied by the OSS application
program. The following messages are most commonly displayed by the inetd program: echo/tcp: bind: Address already in use Service: Can’t set uid ’number’ Service/Protocol: getpwnam ’user’, no
such user Service/Protocol: No such user ’user’,
service ignored Service/Protocol: server failing (looping), service
terminated
|
Cause One of the following occurred: A site-written OSS application has sent an OSS operator
message. The cause of the message is application-specific. This message
identifies an error condition. The OSS inetd program has encountered
a recoverable or ignorable error. The text messages listed previously
under text indicate the following: The port for a requested service is already in use
by another process; a Guardian process is probably providing the indicated
service. The OSS user ID (UID) or group ID number used by a program file entry in the /etc/inetd.conf file is invalid. No entry existed for the user name user in the node’s user access configuration file when the service
was invoked; the entry for the service in the /etc/inetd.conf file might be invalid. The number of requests for a service in the past minute
exceeded the limit allowed; the service is automatically reenabled
after 10 minutes. One of the following caused inetd to terminate the service: Too many hosts requested a service during the past
minute. A broken client application program is requesting
the service too often. A malicious user is running an application program
to invoke the service in a manner intended to deny access to the service
by other programs. The invoked service program has an error that causes
client application programs to retry the service quickly.
Effect The effect depends on the application. Recovery For: A site-written OSS application, contact your application
support representative for recovery information. The OSS inetd program, no recovery
action is necessary. The program adapts its behavior. If the problem
was caused by a configuration error, you can do the following: Edit the /etc/inetd.conf file to correct
the error. Use the OSS kill command to send a SIGHUP signal to the inetd program so that the program rereads its configuration
file.
|
| 9 facility WARNING [,PID = pid] (identity) : text | | facility | is the name of the OSS environment facility associated
with this text message by the OSS application program. The following
names are supported: | | pid | is the OSS process ID for the process reporting the
error. The OSS application program can suppress display of this number. | | identity | is an identifier provided by the issuing program to
indicate the source of the message. Typically this is the filename
of the program file or the effective user ID for the process that
issued the message. If the program provides no identifier, syslog
appears. | | text | is the message text supplied by the OSS application
program. |
Cause A site-written OSS application has sent an OSS operator message.
The cause of the message is application-specific. This message is
only a warning. Effect The effect depends on the application. Recovery Contact your application support representative for recovery
information. |
| 10 facility NOTICE [,PID = pid] (identity) : text | | facility | is the name of the OSS environment facility associated
with this text message by the sending program. The following names
are supported: | | pid | is the OSS process ID for the process reporting the
error. The sending program can suppress display of this number. | | identity | is an identifier provided by the issuing program to
indicate the source of the message. Typically this is the filename
of the program file or the effective user ID for the process that
issued the message. If the program provides no identifier, syslog
appears. | | text | is the message text supplied by the sending program.
For the OSS EasySetup utilities, this text is one of the status messages
documented in the Open System Services Installation Guide. |
Cause One of the following occurred: A site-written OSS application has sent an OSS operator
message. The cause of the message is application-specific. This message
identifies a condition that is not an error, but that should receive
special handling. One of the OSS EasySetup utilities has issued a status
message.
Effect The effect depends on the application. Recovery For: A site-written OSS application, contact your application
support representative for recovery information. The OSS EasySetup utilities, normally no recovery
is necessary. If the reported condition causes process termination
and is not a message described in the Open System Services
Management and Operations Guide, see the error messages
documented in the Open System Services Installation Guide.
|
| 11 facility INFORMATION [,PID = pid] (identity) : text | | facility | is the name of the OSS environment facility associated
with this text message by the OSS application program. The following
names are supported: | | pid | is the OSS process ID for the process reporting the
error. The OSS application program can suppress display of this number. | | identity | is an identifier provided by the issuing program to
indicate the source of the message. Typically this is the filename
of the program file or the effective user ID for the process that
issued the message. If the program provides no identifier, syslog
appears. | | text | is the message text supplied by the OSS application
program. |
Cause A site-written OSS application has sent an OSS operator message.
The cause of the message is application-specific. This message is
informational only. Effect The effect depends on the application. Recovery Contact your application support representative for recovery
information. |
| 12 facility DEBUGGING [,PID = pid] (identity) : text | | facility | is the name of the OSS environment facility associated
with this text message by the OSS application program. The following
names are supported: | | pid | is the OSS process ID for the process reporting the
error. The OSS application program can suppress display of this number. | | identity | is an identifier provided by the issuing program to
indicate the source of the message. Typically this is the filename
of the program file or the effective user ID for the process that
issued the message. If the program provides no identifier, syslog
appears. | | text | is the message text supplied by the OSS application
program. |
Cause A site-written OSS application has sent an OSS operator message.
The cause of the message is application-specific. This message contains
information normally used only when debugging a program. Effect The effect depends on the application. Recovery Contact your application support representative for recovery
information. |
| 13 server-name SQL Catalog
Manager Error err on File filename | | server-name | is the process name of the OSS name server process
reporting the error. | | err | is the text description of the error. | | filename | is the Guardian filename of the OSS file affected
by the error. |
Cause The indicated OSS name server process could not purge an OSS
file using the SQL catalog manager. Effect The OSS file is not purged. Recovery Perform the following steps: Enter a File Utility Program (FUP) INFO DETAIL command
for the file named in the message. If no OSS pathname is shown, use the Subsystem Control
Facility (SCF) DIAGNOSE FILESET command on all filesets used for SQL.
When this command is run, an entry is created in the fileset’s /lost+found directory for any file that has no links
to it. Remove or rename the OSS file in the /lost+found directory as needed.
For more information on OSS filesets and the use of inode numbers
for Guardian filenames and in the /lost+found directory, see the Open System Services Management and
Operations Guide. |
| 14 server-name SQL Catalog
Manager Process Creation Failure error:detail | | server-name | is the process name of the OSS name server process
reporting the error. | | error | is the error returned by the Guardian PROCESS_CREATE_
procedure call. | | detail | is the error detail returned by the PROCESS_CREATE_
procedure call. |
Cause An SQL catalog manager process could not be created because
there is a resource shortage in the primary processor. Effect The process is not created. Recovery Correct the resource problem by stopping unneeded processes
in the OSS name server’s primary processor. For a definition
of the specified error, see Appendix D. For more detailed information, including
recovery actions, see the Guardian Procedure Errors and
Messages Manual. |
| 15 server-name Backup
Process Created in CPU nn | | server-name | is the process name of the OSS sockets local server
process or OSS name server process reporting the event. | | nn | is the processor number of the processor where the
OSS server backup process is running. |
Cause The indicated OSS server process successfully created its backup
process. Effect The OSS server is now running as a process pair. Recovery Informational message only; no corrective action is needed. |
| 16 server-name Unable
to Create Backup CPU cpu, PROCESS_CREATE_Error error:detail | | server-name | is the process name of the OSS sockets local server
process or OSS name server process reporting the error. | | cpu | identifies the processor in which the OSS server backup
process was to be created. | | error | is the error returned by the Guardian PROCESS_CREATE_
procedure call. If is zero, the PROCESS_CREATE_ procedure call was
successful but a subsequent attempt to send the startup sequence to
the backup process resulted in the error shown in detail. | | detail | is the error detail returned by the PROCESS_CREATE_
procedure call. |
Cause The indicated OSS server cannot create a backup server process. Effect The OSS server process has no backup process. Recovery For a definition of the specified error, see Appendix D. For more detailed
information, including recovery actions, see the Guardian
Procedure Errors and Messages Manual. If the PROCESS_CREATE_ error being reported indicates a resource
shortage in the backup processor for the OSS server, correct this
shortage by doing one of the following: Stop unneeded processes in the processor. If the server is the OSS name server, use the SCF
ALTER SERVER command to change specify a different backup processor
and use the SCF CONTROL SERVER with the SYNC option to update the
values in the ZOSSSERV file. These steps are described in the procedure
for reconfiguring an OSS name server in the Open System
Services Management and Operations Guide.
If the PROCESS_CREATE_ error indicates that the backup processor
is down, reload the processor. |
| 17 server-name Unable
to Resize Extended Segment Error error,
FILE ext-swap-file | | server-name | is the process name of the OSS sockets local server
reporting the error. | | error | is the error returned by the Guardian RESIZESEGMENT
procedure. | | ext-swap-file | is the name of the extended swap file for the OSS
sockets local server. |
Cause The OSS sockets local server could not resize its extended segment
during initialization. Either the processor where the process was
running could not accommodate the larger segment or the disk volume
on which the OSS sockets local server’s extended swap file was
allocated did not contain enough free space to extend the file. Effect The OSS sockets local server process terminates abnormally. Recovery If error 43 is reported, make more space available on the volume
or designate a new volume. The volume used for the extended swap file
is determined by the setting of the SWAP attribute of the =_DEFAULTS
DEFINE when the OSS Monitor ($ZPMON) is started. Positive error numbers other than 43 might indicate a more serious
error with the disk volume containing the extended swap file for the
OSS sockets local server. See the Event Management Service (EMS) log
for disk operation messages that occurred before this message and
follow the recovery procedures listed. If a negative number is reported, the processor in which the
process was running cannot accommodate the larger extended segment.
Stop unneeded processes in the processor or move the OSS sockets local
server to another processor. |
| 19 server-name Unable
to Communicate with Local Server ls-name | | server-name | is the server name of the OSS name server reporting
the error. | | ls-name | is the server name of the failed OSS sockets local
server or local server 2 (LS2) server. |
Cause The OSS name server server-name cannot
communicate with the OSS sockets local server ls-name. Either the processor where the OSS sockets local server process
is running is no longer available or the OSS sockets local server
has stopped. Effect That OSS name server treats all AF_UNIX sockets associated with
that OSS sockets local server as closed. Recovery Reload the processor, if necessary. Use the Subsystem Control
Facility (SCF) START SERVER command to start a new OSS sockets local
server. |
20process-name Mount Point Name Propagation Error
Fileset fileset-number
Mount Point mount-point
Name Server name-server
File Management Error error |
| | process-name | is the process name of the OSS name server that generated
the event. | | fileset-number | is the fileset number of the fileset whose mount-point
pathname is being propagated. | | mount-point | is the fileset’s mount point. | | name-server | is the process name of the OSS name server that manages
the fileset. | | error | is the file-management error number of the last attempt
to propagate the mount-point pathname. |
Cause A fileset is managed by an OSS name server process different
from the OSS name server process that manages the fileset’s
mount point, and the process that manages the mount point cannot propagate
the fileset’s mount-point pathname to the process that manages
the fileset. Effect Audit records for files in that fileset or in filesets mounted
on that fileset contain potentially incorrect pathnames. Recovery Stop, then restart that fileset and any filesets mounted on
directories in that fileset. |
| 21 object Server has
reached its persistence count, automatic startup of the server is
disabled | | object | indicates the server process affected by the limit,
represented as a subdevice of the OSS Monitor process. |
Cause The server’s current persistence count has reached its
configured persistence count. The server has been restarted by the
automatic startup service the configured number of times within a
10-minute period. Effect The server is not automatically restarted until its current
persistence count is reset to 0. Recovery Do either of the following, which causes the current persistence
count to be reset to 0: If the server is an OSS name server, issue a Subsystem
Control Facility (SCF) START FILESET command for a fileset managed
by that server. If the server is an OSS message-queue server or an
OSS sockets local server, issue an SCF START SERVER or ALTER SERVER
command for it.
|
| 22 fileset Configured
FSCK outfile, filename, unavailable, falling
back to diskfile filename2 | | fileset | identifies a fileset that is being diagnosed. | | filename | is the filename currently configured as the value
of the REPORT attribute for the fileset. | | filename2 | indicates the alternative file that FSCK will write
its report output to. |
Cause The configured report file is not available. This usually means
that a print spooler is unavailable. Effect FSCK continues its diagnosis, using the output file identified
by filename2. Recovery No recovery is needed. This is an informational message. To prevent recurrence of the message the next time the fileset
is diagnosed, either make the spooler available or change the fileset
configuration to use a different file. |
| 23 Safeguard Manager Process process_name unavailable. Monitor is continuing. | | process_name | indicates the server process, normally $ZSMP. |
Cause The OSS environment requires that the security manager process
be running because it provides certain security features. The OSS
Monitor checks for the availability of the security manager process
when starting and issues this warning message when that process is
not found. Effect Security features such as user aliases, file sharing groups,
initial OSS program, and initial directory might not be available. Recovery No recovery is required. The OSS environment can function without
the missing features. To provide the missing features, start the security manager
process using the Safeguard SAFECOM program or using one of the methods
described in the Open System Services Management and Operations
Guide. |
| 24 Monitor unable to create temporary file on volume_name, error error_number | | volume_name | identifies the disk volume where the file cannot be
created. | | error_number | indicates the Guardian error number returned by the
underlying FILE_CREATE_ procedure call. For more information about
this error, see the Guardian Procedure Errors and Messages
Manual. |
Cause The OSS Monitor cannot create a necessary temporary file. Effect The OSS Monitor terminates. Recovery Determine why the error is occurring, correct the problem, and
restart the OSS Monitor. |
| 25 OSS Monitor FUP reload for alternate key file filename failed. | | filename | is the alternate key file name (ZOSSFS00 or ZOSSFS01). |
Cause The OSS Monitor could not reload its fileset configuration file,
indicated by filename, from the $SYSTEM.ZOSSMON
subvolume. Effect You might not be able to start some filesets. Server startup
is not affected. Recovery Use the File Utility Program (FUP) to reload the alternate key
files. If that fails, restore backup copies of ZOSSFSET, ZOSSFS00,
and ZOSSFS01. |
| 26 objecttype objectname attribute attribute value altered from oldval to newval [ cause ] | | objecttype | indicates an OSS name server process or an OSS fileset. | | objectname | is either the name of the fileset or the name of the
OSS name server process that is the subject of the message. The object
name is represented as a subdevice of the OSS Monitor process $ZPMON. | | attribute | is the affected attribute of the object. This attribute
depends on the object type. For a fileset, this attribute is one of
the following: | AUDITENABLED | | BUFFERED | | FTIOMODE | | MAXDIRTYINODETIME | | MAXINODES | | NFSPERMMAP | | NFSPOOL | | NFSTIMEOUT | | NORMALIOMODE | | READONLY | | RESTRICTEDACCESS | | SEEPPROTECTED |
For an OSS name server, this attribute is one of the following: | BACKUPCPU | | CPU | | INODECACHE | | LINKCACHE | | SEEPCPU | | SEEPENABLED | | SEEPPARAMTEXT | | SEEPPRI | | SEEPPROCESSNAME | | SEEPPROGFILENAME | | SEEPRESPONSETIMEOUT | | SEEPSWAPVOL | | SQLTIMEOUT |
| | oldval | is the attribute value of the object before alteration.
This attribute value depends on the object type. For an OSS fileset,
this attribute value is: For an OSS name server, this attribute value is: | | newval | is the attribute value of the object after alteration.
This attribute value depends on the object type. The possible values
are the same as described for oldval. | | cause | is a description of the reason for the change. This
reason is either system if the OSS name server changed the attribute
value or the user ID of the operator if the attribute value changed
because of an SCF command entry. |
Cause The OSS name server process changed the object attribute value,
either because of operational needs or in response to an SCF CONTROL
FILESET or CONTROL SERVER command issued by an operator. Effect Subsequent OSS name server process operations on the object
use the altered attribute value. Recovery Informational message only; no corrective action is needed. |
| 27 Fileset fileset pool
name changed from oldpoolname to newpoolname pool volume list changed from oldvollist to newvollist by cause | | fileset | is the name of the fileset that is the subject of
the message. The fileset name is represented as a subdevice of the
OSS Monitor process $ZPMON. | | oldpoolname | is the fileset pool Guardian filename before alteration. | | newpoolname | is the fileset pool Guardian filename after alteration. | | oldvollist | is a list of space-separated Guardian disk volume
names; each volume name starts with a $. Each listed disk volume was
eligible for OSS file creation on the fileset before alteration. | | newvollist | is a list of space-separated Guardian disk volume
names; each volume name starts with a $. Each listed disk volume is
eligible for OSS file creation on the fileset after alteration. | | cause | is a description of the reason for the change. This
reason is either system if the OSS name server changed the attribute
value or the user ID of the operator if the attribute value changed
because of an SCF command entry. |
Cause The OSS name server process changed the pool volume list, either
because of operational needs or in response to an SCF CONTROL FILESET
command issued by an operator. Effect Subsequent OSS name server process file creation operations
use the altered pool volume list. Recovery Informational message only; no corrective action is needed. |
| 28 objecttype objectname internal error - attribute attribute value
is val | | objecttype | indicates an OSS name server process or an OSS fileset. | | objectname | is either the name of the fileset or the name of the
OSS name server process that is the subject of the message. The object
name is represented as a subdevice of the OSS Monitor process $ZPMON. | | attribute | is the affected attribute of the object. This attribute
depends on the object type. For a fileset, this attribute is one of
the following: | AUDITENABLED | | BUFFERED | | FTIOMODE | | MAXDIRTYINODETIME | | MAXINODES | | NFSPERMMAP | | NFSPOOL | | NFSTIMEOUT | | NORMALIOMODE | | READONLY | | RESTRICTEDACCESS |
For an OSS name server, this attribute is one of the following: | BACKUPCPU | | CPU | | INODECACHE | | LINKCACHE | | SQLTIMEOUT |
| | val | is an invalid attribute value of the object. A valid
attribute value depends on the object type. For an OSS fileset, valid
attribute values are: For an OSS name server, valid attribute values are: |
Cause This version of the SCF product is not compatible with this
version of the OSS monitor. Effect You cannot change the values of attributes for OSS filesets
or OSS name servers. Recovery Contact your support representative to file a case and provide
the following information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
| 29 Fileset fileset pool
volume list containing numVols volumes
is invalid (vollist) | | fileset | is the name of the fileset that is the subject of
the message. The fileset name is represented as a subdevice of the
OSS Monitor process $ZPMON. | | numVols | is the number of pool volumes. | | vollist | is a list of space-separated Guardian disk volume
names. |
Cause The OSS name server process did not recognize the specified
volume list in an SCF CONTROL FILESET command issued by an operator.
Effect The pool volume list is not changed. Recovery Re-enter the command with a corrected specification for the
pool volume list. |
| 31 processname estimated
FSCK operation operation run time on fileset fileset with ID fsid and
catalog catalog is runtime minutes | | processname | is the process name of the FSCK process diagnosing
the fileset. | | operation | is the operation to be performed on the fileset by
the FSCK process. The operation was specified when the OSS Monitor
process or the operator issued an SCF DIAGNOSE FILESET command. This
operation is one of the following: | DOWNGRADE | | PURGE | | REPAIR ALL | | REPAIR NONE | | REPAIR OPEN | | REPAIR SERIOUS | | UPGRADE |
| | fileset | is the name of the fileset that is the subject of
the message. The fileset name is represented as a subdevice of the
OSS Monitor process $ZPMON. | | fsid | is the device label of the fileset, assigned by the
OSS Monitor process. | | catalog | is the fileset catalog subvolume name of the fileset. | | runtime | is the expected total run time in minutes for the
requested operation. |
Cause An SCF DIAGNOSE FILESET command began running a copy of FSCK. Effect The fileset indicated by fileset is
unavailable for approximately the period of time specified by runtime. Recovery Informational message only; no corrective action is needed. |
| 32 processname estimated
remaining FSCK operation operation run
time on fileset fileset with ID fsid and catalog catalog is runtime minutes | | processname | is the process name of the FSCK process diagnosing
the fileset. | | operation | is the operation being performed on the fileset by
the FSCK process. The operation was specified when the OSS Monitor
process or the operator issued the SCF DIAGNOSE FILESET command that
began the current operation. This operation is one of the following: | DOWNGRADE | | PURGE | | REPAIR ALL | | REPAIR NONE | | REPAIR OPEN | | REPAIR SERIOUS | | UPGRADE |
| | fileset | is the name of the fileset that is the subject of
the message. The fileset name is represented as a subdevice of the
OSS Monitor process $ZPMON. | | fsid | is the device label of the fileset, assigned by the
OSS Monitor process. | | catalog | is the fileset catalog subvolume name of the fileset. | | runtime | is the expected remaining run time in minutes for
the requested operation. |
Cause An SCF DIAGNOSE FILESET command is still running a copy of FSCK.This
event message is generated only when the FSCK process estimated run
time is more than five minutes. Effect The fileset indicated by fileset remains
unavailable for approximately the period of time specified by runtime. Recovery Informational message only; no corrective action is needed. |
33processname FSCK operation operation on fileset fileset with
ID fsid and catalog catalog completed with
Total run time runtime
Minor minorincons
Serious seriousincons
Warning warnings
Errors errors
Status status
Old PXINODE file oldinodefile
Old PXLINK file oldlinkfile
Old PXLOG file oldlogfile
New PXINODE file newinodefile
New PXLINK file newlinkfile
New PXLOG file newlogfile |
| | processname | is the process name of the FSCK process that diagnosed
the fileset. | | operation | is the operation that was performed on the fileset
by the FSCK process. The operation was specified when the OSS Monitor
process or the operator issued the SCF DIAGNOSE FILESET command that
began the completed operation. This operation is one of the following: | DOWNGRADE | | PURGE | | REPAIR ALL | | REPAIR NONE | | REPAIR OPEN | | REPAIR SERIOUS | | UPGRADE |
| | fileset | is the name of the fileset that is the subject of
the message. The fileset name is represented as a subdevice of the
OSS Monitor process $ZPMON. | | fsid | is the device label of the fileset, assigned by the
OSS Monitor process. | | catalog | is the fileset catalog subvolume name of the fileset. | | runtime | is the total run time in minutes for the completed
operation. | | minorincons | is the number of minor inconsistencies encountered. | | seriousincons | is the number of serious inconsistencies encountered. | | warningincons | is the number of warning situations encountered. | | errors | is the number of error situations encountered. | | status | indicates whether new fileset catalog files were created
by FSCK: | No new catalog files created | | New catalog files created |
| | oldinodefile | is the name of the fileset PXINODE file before FSCK
completed. | | oldlinkfile | is the name of the fileset PXLINK file before FSCK
completed. | | oldlogfile | is the name of the fileset PXLOG file before FSCK
completed. | | newinodefile | is the name of the fileset PXINODE file after FSCK
completed. | | newlinkfile | is the name of the fileset PXLINK file after FSCK
completed. | | newlogfile | is the name of the fileset PXLOG file after FSCK completed. |
Cause FSCK finished diagnosing the indicated fileset. Effect The fileset is available to start (mount) and use. Recovery Informational message only; no corrective action is needed. |
| 36 Fileset fileset has numAssocVols associated volumes | | fileset | is the name of the fileset that is the subject of
the message, represented as a subdevice of the OSS Monitor process. | | numAssocVols | is the number of disk volumes associated with the
fileset. |
Cause The fileset has more than 200 associated volumes. Effect This is a warning message. If the number of associated volumes
for the fileset reaches 256, then some of the pool volumes specified
in a Subsystem Control Facility (SCF) START FILESET or CONTROL FILESET
command with the SYNC option for the fileset might not be elligible
for file creation within the fileset. Recovery Informational message only; no corrective action is needed if
the number of associated volumes is close to 200. If the number of associated volumes is 256, then: Delete files from this fileset until a few associated
volumes no longer contain files belonging to this fileset. Issue the SCF CONTROL FILESET command with the SYNC option
to synchronize the pool volumes for the fileset.
|
| 37 Communication error with terminal process objectname file system error errno | | objectname | is the process name of the terminal process that was
the target of the communication. | | errno | is the Guardian file-system error returned by the
underlying Guardian procedure call that encountered the communication
problem. See the Guardian Procedure Errors and Messages
Manual for more information about errno, or use the HP Tandem Advanced Control Language (TACL) ERROR command
for an online explanation. |
Cause The OSS terminal helper server detected an error when communicating
with the terminal process identified as objectname. If the error reported by errno is retryable,
the most likely cause is either a system resource shortage on the
processor used by either the terminal helper process or the terminal
process. Effect Applications that perform OSS file system input or output with
terminals might not function properly. If the error reported by errno is
retryable, the communication is retried indefinitely or until a nonretryable
error is detected, with increasing delays of up to 60 seconds between
attempts. The message is logged once per hour during periods when
an input or output operation is being retried. Recovery If the error reported by errno is
retryable, stop other applications on the processors running the terminal
process and the OSS terminal helper server to free resources. If the
situation does not improve, then the processors running the terminal
process and the OSS terminal helper server should be reloaded. |
| 38 SIGNALTIMEOUT failed due to non-availability
of TLEs error‑text in cpu cpunum,error errornum | | error‑text | is the text containing the details of the error and
of the effect. | | cpunum | is the number of the processor for which all the time-list
elements (TLEs) are in use. | | errornum | is the Guardian file-system error number. |
Cause The OSS name server could not allocate a TLE from processor cpunum. All the TLEs for processor cpunum are in use. Effect The effect depends on what the OSS name server process was doing
when the TLE could not be allocated. In some cases, the OSS name
server process abends. See error-text. Recovery If the OSS name server process abended, restart the filesets
that are managed by the OSS name server. Try to identify the reason for TLE exhaustion in the processor
and change the process or application to eliminate the problem. For
example, look for processes and applications that call SIGNALTIMEOUT
for many different timers in use simultaneously. If a process is
found to be wrongly consuming the TLEs and it is an HP NonStop product,
contact your service provider and provide the following information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products. |
39
Allocation error for resource-type resource.
[ Resource ID: resource-id ]
Resource limit: resource-limit
Current percentage: current-percentage
Current usage: current-usage
Peak percentage: peak-percentage
Peak usage: peak-usage
Peak time: peak-time
Reset time: reset-time
OSS PID: OSS-pid
Program file: process-program-file
Attempted Allocation Amount: allocation-amount |
| | resource-type | is the type of resource. | | resource-id | is the name of the FILESET. For the resource of type
FILESET INODES only. | | resource-limit | is the limit of the resource. For resources of type
HEAP2, this is the pool size in bytes. For resources of type THREADS,
it is the maximum number of threads allowed. For resources of type
FLEXPOOL, this field is not used. For buffer resources, it is the
maximum amount of memory that can used. For open resources, it is
the maximum number of table entries allowed by OSS file system. | | current-percentage | is the current usage represented as a percentage of
the resource limit (rounded down to the nearest integer). The current
percentage can exceed 100% for (1) unbounded open resources and (2)
resources for which the limits have been reduced. | | current-usage | is the current usage of the resource. For buffer
resources, the current usage is the amount of memory used by the resource.
For open resources, the current usage is the number of table entries
being used by the resource. | | peak-percentage | is the peak usage represented as a percentage of the
resource limit. The peak percentage can exceed 100% for (1) unbounded
open resources and (2) resources for which the limits have been reduced. | | peak-usage | is the peak usage of the resource since the reset-time occurred. | | peak-time | is the time, displayed in the format ddmmmyy
hh:mm, at which the peak (highest) usage of resource type resource-type occurred. | | reset-time | The time, displayed in the format ddmmmyy
hh:mm, at which the peak usage of resource type resource-type was reset. The default value for reset-time is the time at which the resource was initialized. | | OSS-pid | is the process identifier for the
OSS process that issued this event. If the reporting process is a
Guardian process, then the null process ID may be reported (the null
OSS process ID is obtained by calling the OSS_PID_NULL_ procedure). | | process-program-file | is the Guardian program file name, represented as
$volume.subvol.filename of the Guardian or OSS program
used by the process that generated this event. | | allocation-amount | is the amount of resource the process attempted to
allocate. |
Cause An allocation error occurred for resource type resource-type. Effect The requested operation fails. After this event is generated,
subsequent allocation errors for the same type of resource do not
generate events for a period of two minutes. For example, for the PXS BUF resource, OSS applications fail
with the error [ENOMEM]. For example, if this message is sent from an OSP process ($ZSPnn), applications that make use of thread-aware I/O
operations for regular files might experience reduced performance. Recovery Reduce the usage of the specified resource type and retry the
operation. For example, if this is a resouce of type PXS BUF, reduce
the number of OSS opens for the processor. For example, if this message
is sent from an OSP process ($ZSPnn), move
applications that are using thread-aware regular file I/O to other
processors. |
40Limit error for resource-type resource.
[ Resource ID: resource-id ]
Resource limit: resource-limit
Current percentage: current-percentage
Current usage: current-usage
OSS PID: OSS-pid
Program file: process-program-file
Attempted Allocation Amount: allocation-amount |
| | resource-type | is the type of resource. | | resource-id | only for the resource of type FILESET INODES, this
is the name of the FILESET. | | resource-limit | is the limit of the resource. For resources of type
HEAP2, this is the pool size in bytes. For resources of type THREADS,
it is the maximum number of threads allowed. For resources of type
FLEXPOOL, this field is not used. For buffer resources, it is the
maximum amount of memory that can used. For open resources, it is
the maximum number of table entries allowed by OSS file system. | | current-percentage | is the current usage represented as a percentage of
the resource limit (rounded down to the nearest integer). The current
percentage can exceed 100% for (1) unbounded open resources and (2)
resources for which the limits have been reduced. | | current-usage | is the current usage of the resource. For buffer
resources, the current usage is the amount of memory used by the resource.
For open resources, the current usage is the number of table entries
being used by the resource. | | OSS-pid | is the process identifier for the
OSS process that issued this event. If the reporting process is a
Guardian process, then the null process ID may be reported (the null
OSS process ID is obtained by calling the OSS_PID_NULL_ procedure). | | process-program-file | is the Guardian program file name, represented as
$volume.subvol.filename of the Guardian or OSS program
used by the process that generated this event. | | allocation-amount | is the amount of resource the process attempted to
allocate. |
Cause A limit error occurred for resource type resource-type. A limit error occurs when the current usage for a resource is at
or so near the resource limit that an allocation cannot be attempted.
A resource allocation cannot be attempted when the resource’s
current usage plus the requested resource amount is greater than the
resource’s defined limit. Effect The requested operation fails. After this event is generated,
subsequent limit errors for the same type of resource do not generate
events for a period of two minutes. Recovery Reduce the usage of the specified resource type and retry the
operation. |
41Resource resource-type is approaching the resource limit.
[ Resource ID: resource-id ]
Resource limit: resource-limit
Warning threshold: warning-threshold
Safe threshold: safe-threshold
Current percentage: current-percentage
Current usage: current-usage
Peak percentage: peak-percentage
Peak usage: peak-usage
Peak time: peak-time
Reset time: reset-time
|
| | type | is the type of resource that is nearing the resource
limit. | | resource-id | only for the resource of type FILESET INODES, this
is the name of the FILESET. | | resource-limit | is the limit of the resource. For resources of type
HEAP2, this is the pool size in bytes. For resources of type THREADS,
it is the maximum number of threads allowed. For resources of type
FLEXPOOL, this field is not used. For buffer resources, it is the
maximum amount of memory that can used. For open resources, it is
the maximum number of table entries allowed by OSS file system. | | warning-threshold | is the warning threshold for the resource type, represented
as a percentage of the resource limit. | | safe-threshold | is the safe threshold for this resource type, represented
as a percentage of the resource limit. When the current-percentage falls below the safe-threshold after
exceeding the warning-threshold, this message
(which indicates that the status is normal for this resource) is sent. | | current-percentage | is the current usage represented as a percentage of
the resource limit (rounded down to the nearest integer). The current
percentage can exceed 100% for (1) unbounded open resources and (2)
resources for which the limits have been reduced. | | current-usage | is the current usage of the resource. For buffer
resources, the current usage is the amount of memory used by the resource.
For open resources, the current usage is the number of table entries
being used by the resource. | | peak-percentage | is the peak usage represented as a percentage of the
resource limit. The peak percentage can exceed 100% for (1) unbounded
open resources and (2) resources for which the limits have been reduced. | | peak-usage | is the peak usage of the resource since the reset-time occurred. | | peak-time | is the time, displayed in the format ddmmmyy
hh:mm, at which the peak (highest) usage of resource type resource-type occurred. | | reset-time | is the date and time when the peak-usage was reset. The default value for reset-time is the time at which the resource was initialized. |
Cause The current resource usage has exceeded the warning threshold
for resource resource-type and has not yet dropped
to or below the safe threshold for the resource. Effect This event is generated the first time after the reset time
that resource usage exceeds the warning threshold for the given type
of resource. In addition, this event is generated once per hour while
the resource usage exceeds the safe threshold. Recovery This is an informational message only; no corrective action
is needed. However, to avoid possible failures due to resource exhaustion
under increased work load, monitor resource usage and tune the application
and system as needed. For example, if this message is sent from an
OSP process ($ZSPnn), consider moving applications
that are using thread-aware regular file I/O to other processors. |
42Status returned to normal for resource-type resource.
[ Resource ID: resource-id ]
Resource limit: resource-limit
Warning threshold: warning-threshold
Safe threshold: safe-threshold
Current percentage: current-percentage
Current usage: current-usage
Peak percentage: peak-percentage
Peak usage: peak-usage
Peak time: peak-time
Reset time: reset-time |
| | resource-type | is the type of resource. | | resource-id | only for the resource of type FILESET INODES, this
is the name of the FILESET. | | resource-limit | is the limit of the resource. For resources of type
HEAP2, this is the pool size in bytes. For resources of type THREADS,
it is the maximum number of threads allowed. For resources of type
FLEXPOOL, this field is not used. For buffer resources, it is the
maximum amount of memory that can used. For open resources, it is
the maximum number of table entries allowed by OSS file system. | | warning-threshold | is the warning threshold for the resource type, represented
as a percentage of the resource limit. | | safe-threshold | is the safe threshold for this resource type, represented
as a percentage of the resource limit. When the current-percentage falls below the safe-threshold after
exceeding the warning-threshold, this message
(which indicates that the status is normal for this resource) is sent
and warning messages for this resource are discontinued. | | current-percentage | is the current usage represented as a percentage of
the resource limit (rounded down to the nearest integer). The current
percentage can exceed 100% for (1) unbounded open resources and (2)
resources for which the limits have been reduced. | | current-usage | is the current usage of the resource. For buffer
resources, the current usage is the amount of memory used by the resource.
For open resources, the current usage is the number of table entries
being used by the resource. | | peak-percentage | is the peak usage represented as a percentage of the
resource limit. The peak percentage can exceed 100% for (1) unbounded
open resources and (2) resources for which the limits have been reduced. | | peak-usage | is the peak usage of the resource since the reset-time occurred. | | peak-time | is the time, displayed in the format ddmmmyy
hh:mm, at which the peak (highest) usage of resource type resource-type occurred. | | reset-time | is the date and time when the peak-usage was reset. The default value for reset-time is the time at which the resource was initialized. |
Cause The current usage for resource-type resource has dropped to or below the safe threshold after it had
previously reached or exceeded the warning threshold. Effect Warning messages (message 41) for this resource type are discontinued. Recovery This is an informational message only; no corrective action
is needed. |
| 45 Fileset fileset RESTRICTEDACCESS
attribute value is set to current-value in the OSS Monitor configuration database. [Old value was old-value] | | fileset | is the name of the OSS fileset. | | current-value | is the value of the RESTRICTEDACCESS attribute after
the change was made. | | old-value | is the value of the RESTRICTEDACCESS attribute before
the change was made. |
Cause The value of the RESTRICTEDACCESS fileset attribute for the fileset fileset was changed from old-value to current-value. The values for the
RESTRICTEDACCESS fileset attribute are: Effect If current-value is ENABLED or LOCAL,
the super ID (255,255) is treated as a normal user and has no special
privileges. If current-value is DISABLED,
the super ID has the appropriate privilege to access any file. Recovery This is an informational message only; no corrective action
is needed. For information about restricted-access filesets, see the Open System Services Management and Operations Guide. |
| 46 State of OSS SEEP objectname changed from oldstate to newstate because of reason [with error error_number, error_detail] | | objectname | is the name of the OSS SEEP process. | | oldstate | is the old state of the process. The state can be
STOPPED or RUNNING. | | newstate | is the new state of the process. The state can be
STOPPED or RUNNING. | | reason | explains the cause of the change in the state of the
object. This cause is one of the following: | | error_number | is the error number reported for SEEP creation failure,
communication failure with SEEP, or the error returned by SEEP. The
possible error values are as follows: | | error_detail | is the error detail information returned by the underlying
call to the Guardian PROCESS_CREATE_ procedure or 0 in the case of
a communication failure or error returned by SEEP. |
Cause The state of OSS SEEP changed either by an SCF CONTROL FILESET/SERVER
or SCF START/STOP FILESET command issued by an operator or due to
some internal error or failure. Effect If SEEP creation fails or SEEP dies due to some internal error,
OSS name server retries the creation if creation failure is not due
to process parameter error. Recovery If the state of SEEP changes to STOPPED unexpectedly, the administrator
must verify the cause of state change and perform the necessary actions
to restart the OSS SEEP if it has not already been automatically restarted.
Look up the error information in the Guardian Procedure
Errors and Messages Manual, correct the problem, and restart
the SEEP via SCF. |
| 47 Error error in communication
with OSS SEEP objectname | | error | is the OSS file system or any other error obtained
when OSS name server tried to communicate with OSS SEEP. | | objectname | is the name of the OSS SEEP process. |
Cause An error occurred while sending the authorization request to
OSS SEEP. This includes: Errors when sending the request. A timeout in SEEP’s response. An error returned by SEEP.
Effect The OSS SEEP consultation does not happen. Recovery Perform any recovery action required based on the error value. |
| 48 Stopping process objectname not started by OSS name server | | objectname | is the name of the configured OSS SEEP process. |
Cause The OSS name server detected a running process with the same
process name as the configured OSS SEEP while attempting to start
OSS SEEP. Effect The OSS name server attempts to kill the running process to
guard against attempted security attacks and attempts to start OSS
SEEP with the configured process name. Recovery If the running process is valid, change the configured process
name for OSS SEEP and perform the necessary actions to restart OSS
SEEP. Otherwise, investigate the running process to determine if it
is part of a security attack. |
|