Chapter 61 NonStop TUXEDO Messages

The messages in this chapter are generated by the NonStop TUXEDO subsystem. The subsystem ID displayed by these messages includes NonStop TUXEDO as the subsystem name. Additional information is contained in the event’s SPI buffer, which contains, for example, the NonStop TUXEDO application, the NonStop TUXEDO catalog and message number. See the EVENTS_EMS reference page in the NonStop TUXEDO documentation for details on the SPI buffer generated by NonStop TUXEDO.




	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.

INFO:.SysACLPerm: User %TA_USRNAME on %TA_LMID tried to access %TA_ACLTYPE %TA_ACLNAME

TA_USRNAME	User name associated with client at tpinit () time via the usrname element of the TPINIT structure). The name must be a string 0 to 30 characters in length.
TA_LMID	Logical machine where client is running (native clients) or where client is connected (workstation clients).
TA_ACLTYPE	The type of the entity for which permissions are being granted.
TA_ACLNAME	The name of the entity for which permissions are being granted. The name can represent a service name, an event name, and/or a queue name. An ACL name is a string of printable characters and cannot contain a colon, pound sign, or newline.

Cause This event is generated when a client attempts to access a service, event, or queue for which it was not granted access via an access control list. The user identifier (configured in the user or principal file), the machine, entity type, and entity name are printed.

Effect The access has failed.

Recovery No action required. The access will fail with an error and an event will be generated. Further action may be required on the part of the NonStop TUXEDO security administrator. See also LIBTUX messages 1515 and 1516.

INFO:.SysClientConfig: User %TA_USRNAME on %TA_LMID configuration change

TA_USRNAME	User name associated with client at tpinit () time via the usrname element of the TPINIT structure). The name must be a string 0 to 30 characters in length.
TA_LMID	Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the attributes on the client specified above have been changed. A complete listing of the current attributes of the client is sent in the posted buffer.

Effect The client’s configuration is changed.

Recovery This is an informational message; no corrective action needed. See also LIBTMIB message 253 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO:.SysClientDied: User %TA_USRNAME on %TA_LMID client died

TA_USRNAME	User name associated with client at tpinit () time via the usrname element of the TPINIT structure). The name must be a string 0 to 30 characters in length.
TA_LMID	Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the client specified exited the application without executing a tpterm(). A complete listing of the current attributes of the client is sent in the posted buffer. Normally, the clients should execute a tpterm() before exiting the application.

Effect The client is not connected to the application.

Recovery This is an informational message; no corrective action needed. See LIBTUX message 1481, WSNAT message 1199, and JOLT message 1199. See also the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

WARN:.SysClientSecurity: User %TA_USRNAME on %TA_LMID authentication failure

TA_USRNAME	User name associated with client at tpinit () time via the usrname element of the TPINIT structure). The name must be a string 0 to 30 characters in length.
TA_LMID	Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the client specified above failed security validation when trying to join the application. A complete listing of the current attributes of the client is sent in the posted buffer.

Effect The client is not joined to the application.

Recovery Check to make sure that there has not been a security breach. See LIBTUX message 1484, WSNAT message 1201, and JOLT message 1201. See also the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO:.SysClientState: User %TA_USRNAME on %TA_LMID state change to %TA_STATE

TA_USRNAME

User name associated with client at tpinit () time via the usrname element of the TPINIT structure). The name must be a string 0 to 30 characters in length.

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

TA_STATE

{ACTIVE | INACTIVE | SUSPENDED | DEAD}

ACTIVE

T_CLIENT object active. This is not an indication of whether the client is idle or busy.

INACTIVE

T_CLIENT object defined and inactive.

SUSPENDED

T_CLIENT object active and suspended from making further service requests.

DEAD

T_CLIENT object identified as active in the bulletin board but currently not running due to the abnormal death of the client.

Cause This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client is sent in the posted buffer.

Effect The client is now in the state specified in the message.

Recovery This is an informational message; no action needed. See LIBTUX messages 1482 and 1483, CMDTUX message 4069, JOLT message 1200, WSNAT message 1200, and LIBTMIB message 251. See also the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysEventDelivery: System Event Monitor delivery failure on %TA_LMID

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the event server failed to perform at least one notification for a posted event.

