CMDTUX Messages 1600-1699
|
|
1600
ERROR: Unable to register - another DBBL already exists on machine
Description
The BEA TUXEDO system application was unable to unregister the DBBL process because another DBBL was found to have been booted already.
Action
No action required.
1601
ERROR: TUXCONFIG,TUXOFFSET device1 offset1 doesn't match first device entry on configuration device2 offset2
Description
While loading a TUXCONFIG file using tmloadcf, the device and offset specified by the TUXCONFIG and TUXOFFSET environment variables, device1 and offset1, don't match the information stored for the first entry in the configuration file, device2 and offset2. This occurs when the device (file) is moved from one name to another.
Action
Remove the configuration file before loading it with tmloadcf.
See Also
tmloadcf(1)
1603
ERROR: TLOGDEVICE must be an absolute pathname
Description
The value for the TLOGDEVICE parameter as specified in the MACHINES section of the UBBCONFIG file must be an absolute pathname. Relative paths and environment variables are not valid.
Action
Correct the value for TLOGDEVICE as specified in the MACHINES section of the UBBCONFIG file to be an absolute pathname.
See Also
ubbconfig(5)
1604
ERROR: section_name entry entry_name - duplicate type(type_name)/subtype(subtype_name)
Description
The BUFTYPE parameter of a SERVICES section entry or ROUTING section entry in the UBBCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the BUFTYPE parameter specified duplicate type pairs.)
Action
Modify the BUFTYPE parameter so that the same type/subtype pair is not specified more than once. Reload the configuration file.
See Also
ubbconfig(5)
1605
ERROR: SERVICES entry entry_name - must have the same BUFTYPE for all SERVICE entries.
Description
If multiple entries exist in the SERVICES section with the same service name but with different SRVGRP parameters, the BUFTYPE parameter must be the same for all of the entries. This rule was violated for the service entry named in the error message.
Action
Specify the same BUFTYPE parameters for all instances of a particular service name. Then reload the configuration file.
See Also
ubbconfig(5)
1614
WARN: Network device does not exist
Description
The device specified for the -d option of tlisten does not exist or is not a character special device. If the sockets network provider is being used, the device is not needed and will be ignored. If the TLI network provider is being used, the network open will fail.
Action
If TLI is being used, specify the correct network device pathname.
See Also
tlisten(1)
1615
ERROR: Identifier or number must be followed by white space or punctuation
Description
While parsing a UBBCONFIG file, invalid syntax was found. This generally occurs when a keyword or operator is missing (for example, two numbers appear together).
Action
Correct the syntax and re-load the configuration file.
See Also
ubbconfig(5)
1624
ERROR: Invalid or unspecified administrative password
Description
An administrative request generated by tmboot to the remote machine indicated in subsequent messages produced to stderr was rejected because either an invalid administrative password was passed to the remote site or no administrative password was available to be passed to the remote site.
Action
If no administrative password was specified locally, then determine an appropriate administrative password and set the local environment to pass it to remote sites as indicated in tmboot.
If an administrative password was specified locally, then either the local setting will have to change to match that expected by the remote site, or the administrative password used by this application will have to be added to the password file used by tlisten on the remote site.
See Also
tmboot(1), tlisten(1)
1626
ERROR: Machine "pmid" cannot be of the form "name.number"
Description
While parsing a UBBCONFIG file, an invalid machine name was specified. The name has a value of the form name.number (this is restricted only in the development copy, compiled to allow what is called fake mp).
Action
Correct the syntax error and re-load the configuration file.
See Also
ubbconfig(5)
1627
ERROR: LMID "value" must not contain comma
Description
While parsing a UBBCONFIG file, an invalid LMID value was found. The LMID value contains a comma.
Action
Correct the syntax and re-load the configuration file.
See Also
ubbconfig(5)
1628
ERROR: LMID "value" must not contain comma
Description
While parsing a UBBCONFIG file, an invalid LMID value was found. The LMID value contains a comma.
Action
Correct the syntax and re-load the configuration file.
See Also
ubbconfig(5)
1629
ERROR: Cannot allow only release 4.2.x BBLs to join system with a configuration of number machines or more
Description
An attempt was made to boot a 4.2.x site into an application with more than number configured machines.
Action
Either reduce the number of configured machines and reboot the site, or upgrade the site to release 5.0.x or later.
See Also
BEA TUXEDO Administrator's Guide
1631
ERROR: MAXMACHINES parameter must be >= number and < 8191
Description
The MAXMACHINES parameter in the RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of number to 8190.
Action
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1633
ERROR: MAXQUEUES parameter must be > 0 and < 8192
Description
The MAXQUEUES parameter in the RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of 1 to 8191.
Action
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1634
ERROR: MAXQUEUES(number) and MAXSERVERS(number) must be equal to interoperate with release number
Description
An attempt was made to boot a 4.2.x site with the MAXQUEUES and MAXSERVERS parameters in the RESOURCES section of the ubbconfig(5) file set to different values.
Action
Either reconfigure the application to have equivalent values for these parameters and reboot the site, or upgrade the 4.2.x site to release 5.0.x or later.
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1636
ERROR: MAXGROUPS parameter must be >= number and < 32767
Description
The MAXGROUPS parameter in the RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of number to 32767.
Action
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1638
ERROR: Invalid CMPLIMIT value string
Description
The CMPLIMIT parameter in the MACHINES section of the ubbconfig(5) file has been specified with an invalid value string.
Action
Correct the value for this parameter to the acceptable format and rerun tmloadcf(1). The acceptable format for this parameter is remote[,local] where both remote and local may be either the string MAXLONG or a non-negative numeric value.
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1640
ERROR: NETLOAD parameter must be >= 0
Description
The NETLOAD parameter in the MACHINES section of the ubbconfig(5) file was specified as a negative value.
Action
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1642
ERROR: SPINCOUNT parameter must be >= 0
Description
The SPINCOUNT parameter in the MACHINES section of the ubbconfig(5) file was specified as a negative value.
Action
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1643
ERROR: More than MAXGROUPS(number) groups in configuration file
Description
The application was configured to handle up to number configured server groups (see the MAXGROUPS parameter in the RESOURCES section of the ubbconfig(5) file) and has excess server groups defined in the ubbconfig(5) file.
Action
Either reset the MAXGROUPS parameter in the RESOURCES section or delete server groups from the *GROUPS section of the ubbconfig(5) file and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1644
ERROR: More than MAXMACHINES(number) machines in configuration file
Description
The application was configured to handle up to number configured machines (see the MAXMACHINES parameter in the RESOURCES section of the ubbconfig(5) file) and has excess machines defined in the MACHINES section of the ubbconfig(5) file.
Action
Either reset the MAXMACHINES parameter in the RESOURCES section or delete machines from the MACHINES section of the ubbconfig(5) file and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1645
ERROR: Illegal opcode (number) sent to tagent
Description
An invalid opcode number was sent to the tagent process.
Action
The most likely cause of this problem is a non-BEA TUXEDO system process incorrectly connecting to the BEA TUXEDO system listener (tlisten(1)) process and attempting to interact with the tagent. In this case, the non-BEA TUXEDO system process should be changed to not connect to tlisten. If this is not the case, then contact your BEA TUXEDO system Technical Support for further assistance.
1646
ERROR: MAXGROUPS(num1) must be num2 to interoperate with release num3
Description
The configured value num1 for the maximum number of configured groups in the application (see the MAXGROUPS parameter in the RESOURCES section of the ubbconfig(5) file) is not set to the value num2 required for interoperability with release num3.
Action
Either modify the value of this parameter in the configuration file and rerun tmloadcf(1), or upgrade the site in question to a later release of the BEA TUXEDO system.
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), tmunloadcf(1), ubbconfig(5)
1647
ERROR: Cannot migrate master from release num1 to release num2
Description
Master migration from a release num1 site to a num2 site was attempted.
Action
Change the backup site to be one of the same release as the master site.
See Also
BEA TUXEDO Administrator's Guide, tmadmin(1), tmloadcf(1), ubbconfig(5)
1649
ERROR: Backup master is running invalid release number
Description
The backup master site attempted to boot with an invalid release number.
Action
Either change the backup master site to one of the same release as the master site, or upgrade the backup master site release.
See Also
BEA TUXEDO Administrator's Guide, tmadmin(1), tmboot(1), tmloadcf(1), ubbconfig(5)
1651
ERROR: Cannot join system with DBBL running older release number
Description
A BBL attempted to boot into an application with a master site running an older release than its own, number.
Action
Either run the older release on the site in question, or upgrade the master site to be one running the latest BEA TUXEDO system release desired.
1655
ERROR: SVCTIMEOUT parameter must not be < 0
Description
The SVCTIMEOUT parameter in the SERVICES section of the ubbconfig(5) file was specified as a negative value.
Action
Change the parameter value in the ubbconfig(5) file and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1666
WARN: Could not terminate server(pid) processing after SVCTIMEOUT
Description
The BBL could not abortively deactivate the server with process id pid after the server exceeded the configured SVCTIMEOUT value for the service it was currently processing.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5), kill(2) in UNIX reference manuals
1667
WARN: Server(pid) processing terminated after SVCTIMEOUT
Description
The BBL has terminated the local server with process id pid using the kill(2) system call to generate a SIGKILL signal because the server exceeded the maximum service processing time for the current service as configured via the SVCTIMEOUT parameter in the *SERVICES section of the ubbconfig(5) file.
Action
Either increase the configured service timeout value, or modify the server to complete the service within the allotted time interval.
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5), kill(2) in UNIX reference manuals
1668
WARN: Cannot shutdown BBL on machine. Clients and/or servers may be running
Description
A shutdown request has been received, but the BBL cannot be shut down because processes are still attached.
Action
Check on what processes are running to see if they can be individually killed.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1), kill(2) in UNIX reference manuals
1669
ERROR: If SECURITY is not set, then AUTHSVC must not be specified.
Description
While parsing a UBBCONFIG file, an AUTHSVR value was found but the SECURITY parameter is not set.
Action
Correct the syntax and re-load the configuration file.
See Also
ubbconfig(5)
1670
ERROR: IPCKEY parameter must be > number and < 262143
Description
The IPCKEY parameter in the *RESOURCES section of the ubbconfig(5) file is not within the acceptable limits as indicated by the message.
Action
Correct the value for this parameter in the configuration file and rerun tmloadcf(1).
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1671
ERROR: Could not initialize /Admin service
Description
The DBBL could not initialize the administrative services necessary for application administration.
Action
Consult the local userlog file and contact your BEA TUXEDO system Technical Support.
1672
ERROR: Could not initialize /Admin service
Description
The BBL could not initialize the administrative services necessary for application administration.
Action
Consult the local userlog file and contact your BEA TUXEDO system Technical Support.
1673
ERROR: Invalid logical machine
Description
While trying to handle a TMIB request for the T_NETWORK class, an invalid logical machine name (TA_LMID) was specified.
Action
Ensure that a valid logical machine name is specified (one that is already configured) and re-run the operation.
See Also
TM_MIB(5)
1674
ERROR: Failed to establish connection
Description
While trying to satisfy a MIB request for the T_NETWORK class to change the state of a connection to ACTIVE, the connection failed.
Action
Ensure that the machine to which the connection is being made and the network are available and re-try the operation.
See Also
TM_MIB(5)
1675
ERROR: Unable to allocate buffer for master migration reply
Description
An attempt dynamically to allocate memory from the operating system failed while trying migrate the master to the backup machine. No response will be returned to the requester of the operation.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1676
ERROR: System tables corrupted
Description
An internal error occurred while trying to migrate the master.
Action
Contact your BEA TUXEDO system Technical Support.
1677
ERROR: Master migration attempted in non-LAN application
Description
A master migration to the backup was requested but the configuration does not have the LAN option configured (and thus doesn't have a backup).
Action
No action required.
See Also
ubbconfig(5)
1678
ERROR: Invalid parameters for master migration
Description
A master migration to the backup was requested, but the master and backup are on the same machine or the DBBL has already been migrated. This should not occur.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
ubbconfig(5)
1679
ERROR: Master migration failed, no available backup site
Description
A master migration was requested but the BBL is not running on the backup site (or the site is already partitioned).
Action
The migration cannot occur in this situation. Make sure that the backup machine and the network are available, and that the application is booted on the machine. Then re-try the operation.
See Also
ubbconfig(5), TM_MIB(5)
1680
ERROR: Master migration failed, could not modify queue parameters
Description
A master migration was requested but the operation failed because the queue for the DBBL could not be re-set to take no more messages. This could occur if the queue were manually deleted or an error occurred with the IPC sub-system.
Action
Re-try the operation. For subsequent failures, shutdown and re-boot the application.
See Also
ubbconfig(5), TM_MIB(5)
1681
ERROR: Master migration failed, could not requeue message
Description
A master migration was requested but the operation failed because an error failed in putting a message on the queue for the DBBL. This could occur if the queue were manually deleted or an error occurred with the IPC sub-system (e.g., the message queues were full).
Action
Re-try the operation.
See Also
ubbconfig(5), TM_MIB(5)
1682
ERROR: Could not retrieve own BB entry for migration
Description
The DBBL process is migrating to another machine. However, it could not find its own server table entry in the bulletin board. This prevents the old DBBL from broadcasting where the new DBBL is located.
Action
After this shaky migration it is possible that a DBBL process is running on both the master or backup machines. If so, shut down the machine with the newest one (that is, the destination of the last migrate command). Then boot that machine up and try to migrate again. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1), tmshutdown(1)
1683
ERROR: Connection received from inactive machine lmid
Description
The machine indicated by the logical machine identifier lmid attempted to connect to the local site but is not active in the application.
Action
This is caused when a partitioned live node is cleaned up in the non-partitioned part of the application (see the pclean subcommand of tmadmin(1)) and then later reconnects to one of the non-partitioned sites. The problem can be resolved using the tmshutdown(1) command with the -P option on the partitioned site to bring down the application, followed by a reboot of the site from the non-partitioned master site. The problem can be avoided by carefully checking the status of a partitioned site prior to invoking the pclean subcommand.
See Also
BEA TUXEDO Administrator's Guide, tmadmin(1), tmboot(1), tmshutdown(1)
1684
ERROR: Application initialization failure
Description
Server failed to restart due to application initialization failure.
Action
This is an application specific failure and must be resolved with application knowledge of server initialization.
See Also
BEA TUXEDO Programmer's Guide
1685
ERROR: Application initialization failure
Description
Server failed to boot due to application initialization failure from tpsvrinit(3c).
Action
Identify application initialization problem and resolve prior to booting the server again.
See Also
BEA TUXEDO Programmer's Guide, tpopen(3c), tpsvrinit(3c), servopts(5)
1686
ERROR: Older release sites cannot join an application with deleted machines in the *MACHINES section
Description
An activation request was received for a a computer running a version prior to release 5.0. However, one or more machines were dynamically deleted from the configuration. A pre-5.0 machine cannot join the application in this situation.
Action
Shutdown the entire application and then re-boot (including the older release machines).
See Also
tmboot(1), TM_MIB(5)
1687
ERROR: No active servers found in class instance
Description
A deactivation (shutdown) request was received. However, based on the values of TA_SRVGRP, TA_SRVID, TA_GRPNO, TA_SERVERNAME, TA_LMID and TA_SEQUENCE for the T_SERVER class, no servers match the desired criteria and no servers will be deactivated.
Action
No action required. Check the activated servers and re-try the operation with valid selection criteria.
See Also
TM_MIB(5)
1688
ERROR: Could not retrieve information on servers
Description
A deactivation (shutdown) request was received. However, based on the values of TA_SRVGRP, TA_SRVID, TA_GRPNO, TA_SERVERNAME, TA_LMID and TA_SEQUENCE for the T_SERVER class, no servers match the desired criteria and no servers will be deactivated.
Action
No action required. Check the activated servers and re-try the operation with valid selection criteria.
See Also
TM_MIB(5)
1689
ERROR: Could not shutdown any servers
Description
A request was received to deactivate one or more servers. Although some servers matched the requested criteria, no servers were shutdown. This could be because the servers could not be contacted, they might be looping, or administrative servers might not shutdown because other clients or servers are still running.
Action
Re-try the operation. It may be necessary to request a forced shutdown, setting the state to DEAd, in which servers will be killed and administrative servers are shutdown even if clients exist.
See Also
tmshutdown(1), TM_MIB(5)
1690
ERROR: System error (error_string) while shutting down server
Description
A MIB request was received to shutdown a server but the request to the server failed, due to a system error. More information regarding the failure is printed as part of the message. For example, it could be that the message queues are full.
Action
Re-try the operation.
See Also
TM_MIB(5)
1691
ERROR: System server cannot shutdown with clients and/or servers attached
Description
A TMIB request to shutdown an administrative server failed because one or more clients and/or servers is still active.
Action
Stop active clients and shutdown application servers before shutting down the administrative servers, or use a forced shutdown that ignores clients and kills application servers.
See Also
TM_MIB(5)
1692
ERROR: Application server will not shutdown
Description
A TMIB request to shutdown an application server failed because server refused to shutdown.
Action
Use a forced shutdown, setting the state to DEAd, which kills application servers.
See Also
TM_MIB(5)
1693
WARN: Timeout period expired on /Admin blocking request
Description
A MIB request was received to shutdown a server but the request to the server failed, due to timeout. This indicates that the server took too long to shutdown. This could indicate that the server is busy (or looping).
Action
Re-try the operation. To force a shutdown, set the state to DEAd.
See Also
TM_MIB(5)
1694
WARN: Alternate site for group is not currently active
Description
A TMIB request was received to deactivate a server for migration to the backup site. The server was shutdown but the backup site is not available so the server cannot be re-activated on the backup.
Action
Issue another operation to activate the server on the backup site.
See Also
TM_MIB(5)
1695
WARN: Server not restartable, will not be migrated
Description
A TMIB request was received to deactivate a server for migration to the backup site. The server was shutdown but the server is not configured to be restartable so the server cannot be re-activated on the backup.
Action
Issue another operation to activate the server on the backup site.
See Also
TM_MIB(5)
1696
ERROR: No active machines available for activation of server group
Description
A TMIB request was received to activate a server, but the primary and backup machines for the group with which the server is associated are not active.
Action
Activate one of the associated machines before activating the application server.
See Also
TM_MIB(5)
1697
ERROR: Could not format command line options
Description
A TMIB request to activate a server failed during processing to start the server. An attempt dynamically to allocate memory from the operating system failed.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1698
ERROR: Could not format command line arguments
Description
A TMIB request to activate a server failed during processing to start the server. An attempt dynamically to allocate memory from the operating system failed.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1699
ERROR: Could not fork
Description
While activating a server, the new program could not be started (forked or spawned). This usually indicates that system resources did not exist to allow for the execution (e.g., a shortage of process table entries or swap space).
Action
Check for administrative events that might keep a program from being started (either on the console, in administrative logs, or in the OS event monitor). Re-try the operation.
See Also
TM_MIB(5)
 |
 |
 |