CMDTUX Messages 1500-1599
|
|
1502
ERROR: Cannot open 'tuxconfig' file
Description
tmipcrm was unable to get information on the RESOURCES section
of 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.
1503
ERROR: Execute permission denied, not application administrator
Description
tmipcrm must be run by the TUXEDO system administrator, as defined
in the RESOURCES section of the TUXCONFIG file.
Action
Re-run the command as the proper user.
1504
ERROR: Cannot attach to the BB!
Description
tmipcrm failed to join the TUXEDO application.
This can occur if more than one tmipcrm
program is run at the same time.
It can also occur for a number of run-time reasons.
Action
Retry the desired operation; if the problem persists, contact BEA Customer Support.
1507
ERROR: shmat to shmid failed!
Description
tmipcrm failed to attach to a shared memory segment
associated with the application,
with the specified identifier, shmid.
Action
Check if the specified segment still exists using ipcs(1).
If it does, retry the desired operation.
If the problem persists,
contact BEA Customer Support.
1573
ERROR: Illegal arguments for send to TAGENT on machine
Description
When sending a message to a remote tagent, invalid arguments were passed to the internal function.
Action
Contact BEA Customer Support.
1574
ERROR: Memory allocation error for TAGENT on machine
Description
While sending a message to a remote tagent (on machine) an attempt dynamically to allocate memory using malloc() failed.
Action
Ensure that 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.
See Also
malloc(3) in UNIX reference manuals
1575
ERROR: Memory allocation error for TAGENT on machine
Description
While sending a message to a remote tagent (on machine), an attempt dynamically to allocate memory using malloc() failed.
Action
Ensure that 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.
See Also
malloc(3) in UNIX reference manuals
1576
ERROR: No NLS available for remote machine machine
Description
When sending a message to a remote tagent, the program was unable to contact the tlisten process on the remote machine.
Action
Start the tlisten process on the remote machine using the proper NLSADDR value that was specified in the TUXCONFIG file. Check that the networking is available from the local to remote machine.
See Also
tlisten(1)
1577
ERROR: Could not open device device_name for contacting NLS on machine
Description
When sending a message to a tagent on a remote machine, the connection failed because the program could not open the specified device, device_name. The device name is taken from the BRIDGE parameter in the TUXCONFIG file for the local machine.
Action
Check that the correct BRIDGE value is specified for the network device for connections between the local machine and the remote machine. Also check that the operating system parameters are set correctly for networking.
1578
ERROR: Could not contact NLS on machine
Description
When sending a message to a remote tagent, the program was unable to contact the tlisten process on the remote machine.
Action
Start the tlisten process on the remote machine using the proper NLSADDR value that was specified in the TUXCONFIG file. Check that the networking is available from the local machine to the remote machine.
See Also
tlisten(1)
1579
ERROR: Network error contacting NLS on machine
Description
When sending a message to a remote tagent, the program was unable to contact the tlisten process on the remote machine because of a networking error.
Action
Check that the networking is available from the local machine to the remote machine.
See Also
tlisten(1)
1580
ERROR: NLS request message for machine not interpretable
Description
When sending a message to a tagent on a remote machine, the program was unable to interpret the message.
Action
Contact BEA Customer Support.
1581
ERROR: NLS request service code code_val unknown on machine
Description
When sending a message to a tagent on a remote machine, the requested NLS service was not recognized.
Action
If the specified service is CHECKALIVE, then a later release is contacting an earlier release of the tlisten process and this message can be ignored. Otherwise, contact BEA Customer Support.
See Also
tlisten(1)
1582
ERROR: Service code code_val currently disabled on machine
Description
When sending a message to a tagent on a remote machine, the requested NLS service was available.
Action
Contact BEA Customer Support.
See Also
tlisten(1)
1583
ERROR: Unknown error during NLS request to machine
Description
When sending a message to a tagent on a remote machine, an unknown error occurred. Normally, this indicates that the remote machine became unavailable after the initial connection (that is, the network or machine failed).
Action
Correct the problem and execute the program again.
1584
ERROR: Unknown error during NLS request to machine
Description
When sending a message to a tagent on a remote machine, an unknown error occurred. Normally, this indicates that the remote machine became unavailable after the initial connection (that is, the network or machine failed).
Action
Correct the problem and execute the program again.
1585
ERROR: Memory allocation error encoding request for TAGENT on machine
Description
While encoding a message for a remote TAGENT on the specified machine, an attempt to dynamically allocate memory from the operating system using malloc() failed.
Action
Ensure that 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.
See Also
malloc(3) in a UNIX reference manual
1586
ERROR: Could not encode TAGENT msg for machine
Description
While encoding a message for a remote TAGENT on the specified machine, the operation failed.
Action
Contact BEA Customer Support.
1588
ERROR: Error sending to TAGENT on machine
Description
When sending a message to a tagent on a remote machine, an error occurred. Normally, this indicates that the remote machine became unavailable after the initial connection (that is, the network or machine failed).
Action
Correct the problem and execute the program again.
1590
ERROR: Unknown network error receiving reply from TAGENT on machine
Description
When receiving a message to a tagent on a remote machine, an unknown network error occurred. Normally, this indicates that the remote machine became unavailable after the initial connection (that is, the network or machine failed).
Action
Correct the problem and execute the program again.
1591
ERROR: Memory allocation error receiving reply from TAGENT on machine
Description
While receiving a reply message from a remote TAGENT on the specified machine, an attempt to dynamically allocate memory from the operating system using malloc() failed.
Action
Ensure that 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.
See Also
malloc(3) in a UNIX system reference manual
1592
ERROR: Error decoding reply from TAGENT on machine
Description
While decoding a message reply from a remote TAGENT on the specified machine, the operation failed.
Action
Contact BEA Customer Support.
1593
ERROR: Error decoding reply from TAGENT on machine
Description
While decoding a message from a remote TAGENT on the specified machine, the operation failed.
Action
Contact BEA Customer Support.
1594
ERROR: Cannot find master without BB
Description
An attempt was made to find the acting MASTER machine, that is, the machine where the DBBL is currently running, by a process that has not yet joined the application as a client or server.
Action
Contact BEA Customer Support.
1595
ERROR: Unable to register process - semctl failure; errno = err_number key = ipc_key
Description
While in the process of registering an entry in the Bulletin Board, a semaphore operation was required in order to set the process ID of the registering process in the semaphore. This semaphore operation, performed using semctl(2), failed.
Action
Contact BEA Customer Support.
1596
ERROR: Unable to get space for unregister request - errmsg
Description
The BEA TUXEDO system application was unable to allocate space to create a message to unregister with the DBBL process. The nature of the failure is indicated by errmsg.
Action
The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
See Also
tpalloc(3c)
1597
ERROR: Unable to unregister - remote procedure call failure - can't send request - errmsg
Description
The BEA TUXEDO system application was unable to unregister with the DBBL process because the remote procedure call to perform the unregister operation failed. The nature of the failure is indicated by errmsg.
Action
Check the userlog for other messages indicating the reason for the failure. The DBBL will detect that the process has gone away and clean up the entry during a later sanity check.
1598
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.
1599
ERROR: Unable to register process - semctl err - errno = errno key = ipc_key
Description
While in the process of registering the DBBL process in the Bulletin Board, a semaphore operation was required in order to set the process ID of the DBBL in the semaphore. This semaphore operation, performed using semctl(2), failed.
Action
Contact BEA Customer Support.
 |
 |
 |