Effect At least one of the subscription actions has not been performed.

Recovery Check to make sure that the notifications specified in the NonStop TUXEDO subscriptions that match the posted event can be performed. See also CMDTUX message 4076 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

WARN: .SysMachineBroadcast: %TA_LMID broadcast delivery failure

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that tpbroadcast() failed for at least one accesser on the LMID of the application. A complete listing of the machine parameters are sent along in the posted buffer.

Effect At least one client has not been notified of the broadcast message.

Recovery Since the broadcast messages are sent in non-blocking mode, it is possible that the process doing the broadcasting encountered a blocking condition and dropped a message. For the NonStop TUXEDO application, configure larger message queues and/or load-balance clients/servers such that excessive load is not put on some machines. See also LIBTUX message 1498 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO:.SysMachineConfig: %TA_LMID configuration change

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that parameters in the T_MACHINE class for the given LMID have been updated. A complete listing of the current parameters for the given LMID are sent along in the posted buffer.

Effect The configuration of the specified LMID changed.

Recovery This is an informational message; no corrective action needed. See also LIBTMIB message 240 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR:.SysMachineCPUDown: %TA_PMID processing element failure

TA_PMID

Physical machine identifier with the ASCII CPU number appended following a period.

Cause This message indicates that one of the CPUs on an active machine has failed. The string PMID is the physical machine identifier with the CPU number of the failed CPU, for example, “NODE.3”. The NonStop TUXEDO application on that machine should continue to run, and the services are still available. Servers that had been running on the affected CPU are restarted on other configured CPUs.

Effect Clients and servers connected to the NonStop TUXEDO application running in the affected CPU will fail. Servers will be restarted by NonStop TUXEDO if appropriate and possible; client restart is application dependent.

Recovery If this is an unintended CPU failure, take a CPU dump and determine the cause of the failure. Reload the CPU. See also TDM message 2208 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO:.SysMachineCPUUp %TA_PMID processing element up

TA_PMID

Physical machine identifier with the ASCII CPU number appended following a period.

Cause This informational message indicates that the CPU identified in the message is operational.

Effect Servers might be started automatically in the reloaded CPU, allowing the configured server balance to be reached.

Recovery This is an informational message; no corrective action needed. See also TDM message 2209 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

WARN:.SysMachineFullMaxaccessers: %TA_LMID capacity limit

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the given LMID reached the capacity limit on the number of accessers. A complete listing of the current parameters for the given LMID are sent along in the posted buffer.

Effect New accessers are unable to join the application until existing accessers exit the application.

Recovery Increase the MAXACCESSERS for the particular machine in the NonStop TUXEDO application, or if the hardware/software limits have been reached for the maximum number of users on the machine, move additional users to other machines. See also LIBTUX message 1491 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

WARN:.SysMachineFullMaxconv: %TA_LMID capacity limit

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the given LMID reached the capacity limit on the number of concurrent conversations. A complete listing of the current parameters for the given LMID are sent along in the posted buffer.

Effect New conversations are unable to join the application until an existing conversation ends.

Recovery Increase the value of MAXCONV for the particular machine in the NonStop TUXEDO application configuration to avoid this event. See also LIBTUX message 1488 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

WARN:.SysMachineFullMaxwsclients: %TA_LMID capacity limit

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the given LMID reached the capacity limit on the number of WS clients. A complete listing of the current parameters for the given LMID are sent along in the posted buffer.

Effect New workstation clients are unable to join the application until existing workstation clients exit the application.

Recovery Increase the value of MAXWSCLIENTS for the particular machine in the NonStop TUXEDO application configuration such that this event is not generated. See also LIBTUX message 1490 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

WARN:.SysMachineMsgq: %TA_LMID message queue blocking

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the server posting a message encountered a blocking condition while putting a message on the message queue. A complete listing of the machine parameters are sent along in the posted buffer.

Effect The message is not sent.

