During the booting of servers,
memory could not be allocated for an internal
structure.
Remove processes that may be tying up physical memory, ensure
that the application IPC key is correct, or verify that the UNIX
sysgen
process sizing parameters are correct.
During the booting of servers,
memory could not be allocated for an internal
structure.
Remove processes that may be tying up physical memory, ensure
that the application IPC key is correct, or verify that the UNIX
sysgen
process sizing parameters are correct.
During the
tmboot
process, the *GROUPS section of the configuration file could not be
read.
Verify that the environment variable
TUXCONFIG
is set correctly and exported, or that
TUXCONFIG
is not corrupted (try a
tmunloadcf ),
or
TUXCONFIG
was propagated to
all machines in the configuration.
tmboot (1),
tmunloadcf (1)
During the
tmboot
process, the SERVERS section of the configuration file could not
be read.
Verify that the environment variable
TUXCONFIG
is set correctly and exported.
Make sure the
TUXCONFIG
file is not corrupted (try a
tmunloadcf ).
Verify that the
TUXCONFIG
file was propagated to
all machines in the configuration.
tmboot (1),
tmunloadcf (1)
During the
tmboot
process, the server specification used an illegal
lmid
and consequently the server
a.out
was not started.
Verify that the correct
lmid
is used in the configuration file and reload the configuration
once the server entry has been corrected.
tmboot (1),
tmloadcf (1),
ubbconfig (5)
During the
tmboot
process, the command line options for a server to be booted is
generated. An error has occurred in forming this string. The
problem associated with this error is probably not caused by
something the user has done.
Contact your TUXEDO System Technical Support.
During the
tmboot
process, the command line options for a server to be booted are
generated. The resultant command line options string is longer that
256 characters and cannot be processed.
Reduce the number of arguments or the length of parameters set,
such as path names, wherever possible. Note that internal options
may be added to the command line. Therefore, even if the command
line options specified by the user have fewer than 256 characters,
this error may occur.
tmboot (1)
During the
tmboot
process, the specified servers are booted. The machine section
of the
TUXCONFIG
file is read and an error has occurred in retrieving
this information.
The problem associated with this error is probably not caused by
something the user has done.
Contact your TUXEDO System Technical Support.
During the
tmboot
process, the specified servers are booted. The machine section
of the
TUXCONFIG
file is read and an error has occurred in retrieving
this information. The
problem associated with this error is probably not caused by
something the user has done.
Contact your TUXEDO System Technical Support.
During the
tmboot
process, the
TUXCONFIG
file was not successfully
propagated to the remote machine. This error may occur in a variety
of ways.
The network listener process
tlisten
may not be reached. This could be due to a mismatch of the
network listener address in the
UBBCONFIG
file (the
NLSADDR
value)
and the actual address that the tlisten process is using.
If the
TAGENT
on a remote node encounters an error
while trying to process the configuration file.
Verify the network listener address in the
TUXCONFIG
and the address
used for the
tlisten
process.
Examine the userlog for further error messages from the
TAGENT
process.
tlisten (1),
tmboot (1),
ubbconfig (5)
tmboot
was unable to
fork()
a child process in order to start a TUXEDO System process.
The system resources are being used intensively. Try the boot
command again. If this situation persists, contact your
UNIX system administrator.
tmboot (1)
While starting a TUXEDO System or server process, the executable file
was not found.
For a TUXEDO System process, make sure that the
TUXDIR
value of the
lmid
is set properly. The executables should be found in
${TUXDIR}/bin.
For a server process, check the value of
APPDIR
for that
lmid.
Make sure that the server executable file is located in that
directory.
tmboot (1),
ubbconfig (5)
While trying to contact a remote site to start TUXEDO System processes
or servers, a network error has occurred. Check the userlog to find
out specific details of the failure.
The boot command may be tried again. If the error persists, contact
your network administrator.
tmboot (1)
While booting 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.
No action is necessary, however, it is useful to note the status of
system processes during this scenario.
tmboot (1)
While booting TUXEDO System processes,
tmboot
receives an interrupt and the system issues this message to point out
that it is not aware of
the process status.
Even though the
boot
process is interrupted (and
perhaps aborted by the administrator), the local TUXEDO System process
currently being started may succeed or fail.
No action is necessary, however, it is useful to note the status of
system processes during this scenario.
tmboot (1)
A
boot
command has been issued for a server that is already running.
This message is issued to inform the administrator that a redundant
boot
command has been issued.
No action is necessary.
While starting a server process, the
BBL
was not available; the server
cannot join the application without this system process. All
outstanding requests to boot servers will be ignored.
Make sure that the
BBL
is running on the site that failed, and reissue
the
boot
command that originally failed.
tmboot (1)
While starting a server process on the master site, the
DBBL
was not
available; the server cannot join the application without this system
process. All outstanding requests to boot servers will be ignored.
Make sure that the
DBBL
is running on the master site, and reissue
the
boot
command that originally failed.
tmboot (1)
This message prints out a TUXEDO System /T error that has occurred in the process
a.out
while booting on the machine
lmid.
Check the userlog for messages from the
a.out
process to further determine what failure has occurred.
tmboot (1)
This message prints out a TUXEDO System/T error number that has occurred in the
process
a.out
while booting on the machine
lmid.
Check userlog messages for the
a.out
process to further determine what failure has occurred.
tmboot (1)
A fatal error has occurred and the user error handler is invoked.
Check previous userlog messages to further determine what
failure has occurred.
tmboot (1)
The system, in trying to initiate the user error handler, could not
fork a new process (the
fork()
system call returns -1).
This error is directly related to system resources (too many
processes, lack of swap space, etc). Consult your UNIX system
administrator for appropriate actions.
The user has specified a command
error_cmd
to be executed if any process fails
to boot (via the -e option). The system, in trying to initiate the
user error handler, could not exec a new process (the
execl()
system call returns an
error).
The command specified should be checked.
tmboot (1)
An error has occurred while trying to read the data from the Bulletin
Board. This error could occur in a variety of situations including
not being able to open the
TUXCONFIG
file, an error in reading
information from the
TUXCONFIG
file, trying to read a
TUXCONFIG
file
from an old release, etc.
Verify that the environment variable
TUXCONFIG
is set correctly and
exported, or that the
TUXCONFIG
file is not corrupted (try a
tmunloadcf ).
Also make sure that the
TUXCONFIG
file was propagated to
all machines in the configuration. Check the userlog for additional
details on this failure.
tmboot (1),
tmunloadcf (1)
During the
tmboot
process, the *MACHINES section of the configuration
file could not be read.
Verify that the environment variable
TUXCONFIG
is set correctly and
exported, or that the
TUXCONFIG
file is not corrupted (try a
tmunloadcf ),
or the
TUXCONFIG
file was propagated to all machines in the configuration.
tmboot (1),
tmunloadcf (1)
During the
tmboot
process, the *GROUPS section of the configuration
file could not be read.
Verify that the environment variable
TUXCONFIG
is set correctly and
exported, or that the
TUXCONFIG
file is not corrupted (try a
tmunloadcf ),
or the
TUXCONFIG
file was propagated to all machines in
the configuration.
tmboot (1),
tmunloadcf (1)
An attempt dynamically to allocate memory from the operating system
using
malloc()
failed while setting up an entry for the
IPC
sizing
information requested.
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.
tmboot (1)
During the tmboot process, the SERVERS section of the configuration
file could not be read.
Verify that the environment variable
TUXCONFIG
is set correctly and
exported, or that the
TUXCONFIG
file is not corrupted (try a
tmunloadcf ),
or the
TUXCONFIG
file was propagated to all machines in
the configuration.
tmboot (1),
tmunloadcf (1)
An attempt dynamically to allocate memory from the operating system
using
malloc()
failed while setting up an entry for the IPC sizing
information requested.
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.
tmboot (1)
An attempt dynamically to allocate memory from the operating system
using
malloc()
failed while setting up an entry for system processes
to be started.
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.
tmboot (1)
An attempt dynamically to allocate memory from the operating system
using
malloc()
failed while setting up an entry for system processes
to be started.
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.
tmboot (1)
The ctype of this entry in the
TODO
list is not
CT_MCHID
as expected.
Contact your TUXEDO System Technical Support.
An attempt dynamically to allocate memory from the operating system
using
malloc()
failed while setting up a list of message queues
to be created.
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.
tmboot (1)
The
802 ERROR: Cannot start servers, memory allocation failure
DESCRIPTION
ACTION
803 ERROR: Cannot start servers, memory allocation failure
DESCRIPTION
ACTION
804 ERROR: Cannot start TMS servers, error reading *GROUP section
DESCRIPTION
ACTION
SEE ALSO
805 ERROR: Cannot start servers, error reading *SERVERS section
DESCRIPTION
ACTION
SEE ALSO
808 ERROR: Skipping aout=a.out, LOC=lmid - illegal LMID specification.
DESCRIPTION
ACTION
SEE ALSO
809 ERROR: Argument vector formation error
DESCRIPTION
ACTION
810 ERROR: Aout=a.out - too many arguments
DESCRIPTION
ACTION
SEE ALSO
812 ERROR: Illegal machine id value
DESCRIPTION
ACTION
813 ERROR: Illegal machine id value, mid, for a.out
DESCRIPTION
ACTION
814 ERROR: Cannot propagate TUXCONFIG file
DESCRIPTION
ACTION
SEE ALSO
815 ERROR: Cannot fork
DESCRIPTION
ACTION
SEE ALSO
816 ERROR: Cannot exec, executable file not found
DESCRIPTION
ACTION
SEE ALSO
817 ERROR: Cannot exec, network send error
DESCRIPTION
ACTION
SEE ALSO
818 WARN: Process id=pid... Assume started (network).
DESCRIPTION
ACTION
SEE ALSO
819 INFO: Process id=pid... Assume started (pipe).
DESCRIPTION
ACTION
SEE ALSO
821 INFO: Duplicate server.
DESCRIPTION
ACTION
822 ERROR: No BBL available, cannot boot
DESCRIPTION
ACTION
SEE ALSO
823 ERROR: No DBBL available, cannot boot
DESCRIPTION
ACTION
SEE ALSO
825 ERROR: Process a.out at lmid failed with /T tperrno (tperrno_val)
DESCRIPTION
ACTION
SEE ALSO
826 ERROR: Process a.out at lmid failed with code error_code
DESCRIPTION
ACTION
SEE ALSO
827 ERROR: Fatal error encountered; initiating user error handler
DESCRIPTION
ACTION
SEE ALSO
828 ERROR: Cannot create error process - fork() failed
DESCRIPTION
ACTION
829 ERROR: Error executing `error_cmd' - error
DESCRIPTION
ACTION
SEE ALSO
830 ERROR: Could not get BB parameters
DESCRIPTION
ACTION
SEE ALSO
835 ERROR: Could not read *MACHINES section
DESCRIPTION
ACTION
SEE ALSO
840 ERROR: Could not read *GROUPS section
DESCRIPTION
ACTION
SEE ALSO
841 ERROR: Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
842 ERROR: Could not read *SERVERS section
DESCRIPTION
ACTION
SEE ALSO
843 ERROR: Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
844 ERROR: Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
845 ERROR: Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
846 ERROR: Illegal ctype
DESCRIPTION
ACTION
847 ERROR: Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
848 ERROR: Machine id mismatch for GROUP set group_number
DESCRIPTION