An encryption algorithm error occurred while passing security key
information to a remote machine.
Contact your TUXEDO System Technical Support.
An encryption algorithm error occurred while passing security key
information to a remote machine.
Contact your TUXEDO System Technical Support.
An encryption algorithm error occurred while passing security key
information to a remote machine.
Contact your TUXEDO System Technical Support.
The
tmconfig
command was unable to obtain a value for the application password.
This value is entered at the terminal if
tmconfig
is being invoked interactively, and is gotten from the
APP_PW
environment variable if the standard input to the
tmconfig
process is not a terminal.
If the
tmconfig
command is being invoked in the background, be sure to set
and export the
APP_PW
environment variable.
If
tmconfig
is being invoked at a terminal, be sure that the user enters a
value at the
Enter
Application
Password :
prompt.
tmconfig (1)
The
NLSADDR
parameter in the *NETWORK section of the configuration file must be
specified for every machine in the network, except the
master machine.
It is recommended but not required
for the master machine.
Add
NLSADDR
information to the configuration file.
ubbconfig (5),
*NETWORK section
The
NLSADDR
parameter in the *NETWORK section of the configuration file
is recommended but not required for
the master machine.
The master machine needs an
NLSADDR
and a
tlisten
process running in order for
master migration to work.
Add
NLSADDR
information for the master machine to the configuration file.
ubbconfig (5),
*NETWORK section
While executing
tmconfig ,
the program was unable to get the field identifier for
TA_SECTION
from the field table
$TUXDIR/udataobj/tpadmin .
Make sure that the tpadmin field table exists and is readable.
Contact your TUXEDO System Technical Support.
tmconfig (1)
When executing
tmboot
or
tmshutdown
as user id 0 (root),
the program sets the group identifier to the group identifier
for the application administrator as specified in the
TUXCONFIG
file. The
setgid ()
failed.
Make sure that the
GID
value as set in the *RESOURCES or *MACHINES sections of the
UBBCONFIG
file is valid.
Contact your TUXEDO System Technical Support.
tmboot (1),
tmshutdown (1)
When executing
tmboot
or
tmshutdown
as user id 0 (root),
the program sets the user identifier to the user identifier
for the application administrator as specified in the
TUXCONFIG
file. The
setuid ()
failed.
Make sure that the
UID
value as set in the *RESOURCES or *MACHINES sections of the
UBBCONFIG
file is valid.
Contact your TUXEDO System Technical Support.
tmboot (1),
tmshutdown (1)
The
tlisten
process will print this message to the standard error output
when terminating.
The only valid exit for the
tlisten
process is when it receives a
SIGTERM
termination signal.
No action required.
tlisten (1)
While executing
tlisten ,
the -l option was specified more than once on the command line.
Re-execute the command specifying the -l option only once with
the network listening address.
tlisten (1)
While executing
tlisten ,
the -u option was specified more than once on the command line.
Re-execute the command specifying the -u option only once with
the user identifier or name for the configuration administrator.
tlisten (1)
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while
storing a list of processes to be booted or shut down in
tmboot
or
tmshutdown .
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.
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while
generating a list of servers to be booted in
tmboot .
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.
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while
generating a list of servers to be shut down in
tmshutdown .
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.
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.
If running
tmloadcf
from a script, make sure that
APP_PW
is set and exported into the environment.
Otherwise, contact your TUXEDO System Technical Support.
tmloadcf (1),
ubbconfig (5)
While
tmloadcf
is being run on the master machine, the
UID
parameter in the *RESOURCES or *MACHINES section of the
UBBCONFIG
does not match the effective user identifier of the person running the command.
Change the
UID
parameter in the *RESOURCES or *MACHINES section of the
UBBCONFIG
file or run the command under that user identifier.
tmloadcf (1)
While
tmloadcf
is being run on the master machine, the
GID
parameter in the *RESOURCES or *MACHINES section of the
UBBCONFIG
does not match the effective group identifier of the person running the command.
Change the
GID
parameter in the *RESOURCES or *MACHINES section of the
UBBCONFIG
file or run the command under that group identifier.
tmloadcf (1)
The
MAXACCESSERS
parameter in the *MACHINES section of the
UBBCONFIG
file must be greater than 0 and less than 32768.
Correct the value for
MAXACCESSERS
as specified in the *MACHINES section of the
UBBCONFIG
file to be greater than 0 and less than 32768.
tmloadcf (1),
ubbconfig (5)
The
MAXGTT
parameter in the *MACHINES section of the
UBBCONFIG
file must be greater than or equal to 0 and less than 32768.
Correct the value for
MAXGTT
as specified in the *MACHINES section of the
UBBCONFIG
file to be greater than or equal to 0 and less than 32768.
tmloadcf (1),
ubbconfig (5)
The
MAXCONV
parameter in the *MACHINES section of the
UBBCONFIG
file must be greater than zero and
less than 32768.
Correct the value for
MAXCONV
as specified in the *MACHINES section of the
UBBCONFIG
file to be greater than 0 and less than 32768.
tmloadcf (1),
ubbconfig (5)
The
PERM
parameter in the *MACHINES section of the
UBBCONFIG
file must be greater than or equal to 1 and
less than or equal to 0777.
Correct the value for
PERM
as specified in the *MACHINES section of the
UBBCONFIG
file to be greater than or equal to 1 and less than or equal to 0777.
tmloadcf (1),
ubbconfig (5)
A
TMSNAME
parameter is specified for group,
groupname,
but the primary LMID for the group,
lmid,
does not have a
TLOGDEVICE
specified in the *MACHINES section.
Either change the *GROUPS entry to not have a
TMSNAME
parameter, or change the
LMID
value for the group,
or change the *MACHINES entry to have a
TLOGDEVICE
parameter.
tmloadcf (1),
ubbconfig (5)
An attempt dynamically to allocate a typed buffer using
tpalloc ()
failed while
the
DBBL
was broadcasting a message to a
BBL
running the prior release of the software.
The message indicates the reason that
tpalloc ()
failed.
Most likely, the call was unable dynamically to allocate memory.
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.
Contact your TUXEDO System Technical Support.
While executing
tmshutdown
with the -R option, the program was unable to retrieve
the queue information for the servers.
The server will be shut down and not migrated to the alternate machine.
Contact your TUXEDO System Technical Support.
tmshutdown (1)
While executing
tmshutdown
with the -R option, the program determined that the server
is not configured to be restartable.
The server will be shut down and not migrated to the alternate machine.
If you want to be able to migrate the server between the primary
and backup machines, the *GROUPS entry with which the server
is associated must have a primary and backup
LMID
specified.
tmshutdown (1),
ubbconfig (5)
While executing
tmboot
or
tmshutdown ,
the program was unable to get the Bulletin Board parameters from
the
TUXCONFIG
configuration file.
Check that the
TUXCONFIG
environment variable is set and exported.
Check the userlog for prior messages that indicate the nature
of the failure.
tmboot (1),
tmshutdown (1)
The
BRIDGE
process has received a connection from another machine,
machine.
No action required.
The
BRIDGE
process has completed an orderly disconnect sequence
with a remote
BRIDGE .
Orderly disconnections
usually result from execution of the tmshutdown utility.
No action required.
tmshutdown (1)
and Messages 1370 and 1371 above.
The
BRIDGE
process has experienced an abnormal disconnect from a remote
BRIDGE .
There may be networking problems, or the remote
machine
may have crashed.
Check that
machine
is up.
Check network connectivity between the machines.
Check that the TUXEDO System is running on
machine.
The
BRIDGE
processes will automatically reestablish a
connection between the machines on demand, when possible.
To prevent thrashing, the link will be suspended for five minutes
if an automatic reconnect attempt fails.
No further automatic reconnection attempts are made during this interval.
If desired, use tmadmin(1)'s reconnect command to
initiate a reconnection attempt manually.
Manual attempts are allowed during the five-minute suspension interval.
tmadmin (1)'s
reconnect
command.
Also check Messages 1370, 1371, 1374, 1375, and 1376 in
this chapter.
The
BRIDGE
process successfully reconnected to the
BRIDGE
on
machine
during recovery from a networking problem.
No action required.
Message 1373 above
The
BRIDGE
process could not reconnect to
machine
during recovery from a networking problem.
Check that
machine
is up.
Check network connectivity between the machines.
Check that the TUXEDO System is running on
machine.
The
BRIDGE
processes will automatically reestablish a
connection between the machines on demand, when possible.
To prevent thrashing, the link will be suspended for five minutes
if an automatic reconnect attempt fails.
No further automatic reconnection attempts are made during this interval.
If desired, use
tmadmin (1)'s
reconnect
command to
initiate a reconnection attempt manually.
Manual attempts are allowed during the five-minute suspension interval.
Messages 1373 and 1374 above and
tmadmin (1)'s
reconnect
command
The
BRIDGE
process has suspended automatic reconnection
attempts to
machine
for five minutes.
This is to prevent thrashing caused by too many
recovery attempts.
Use
tmadmin (1)'s
reconnect
command to
initiate a reconnection attempt manually.
Manual attempts are allowed during the five-minute suspension interval.
Messages 1373, 1374, and 1375 above and
tmadmin (1)'s
reconnect
command.
The
BRIDGE
process could not deliver a message it received from
the network due to UNIX message queue blocking.
The process(es) associated with the full queue may be
identified by looking up
qaddress
in output of
tmadmin 's
printserver
command (verbose mode).
Another method of examining message queue status is the
"ipcs -aq"
command.
1300 ERROR: Could not generate security password encryption key
DESCRIPTION
ACTION
1301 ERROR: Could not generate security password encryption schedule
DESCRIPTION
ACTION
1302 ERROR: Could not encrypt application security key
DESCRIPTION
ACTION
1307 ERROR: Unable to obtain application password
DESCRIPTION
ACTION
SEE ALSO
1308 ERROR: Must specify NLSADDR parameters in NETWORK entry machine
DESCRIPTION
ACTION
SEE ALSO
1309 WARN: NLSADDR parameter not specified for NETWORK entry machine
DESCRIPTION
ACTION
SEE ALSO
1316 ERROR: Can't find the tpadmin field table in dir
DESCRIPTION
ACTION
SEE ALSO
1317 ERROR: Failed to set group id to administrator
DESCRIPTION
ACTION
SEE ALSO
1318 ERROR: Failed to set user id to administrator
DESCRIPTION
ACTION
SEE ALSO
1319 INFO: Terminating tlisten process
DESCRIPTION
ACTION
SEE ALSO
1320 ERROR: Duplicate -l option specified
DESCRIPTION
ACTION
SEE ALSO
1322 ERROR: Duplicate -u option specified
DESCRIPTION
ACTION
SEE ALSO
1326 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1327 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1328 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1329 ERROR: Error obtaining Application Password
DESCRIPTION
ACTION
SEE ALSO
1335 ERROR: UID is not effective user ID
DESCRIPTION
ACTION
SEE ALSO
1336 ERROR: GID is not effective group ID
DESCRIPTION
ACTION
SEE ALSO
1341 ERROR: MAXACCESSERS parameter must be > 0 and < 32768
DESCRIPTION
ACTION
SEE ALSO
1343 ERROR: MAXGTT parameter must be >= 0 and < 32768
DESCRIPTION
ACTION
SEE ALSO
1344 ERROR: MAXCONV parameter must be > 0 and < 32768
DESCRIPTION
ACTION
SEE ALSO
1351 ERROR: PERM parameter must be >= 1 and <= 0777
DESCRIPTION
ACTION
SEE ALSO
1352 ERROR: GROUP entry groupname has TMS specified and LMID lmid does not have TLOGDEVICE
DESCRIPTION
ACTION
SEE ALSO
1356 ERROR: tpalloc() failed - tperrno_msg
DESCRIPTION
ACTION
1358 ERROR: Cannot retrieve server information
DESCRIPTION
ACTION
SEE ALSO
1359 ERROR: Server ID id in group groupname not marked as restartable. This server will not be restarted upon migration.
DESCRIPTION
ACTION
SEE ALSO
1360 ERROR: configuration file not found
DESCRIPTION
ACTION
SEE ALSO
1371 INFO: Connection received from machine
DESCRIPTION
ACTION
1372 INFO: Orderly disconnect from machine
DESCRIPTION
ACTION
SEE ALSO
1373 ERROR: Abnormal disconnect from machine
DESCRIPTION
ACTION
SEE ALSO
1374 WARN: Reconnecting to machine
DESCRIPTION
ACTION
SEE ALSO
1375 ERROR: Unable to reconnect to machine
DESCRIPTION
ACTION
SEE ALSO
1376 WARN: Suspending communication with machine
DESCRIPTION
ACTION
SEE ALSO
1380 ERROR: Message queue blocking prevented delivery, Qaddr = qaddress
DESCRIPTION