Recovery Distribute the load equally on all the CPUs. See also LIBTUX message 1497 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR:.SysMachineNetworkDown: %TA_LMID connection lost

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This message indicates that the Expand network connection from the master machine to the indicated machine has been lost. LMID is the logical machine name (from the UBBCONFIG file) of the affected nonmaster machine. Communication from the master machine to LMID is no longer possible. The application servers and services running on LMID are marked “PARTITIONED” and are not available.

This problem can arise from two causes: 1) there may be a network failure between the machines; or 2) the nonmaster machine may have completely failed. Closer examination of the remote machine from a directly connected terminal can determine if the machine has failed.

Effect The processing power of the remote machine is lost until the connection is restored.

Recovery The recovery depends on the cause of the failure. If it was a network failure, after the problem has been resolved, the network connection can be restored. NonStop TUXEDO automatically senses the reconnection and makes the servers and services on LMID available.

If it was a machine failure, the problem should be analyzed and corrected and the machine restarted. NonStop TUXEDO automatically senses the reconnection and notices that the applications are no longer running on LMID. It then deletes the affected servers and services. tmboot can be used to restart the TUXEDO application on LMID.

An alternative recovery for either case is to use the tmadmin pclean command, or the GUI clean command to delete the partitioned servers and services and free up their resources. If the problem was a network failure tmshutdown -P LMID can be run on the remote machine to stop the partitioned application servers.

See also TDM message 2210 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO:.SysMachineNetworkUp: %TA_LMID connection reestablished

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

Cause This informational message states that the network connection is reestablished.

Effect The network connection is reestablished.

Recovery This is an informational message; no corrective action needed. See also TDM message 2211 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR:.SysMachinePartitioned: %TA_PMID is partitioned

TA_PMID

Physical machine identifier with the ASCII CPU number appended following a period.

Cause This message indicates that the DBBL partitioned the stated machine either because the BBL on the machine is slow or the network link between the master and the machine is broken.

Effect While the BBL is partitioned, new clients and servers may not be able to attach to the application in that CPU.

Recovery This can be caused due to various reasons. The first one is that the entire network is slowed down due to heavy traffic. The second one is that the BBL on the nonmaster machine is either dead or slow. The software is capable of unpartitioning the machine. See also LIBTUX message 1492 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

WARN:.SysMachineSlow: %TA_PMID slow responding to DBBL

TA_PMID

Physical machine identifier with the ASCII CPU number appended following a period.

Cause This message indicates that the BBL on the nonmaster machine is slow in generating IAMOK messages. These messages are sent periodically from the BBLs to the DBBL which helps the DBBL maintain the pulse of the system.

Effect This could be an indication that the BBL will become partitioned.

Recovery This can be caused due to various reasons. The first one is that the entire network is slowed down due to heavy traffic. The second one is that the BBL on the nonmaster machine is either down or slow. This problem can be intermittent. See also LIBTUX message 1496 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO:.SysMachineState: %TA_LMID state changed to %TA_STATE

TA_LMID

Logical machine where client is running (native clients) or where client is connected (workstation clients).

TA_STATE

{INVALID | INACTIVE | PARTITIONED}

INVALID

Delete T_MACHINE object for application. State change allowed only when in the INACTIVE state. Successful return leaves the object in the INVALID state.

INACTIVE

T_MACHINE object defined and inactive.

PARTITIONED

T_MACHINE object defined, listed in accessible bulletin boards as active, but currently unreachable.

Cause This informational message states that the state has changed.

Effect The machine’s state has changed to the state indicated in the message.

Recovery This is an informational message; no corrective action needed. See LIBTUX message 1517, LIBTMIB message 248, and CMDTUX messages 4058, 4064, 4483, 4075, and 4485. See also the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO:.SysMachineUnpartitioned: %TA_PMID is unpartitioned

TA_PMID

Physical machine identifier with the ASCII CPU number appended following a period.

Cause A machine that was partitioned is again available to service requests.

Effect The BBL in the indicated CPU has rejoined the application.

Recovery This is an informational message; no corrective action needed. See also LIBTUX message 1495 and CMDTUX message 4484. See also the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO: .SysResourceConfig: system configuration change

