CMDTUX Messages 1800-1899
|
|
|
1800
WARN: Server RESTART set to Y and MAXGEN set < 2 on server entry servername
Description
A server entry for servername is configured with the RESTART option but the MAXGEN is set to or defaults to a value less than 2 so that the server will never be restarted.
Action
No action is required. Normally, the MAXGEN value should be set higher so that the server will restart.
See Also
ubbconfig(5)
1801
WARN: Error while parsing filename.
Description
buildserver(1) was parsing the given filename. While parsing the file given via the "-s @filename" option, buildserver encountered a syntax error.
Action
Edit the file specified by the "-s @filename" option. Make sure that each line is a valid argument to the -s option. The file may be commented if the first character of the comment line is "#". Blank lines are also acceptable.
1802
ERROR: Error adding element to heap.
Description
buildserver(1) uses a heap sort algorithm to order the function names. If buildserver(1) was unable to add an element to the heap, then this error will be returned.
Action
If this error occurs consistently, contact BEA TUXEDO system Technical Support.
1803
ERROR: Unable to parse -s option.
Description
While buildserver(1) was parsing the -s option, an error occurred. This error could range anywhere from a syntax error to a file input/output error.
Action
Make sure the -s option has the proper syntax. Also make sure that any file specified with the "-s @filename" option exists and has the proper format.
1804
ERROR: Unable to build function table.
Description
buildserver(1) uses a heap sort in order to manage function names. This error can occur in the second phase of the heap sort if the actual sorted table could not be built.
Action
If this error occurs consistently, contact the
BEA TUXEDO system Technical Support.
1805
WARN: Could not open file filename.
Description
The file specified to buildserver(1) via the "-s @filename" option does not exist.
Action
Make sure that the given filename exists. One useful trick is to specify filename as a full path name, rather than a relative path name.
1806
WARN: File recursion is not supported.
Description
The "-s @filename" option can be used on the command line to buildserver(1). However, the arguments within the file specified by filename cannot specify another file to open and parse. This practice is known as file recursion. File recursion is not supported by buildserver(1).
Action
Remove any lines from filename which begin with the @ character.
1812
WARN: Could not read filetype file filename on LMID
Description
While booting the system or updating the MIB, a security file could not be read on the specified machine. Normally, this will occur when security is configured but one or more of the security files have not been populated (for example, SECURITY is set to USER_AUTH but the group and ACL information is not set).
Action
No action is needed if the associated information is not required for the application.
See Also
ubbconfig(5)
1813
ERROR: Could not encrypt filetype file for propagation to LMID
Description
While booting the system or updating the MIB, a directory needed to hold the security file could not be created.
Action
Verify that the $APPDIR directory exists and has directory permissions that will allow the administrator to create a subdirectory there. Verify that the file system containing $APPDIR has free disk blocks and inodes.
See Also
tmboot (1)
1814
ERROR: Could not propagate filetype file to LMID: Failed to make directory
Description
While booting the system or updating the MIB, a directory needed to hold the file could not be created.
Action
Verify that the $APPDIR directory exists and that directory permissions will allow the administrator to create a subdirectory there. Verify that the file system containing $APPDIR has free disk blocks and inodes.
See Also
tmboot (1)
1815
ERROR: Could not propagate filetype file to LMID: Invalid file type for directory
Description
While booting the system or updating the MIB, a directory needed to hold the file could not be created because a file exists with the same path name.
Action
Remove the file.adm or adm and retry the command.
1816
ERROR: Could not propagate filetype file to LMID: Cannot change mode of directory
Description
While booting the system or updating the MIB, the permissions of a directory needed to hold the file could not be changed.
Action
Change ownership of the adm or .adm directory to the administrative UID.
See Also
ubbconfig(5) MACHINES section
1817
ERROR: Could not propagate filetype file to LMID: Cannot open file
Description
While booting the system or updating the MIB, a security file could not be opened for reading or writing.
Action
Verify that the file system containing $APPDIR has free disk blocks and inodes.
1818
ERROR: Could not propagate filetype file to LMID: Cannot write to file
Description
While booting the system or updating the MIB, a write failed on a security file being propagated to the specified LMID.
Action
Verify that the file system containing $APPDIR has free disk blocks and inodes.
See Also
ubbconfig(5) MACHINES section
1819
ERROR: Could not propagate filetype file to LMID: Error decrypting the file
Description
While booting the system or updating the MIB, there was an encryption problem when propagating one of the security files.
Action
Contact your BEA TUXEDO system Technical Support.
1820
ERROR: Could not propagate filetype file to LMID: Unknown error
Description
While booting the system or updating the MIB, there was an unrecognized return code encountered.
Action
Contact your BEA TUXEDO system Technical Support.
1821
ERROR: MAXACLGROUPS parameter must be > 0 and <= 16384
Description
The MAXACLGROUPS parameter in the RESOURCES section must be greater than 0 and less than 16K. It specifies the maximum number of group identifiers that can be used for ACL permissions checking.
Action
Correct the value of MAXACLGROUPS and re-run tmloadcf(1).
See Also
tmloadcf (1)
1824
ERROR: MAXACLCACHE parameter must be >= 10 and <= 32000
Description
The MAXACLCACHE parameter in the MACHINES section must be greater than or equal to 10 and less than 32000. It specifies the number of entries in the cache used for ACL entries when SECURITY is set to ACL or MANDATORY_ACL.
Action
Correct the value of MAXACLCACHE and re-run tmloadcf(1).
See Also
tmloadcf (1)
1825
ERROR: Current work directory path name is too long
Description
While executing tmloadcf, an attempt to get the current working directory path failed. This can indicate that either the directory pathname is greater than 78 characters in length or that the directory hierarchy is not readable.
Action
Check that the directory hierarchy has the proper permissions and is no longer than 78 characters, and re-execute the command.
1827
ERROR: Absolute path name of the input file is too long
Description
The length of the absolute path name of the input file is greater than MAXTLSTRING.
Action
Specify a shorter path name.
1828
ERROR: Security level must be USER_AUTH, ACL or MANDATORY_ACL.
Description
In order to run tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1), the security level of the BEA TUXEDO application must be USER_AUTH, ACL, or MANDATORY_ACL.
Action
Change the security level in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig(5) file. Then re-run the command that caused this failure.
1829
ERROR: Security level must be USER_AUTH, ACL or MANDATORY_ACL.
Description
In order to run tpusradd(1), tpusrmod(1), or tpusrdel(1), the security level of the BEA TUXEDO application must be USER_AUTH, ACL, or MANDATORY_ACL.
Action
Change the security level in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig(5) file. Then re-run the command that caused this failure.
1830
ERROR: client name is invalid.
Description
The client name given to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. A client name must not contain the characters ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Action
Change the name given to the command in order to comply with the specifications.
1831
ERROR: new user name is not valid.
Description
The new user name given to tpaclmod(1) or tpacldel(1) was invalid. A user name must not contain the characters '#', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Action
Change the name given to the command in order to comply with the specifications.
1832
ERROR: can't execute command
Description
An error occurred while compiling a server with the buildserver command. The message prints the exact compilation command.
Action
Check the command that it is valid (e.g., files exist and have the correct permissions). Check the errors generated by the compiler and correct them.
See Also
buildserver(1)
1833
ERROR: Group numbers must be between 0 and max.
Description
Group identifiers must be between 0 and 16383. tpgrpadd(1) or tpgrpmod(1) was presented a group number which is not within these boundaries.
Action
Change the group number to be within the proper boundaries. Re-run the command that caused the error.
1834
ERROR: Group numbers must be between 0 and max.
Description
Group identifiers must be between 0 and 16383. tpusradd(1) or tpusrmod(1) was presented a group number which is not within these boundaries.
Action
Change the group number to be within the proper boundaries. Re-run the command that caused the error.
1835
ERROR: Group name is invalid.
Description
The group name given to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. A group name must not contain the characters '#', ',', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Action
Change the name given to the command in order to comply with the specifications.
1836
WARN: Server(pid) processing terminated with SIGKILL 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 using 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
1837
WARN: Server(pid) processing terminated with SIGTERM after SVCTIMEOUT
Description
The BBL has terminated the local server with process id pid using the kill(2) system call to generate a SIGTERM signal because the server exceeded the maximum service processing time for the current service as configured using the SVCTIMEOUT parameter in the *SERVICES section of the ubbconfig(5) file.
The TM_SVCTIMEOUT_SIGTERM environment variable was also set in the BBL environment, which caused a SIGTERM signal to be sent instead of a SIGKILL.
If the SIGTERM signal does not cause the misbehaving server to terminate, a subsequent SIGKILL signal is sent.
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
1838
ERROR: .SysServiceTimeout: queue, group group, id srvid server sent SIGTERM due to a service time-out
Description
The BBL has sent SIGTERM to a server due to a service time-out. The server is described by its queue, group and srvid.
Action
The administrator may need to configure the service time-out higher in order to accommodate a heavily loaded system.
(The service time-out is specified using the SVCITMEOUT parameter in the *SERVICES section of the ubbconfig(5) file.)
If immediate SIGKILL signal is needed instead of a SIGTERM signal, then the TM_SVCTIMEOUT_SIGTERM environment variable should be unset in the environment of the BBL.
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), ubbconfig(5)
1850
INFO: TM_RESTARTSRVTIMEOUT is set to secs seconds
Description
The restartsrv process has recognized the numeric value of the TM_RESTARTSRVTIMEOUT environment variable setting, and has established the indicated timeout time for restarted servers.
Action
If the indicated timeout time is incorrect, change the value of the TM_RESTARTSRVTIMEOUT environment variable and restart the application.
1851
INFO: TM_BOOTTIMEOUT is set to secs seconds
Description
The tmboot process has recognized the numeric value of the TM_BOOTTIMEOUT environment variable setting, and has established the indicated timeout time for started servers.
Action
If the indicated timeout time is incorrect, change the value of the TM_BOOTTIMEOUT environment variable and restart the application.
See Also
tmboot(1)
1852
INFO: TM_BOOTTIMEOUT is set to secs seconds
Description
The tlisten process has recognized the numeric value of the TM_BOOTTIMEOUT environment variable setting, and has established the indicated timeout time for started servers.
Action
If the indicated timeout time is incorrect, change the value of the TM_BOOTTIMEOUT environment variable and restart the application.
1853
INFO: TM_SHUTDOWNTIMEOUT is set to secs seconds
Description
The tmshutdown process has recognized the numeric value of the TM_SHUTDOWNTIMEOUT environment variable setting, and has established the indicated timeout time for servers being shut down.
Action
If the indicated timeout time is incorrect, change the value of the TM_SHUTDOWNTIMEOUT environment variable and restart the tmshutdown.
See Also
tmshutdown(1)
1854
INFO: TM_BOOTTIMEOUTKILL option is selected
Description
The tmboot process has recognized the TM_BOOTTIMEOUTKILL environment variable setting.
Action
If this option was not intended, unset the TM_BOOTTIMEOUTKILL environment variable and restart the tmboot.
1855
INFO: TM_BOOTPRESUMEDFAIL option is selected
Description
The tmboot process has recognized the TM_BOOTPRESUMEDFAIL environment variable setting.
Action
If this option was not intended, unset the TM_BOOTPRESUMEDFAIL environment variable and restart the tmboot.
1856
INFO: TM_RESTARTSRVTIMEOUTKILL option is selected
Description
The restartsrv process has recognized the TM_RESTARTSRVTIMEOUTKILL environment variable setting.
Action
If this option was not intended, unset the TM_RESTARTSRVTIMEOUTKILL environment variable and restart the application.
1857
WARN: Server process ID pid on site lmid failed to shut down within secs seconds
Description
tmshutdown has not received a response from the indicated process after sending it a shutdown command. tmshutdown will no longer wait for a reply from this server, and will process the next server to be shutdown, if any.
Action
Investigate the reason for the failure of the server to respond. If necessary, use the -w or -k options to shutdown the server.
See Also
tmshutdown(1)
1858
ERROR: Server process ID pid on site lmid failed to initialize within TM_BOOTTIMEOUT seconds
Description
tmboot has detected that a started server has taken longer than secs seconds to complete initialization. The tmboot process will no longer wait for the started server to report that initialization is complete, and will start the next server to be booted, if any.
Action
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function.
1859
ERROR: Server process ID pid failed to initialize within secs seconds
Description
tmboot has detected that a started server has taken longer than secs seconds to complete initialization. The tmboot process will no longer wait for the started server to report that initialization is complete, and will start the next server to be booted, if any.
Action
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function.
1860
ERROR: On restart, server process ID pid failed to initialize within secs seconds
Description
The restartsrv process has detected that a restarted server has taken longer than secs seconds to complete initialization. The restartsrv process will no longer wait for the restarted server to report that initialization is complete, and will restart the next server in need of restarting, if any.
Action
Investigate the failure of the server to restart. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function.
1861
ERROR: Server process ID pid failed to initialize within secs seconds
Description
The tlisten process has detected that a started server has taken longer than secs seconds to complete initialization. The tlisten process will no longer wait for the started server to report that initialization is complete, and will start the next server to be booted, if any.
Action
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function.
See Also
tlisten(1)
1862
INFO: Process ID=pid Assume started (timeout).
Description
tmboot has detected that a started server has taken longer than the configured TM_BOOTTIMEOUT to complete initialization. The tmboot process will no longer wait for the started server to report that initialization is complete, and will start the next server to be booted, if any.
Action
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function.
1863
INFO: Process ID=pid Assume failed (timeout).
Description
tmboot has detected that a started server has taken longer than the configured TM_BOOTTIMEOUT to complete initialization. The tmboot process will no longer wait for the started server to report that initialization is complete, and will run the "-e failcmd" command, if provided.
Action
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function.
1864
INFO: Process ID=pid Assume failed (pipe).
Description
While booting BEA TUXEDO system processes or servers, tmboot received an interrupt, and is not aware of the process status. Because the TM_BOOTPRESUMEDFAIL option is selected, tmboot will run the "-e failcmd" command, if provided.
Action
Investigate the failure of the server to report completion of initialization.
1865
WARN: Process ID=pid Assume failed (network).
Description
While booting BEA TUXEDO system processes or servers, tmboot did not receive the status from a network call. The system issues this message to point out that it is not aware of the process status. The tmboot process will run the "-e failcmd" command, if provided.
Action
Investigate the failure of the server to report completion of initialization. There may be a problem with the network.
1866
ERROR: Attempt to send SIGKILL to site lmid process ID pid failed (errno=errno_val, tperrno=tperrno_val)
Description
tmboot was unable to send a SIGKILL to a server of the given site lmid and pid. The value of tperrno_val may provide further information on the source of the failure.
Action
No action necessary.
1867
INFO: SIGKILL delivered to site lmid process ID pid
Description
tmboot was successful in sending a SIGKILL to a server of the given site lmid and pid.
Action
No action necessary.
1868
ERROR: Attempt to send SIGKILL to process ID pid failed (reason)
Description
restartsrv was unable to send a SIGKILL to a server of the given pid. The reason may provide further information on the source of the failure.
Action
No action necessary.
1869
INFO: SIGKILL delivered to process ID pid
Description
restartsrv was successful in sending a SIGKILL to a server of the given pid.
Action
No action necessary.
1870
ERROR: The TM_RESTARTSRVTIMEOUT value (string) is non-numeric or outside the valid range
Description
The restartsrv process has recognized that the TM_RESTARTSRVTIMEOUT environment variable is set, but the specified string contains non-numeric characters, or is outside the valid range 0..65535.
Action
If the indicated timeout time is incorrect, change the value of the TM_RESTARTSRVTIMEOUT environment variable and restart the application.
1871
ERROR: The TM_BOOTTIMEOUT value (string) is non-numeric or outside the valid range
Description
The tmboot process has recognized that the TM_BOOTTIMEOUT environment variable is set, but the specified string contains non-numeric characters, or is outside the valid range 0..65535.
Action
Change the value of the TM_BOOTTIMEOUT environment variable and run tmboot again.
1872
ERROR: The TM_BOOTTIMEOUT value (string) is non-numeric or outside the valid range
Description
The tlisten process has recognized that the TM_BOOTTIMEOUT environment variable is set, but the specified string contains non-numeric characters, or is outside the valid range 0..65535.
Action
Change the value of the TM_BOOTTIMEOUT environment variable and start the tlisten process again.
See Also
tlisten(1)
1873
ERROR: The TM_SHUTDOWNTIMEOUT value (string) is non-numeric or outside the valid range
Description
The tmshutdown process has recognized that the TM_SHUTDOWNTIMEOUT environment variable is set, but the specified string contains non-numeric characters, or is outside the valid range 0..65535.
Action
Change the value of the TM_SHUTDOWNTIMEOUT environment variable and run tmshutdown again.
See Also
tmshutdown(1)
 |
 |
 |