CMDTUX Messages 1000-1099

1001

ERROR: The MAXCONV parameter must be > 0 and < 32768.

Description

The MAXCONV parameter in the UBBCONFIG file must be greater than zero and less than 32768.

Action

Correct the value for MAXCONV as specified in the RESOURCES section of the UBBCONFIG file to be greater than 0 and less than 32768.

See Also

tmloadcf(1), ubbconfig(5)

1002

ERROR: The MIN parameter must be >=1 and <= 1000

Description

The MIN parameter in the UBBCONFIG SERVERS section must be greater than or equal to 1 and less than or equal to 1000.

Action

Correct the value for MIN as specified in the SERVERS section of the UBBCONFIG file to be greater than 0 and less than or equal to 1000.

See Also

tmloadcf(1), ubbconfig(5)

1003

ERROR: The MAX parameter must be >=1 and <= 1000

Description

The MAX parameter in the UBBCONFIG SERVERS section must be greater than or equal to 1 and less than or equal to 1000.

Action

Correct the value for MAX as specified in the SERVERS section of the UBBCONFIG file to be greater than or equal to 1 and less than or equal to 1000.

See Also

tmloadcf(1), ubbconfig(5)

1021

ERROR: The Primary and Backup LMIDs for a Group can't be the same.

Description

In the GROUPS section of the UBBCONFIG file, a group was specified as having a Backup machine (using the LMID,LMID syntax), but the LMIDs were the same. The Backup must be on a different machine from the Primary.

Action

Correct the value for LMID as specified in the GROUPS section of the UBBCONFIG so that the primary and backup machine names are different, or specify only one machine name.

See Also

tmloadcf(1), ubbconfig(5)

1022

WARN: The MIGRATE option was given without any Backup LMIDs present.

Description

The MIGRATE keyword appeared in the OPTIONS parameter in the RESOURCES section of the UBBCONFIG file, but neither a Group nor the Master were given Backup LMIDs (using the LMID,LMID syntax).

Note that some versions of BEA TUXEDO system R4.2 have a bug where this warning will appear even though a backup Master machine was specified.

Action

Make sure that either the Master machine was made migratable (using the LMID,LMID syntax for the MASTER parameter), or that at least one group was migratable (using LMID,LMID in the LMID parameter in the GROUPS section).

If only the Master is migratable, and the configuration looks ok, then this warning is probably due to the bug mentioned in the description. The message can be ignored in this case.

See Also

tmloadcf(1), ubbconfig(5)

1036

ERROR: The AUTHSVC parameter is NULL or longer than len characters.

Description

The AUTHSVC parameter in the RESOURCES section of the UBBCONFIG file must be a Service name that is less than or equal to 15 characters long.

Action

Change the AUTHSVC parameter in the UBBCONFIG file and re-load the configuration.

See Also

tmloadcf(1), ubbconfig(5)

1037

ERROR: MAXWSCLIENTS must be >= 0 and < 32768.

Description

The MAXWSCLIENTS parameter is outside the allowable range of values.

Action

Change the MAXWSCLIENTS parameter to be in the allowable range of values and re-load the configuration.

See Also

tmloadcf(1), ubbconfig(5)

1056

ERROR: Can't get Application Password

Description

When the SECURITY option is defined in the UBBCONFIG file, tmloadcf tries to get a password from the user. If the standard input is connected to a terminal, tmloadcf prompts for the password interactively. If not, it looks at the APP_PW environment variable.

This error happens if tmloadcf cannot open the tty device for prompting, or if APP_PW is not set.

Action

If running tmloadcf from a script, make sure that APP_PW is set and exported into the environment. Otherwise, contact your BEA TUXEDO system Technical Support.

See Also

tmloadcf(1), ubbconfig(5)

1057

WARN: Passwords do not match. Try again.

Description

tmloadcf prompts for the application password twice. If the two entries do not match, this message appears, and the sequence is repeated. Three separate tries are allowed.

Action

Re-enter the password correctly.

See Also

tmloadcf(1), ubbconfig(5)

1058

ERROR: Too many failures to obtain application password.

Description