Cause This message indicates that parameters in the T_DOMAIN class have been updated. A complete listing of the current parameters are sent along in the posted buffer.

Effect The T_DOMAIN class is updated.

Recovery This is an informational message; no corrective action needed. See also LIBTMIB message 235 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysServerCleaning: %TA_SERVERNAME, group %TA_SRVGRP, id %TA_SRVID server cleaning

TA_SERVERNAME	Full pathname of the server executable file. The server identified by TA_SERVERNAME is running on the machine identified by the T_QUEUE:TA_LMID attribute.
TA_SVRGRP	Logical name of the server group.
TA_SRVID	Unique number (within the server group) server identification number.

Cause This message indicates that the server specified above aborted abnormally and the BBL cleaned up the slot allocated by the server.

Effect The failed server is removed from the BB.

Recovery Debug the server and fix the problem before the server is restarted. See LIBTUX message 1475 and CMDTUX message 4484. See also the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO: .SysServerConfig: %TA_SERVERNAME, group %TA_SRVGRP, id %TA_SRVID configuration change

TA_SERVERNAME	Full pathname of the server executable file. The server identified by TA_SERVERNAME is running on the machine identified by the T_QUEUE:TA_LMID attribute.
TA_SVRGRP	Logical name of the server group.
TA_SRVID	Unique number (within the server group) server identification number.

Cause This message indicates that the configuration parameters for the server specified above have been updated. A complete listing of the attributes of the server is sent along in the posted buffer.

Effect The server’s configuration is updated.

Recovery This is an informational message; no corrective action needed. See also LIBTMIB message 249 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysServerDied: %TA_SERVERNAME, group %TA_SRVGRP, id %TA_SRVID server died

TA_SERVERNAME	Full pathname of the server executable file. The server identified by TA_SERVERNAME is running on the machine identified by the T_QUEUE:TA_LMID attribute.
TA_SVRGRP	Logical name of the server group.
TA_SRVID	Unique number (within the server group) server identification number.

Cause This message indicates that the server specified aborted abnormally and the BBL detected this condition.

Effect The server abnormally ended.

Recovery Debug the server and fix the problem before the server is restarted. See also LIBTUX message 1477, CMDTUX message 4136, and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysServerInit: %TA_SERVERNAME, group %TA_SRVGRP, id %TA_SRVID server initialization failure

TA_SERVERNAME	Full pathname of the server executable file. The server identified by TA_SERVERNAME is running on the machine identified by the T_QUEUE:TA_LMID attribute.
TA_SVRGRP	Logical name of the server group.
TA_SRVID	Unique number (within the server group) server identification number.

Cause This message indicates that the server specified above failed in tpsvrinit() and therefore could not be booted.

Effect The server is not running.

Recovery Fix the problem and then reboot the server. The problem could be due to a NonStop TUXEDO resource limit or it could be an application-specific problem. See also LIBTUX message 1478 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysServerRestarting: %TA_SERVERNAME, group %TA_SRVGRP, id %TA_SRVID restarting

TA_SERVERNAME	Full pathname of the server executable file. The server identified by TA_SERVERNAME is running on the machine identified by the T_QUEUE:TA_LMID attribute.
TA_SVRGRP	Logical name of the server group.
TA_SRVID	Unique number (within the server group) server identification number.

Cause This message indicates that the server specified above aborted abnormally and will be restarted.

Effect TS/MP 3.0 will try to restart the server if it appears to be a viable serverclass. Otherwise, a .SysServerCleaning event is posted indicating the server is not running.

Recovery NonStop TUXEDO application servers should not ordinarily abort abnormally. The problem is most likely an application-specific problem. Debug the server and resolve the problem before restarting the server. See also LIBTUX message 1476 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

INFO: .SysServerState: %TA_SERVERNAME, group %TA_SRVGRP, id %TA_SRVID state change to %TA_STATE

TA_SERVERNAME	Full pathname of the server executable file. The server identified by TA_SERVERNAME is running on the machine identified by the T_QUEUE:TA_LMID attribute. When specified as a key field on a GET operation, this attribute may specify a relative pathname; all appropriate full pathnames will be matched to the relative pathname.
TA_SVRGRP	Logical name of the server group. The group name must be unique within all group names in the T_GROUP class and TA_LMID values in the T_MACHINE class. Server group names cannot contain an asterisk (*), comma, or colon.
TA_SRVID	Unique number (within the server group) server identification number.
TA_STATE	{INVALID \| INACTIVE \| SUSPENDED \| ACTIVE \| RESTARTING \| CLEANING \| DEAD} INVALID Delete T_DEVICE object for application. State change allowed only when in the VALID state. Successful return leaves the object in the INVALID state. INACTIVE T_SERVER object defined and inactive. SUSPENDED T_SERVER object defined and currently suspended pending shutdown. ACTIVE T_SERVER object defined and active. RESTARTING T_SERVER object defined and currently being restarted by the system due to the object's abnormal death. CLEANING T_SERVER object defined and currently being cleaned up after by the system due to an abnormal death. DEAD T_SERVER object defined, identified as active in the bulletin board, but currently not running due to the object's abnormal death. This state will exist only until the BBL local to the server notices the death and takes action (REStarting \| CLEaning).

Cause This message indicates that the server specified above changed to a new state. A complete listing of the server attributes are sent in the posted buffer.

Effect The server has the reported or indicated new state.

Recovery This is an informational message; no corrective action needed. See LIBTMIB message 250, CMDTUX message 4068, and LIBTUX message 1518. See also the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysServerTpexit: %TA_SERVERNAME, group %TA_SRVGRP, id %TA_SRVID requested TPEXIT

TA_SERVERNAME	Full pathname of the server executable file. The server identified by TA_SERVERNAME is running on the machine identified by the T_QUEUE:TA_LMID attribute.
TA_SVRGRP	Logical name of the server group.
TA_SRVID	Unique number (within the server group) server identification number.

Cause This message indicates that the server specified received a request and the service routine code executed a tpreturn (TPEXIT) while the server was executing application-specific code.

Effect The server is not running.

Recovery No action required. See also LIBTUX message 1479 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysDomainTranHeuristicAbort: Transaction %TA_DMTXID in domain %TA_LDOMAIN

TA_DMTXID	The TMF transaction identifier mapped to a string representation.
TA_LDOMAIN	The local DOMAINID for the NonStop TUXEDO domain.

Cause This message indicates that the gateway tried to abort the transaction but the Transaction Manager reported that it has no record of the transaction. The Transaction Manager does not know the outcome of the transaction and has no means of determining it.

Effect The transaction aborted.

Recovery Contact your service provider. See also TDM message 3616 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysDomainTranHeuristicCommit: Transaction %TA_DMTXID in domain %TA_LDOMAIN

TA_DMTXID	The TMF transaction identifier mapped to a string representation.
TA_LDOMAIN	The local DOMAINID for the NonStop TUXEDO domain.

Cause This message indicates that the database in the group specified above performed heuristic commit on the transaction indicated in the message.

Effect The transaction committed.

Recovery Check to make sure that the coordinator of the transaction is still up and running. See also TDM message 3617 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.

ERROR: .SysDomainTranProtoResend: Transaction %TA_DMTXID in domain %TA_LDOMAIN

TA_DMTXID	The TMF transaction identifier mapped to a string representation.
TA_LDOMAIN	The local DOMAINID for the NonStop TUXEDO domain.

Cause The /Domain gateway process had to resend a two-phase commit protocol message for the specified transaction. If the message is resent more than once, this message is displayed the first time only. This message usually indicates that the network connection to a remote gateway failed or that the remote gateway failed.

Effect The /Domain gateway resends the message but operator intervention may be required to resolve the problem.

Recovery The remote domains participating in the transaction can be determined using the dmadmin command printtrans. If possible, recover the network connection or restart the remote gateway. The transaction is resolved either when the remote gateway restarts or when the message is resent. See also TDM message 3618 and the EVENT_MIB and TM_MIB reference pages in the NonStop TUXEDO online documentation.