After three failed attempts to read the application password, the tmloadcf program gives up and prints this message.

Action

Re-load the configuration again, entering matching password values.

See Also

tmloadcf(1), ubbconfig(5)

1070

ERROR: Unable to forward message, sending it back

Description

A server cleanup was underway. While draining the request queue, a function executed to (possibly) convert from one BEA TUXEDO system release to another failed. The possible causes of this error are: attempting to send a message that has an incorrect release identifier in the message header, or sending a message to a site with an unknown release.

Action

Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator.

1071

ERROR: Unable to forward message, sending it back

Description

A server cleanup was underway. While attempting to forward messages, a function executed to (possibly) convert from one BEA TUXEDO system release to another failed. The possible causes of this error are: attempting to send a message that has an incorrect release identifier in the message header, or sending a message to a site with an unknown release.

Action

Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator.

1073

WARN: Client process pid - dropped message because server died, SERVICE=service_name

Description

A server cleanup was underway. The BEA TUXEDO system logs a message to the userlog file indicating that the server had been cleaned up.

Action

Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator.

1074

WARN: Client process pid - dropped message because server and client died, SERVICE=service_name

Description

A server cleanup was underway. The BEA TUXEDO system logs a message to the userlog file indicating that the server and client had died.

Action

Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator.

1081

ERROR: Unable to read RESOURCES section of TUXCONFIG file

Description

A server cleanup was underway. The BEA TUXEDO system was unable to get information on the RESOURCES section from the TUXCONFIG file. Additional information from the userlog will indicate why the System was unable to do so. For example, the TUXCONFIG environment variable may not have been set.

Action

Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator.

1082

ERROR: Execute permission denied, not application administrator

Description

A server cleanup had been attempted, but the executor of this command did not have the proper permissions to execute the cleanupsrv command.

Action

Please contact the BEA TUXEDO system Administrator.

1089

ERROR: Unable to read the *RESOURCES section of the TUXCONFIG file

Description

The restartsrv process was not able to read the RESOURCES section of the TUXCONFIG file.

Action

The shared memory might be corrupted. Check the permissions on all IPC or contact your BEA TUXEDO system Technical Support. See LIBTUX_CAT Message 607 for further explanation.

1090

ERROR: Execute permission denied, not application administrator

Description

Execute permission was denied when a non-administrator was executing the restartsrv process.

Action

Only the BEA TUXEDO system application administrator can execute the command.

1091

ERROR: Invalid option, duplicate option option

Description

The tlisten -d option was passed twice at the command line.

Action

Invoke the tlisten command with only one -d option.

See Also

tlisten(1)

1092

ERROR: tlisten could not set group id to group_id

Description

The tlisten process failed to reset its group id.

Action

Verify that the user name or user id passed as an argument to the -u option has a valid entry in the /etc/passwd file.

See Also

tlisten(1)

1096

ERROR: Could not send broadcast to BBL (machine)

Description

A tpbroadcast message could not be sent to the BBL process on machine, because the message send operation failed. Clients on machine will not receive the broadcast.

A likely cause is UNIX system message queue blocking on the DBBL 's machine. The BRIDGE 's message queue may be full, or the total amount of message queue buffer space in the kernel may be exhausted. The ipcs -aq shell command is one way to verify this.

Action

• Check the machine's kernel parameters related to message queuing: MSGMNB, MSGSEG, MSGSSZ, and MSGMAX. Increase them if this seems reasonable.

• Check for any networking problems that might cause the BRIDGE to run slowly.

• Check for performance problems causing overload on the machine.

• Reduce the frequency of broadcasts.

See Also

BEA TUXEDO Installation Guide, tpbroadcast(3c), ipcs(1) in UNIX reference manuals

1097

WARN: DBBL should not be receiving notifications

Description

A tpnotify request for asynchronous client notification message should go directly to the BBL process on the client's machine. One was unexpectedly received by the DBBL process, which ignored it.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

tpnotify(3c)

1098

ERROR: Can't create queue

Description

Queues used for communication with the (D)BBL could not be created.

Action

Examine the userlog for further details. Contact your BEA TUXEDO system Technical Support.