 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the TASK prefix.
abort executable-name[pid] version version built by builder on date: error-message
The control protocol process terminated because of an internal error.
Error: An error occurred
error
Examine the messages that immediately follow this message in the system log for information about possible causes.
An internal software failure occurred.
Exiting with active tasks: task-name
After receiving multiple termination requests, the control protocol process exited without performing the indicated cleanup tasks.
Event: This message reports an event, not an error
notice
Assertion failed executable-name[pid]: file "source-filename", line line-number: "message"
The source code for this process includes internal self-consistency checks. The process terminated because a check failed, creating a diagnostic core dump for analysis by technical support personnel and noting the number of the line in the source file where the check failed.
Error: An error occurred
error
An internal software failure occurred.
Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core dump, if requested.
Soft assertion failed executable-name[pid]: file "source-filename", line line-number: "message", daemon continued running
The source code for the process includes internal self-consistency checks. A check failed but the process continued running. It created a diagnostic core dump for analysis by technical support personnel and noted the number of the line in the source file where the check failed.
Error: An error occurred
error
An internal software failure occurred.
Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core dump, if requested.
Exit executable-name[pid] version version built by builder on date, caller address
The process exited, either in response to a user request or because of a system error.
Event: This message reports an event, not an error
notice
A system resource was unavailable, an unexpected error occurred, or a user terminated the process.
Examine the messages that immediately follow this message in the system log for information about possible causes.
Unable to obtain a lock on filename, is another copy of the process running?
The process could not obtain the mutual exclusion lock that prevents more than one instance from running simultaneously. The system terminated the indicated process.
Error: An error occurred
error
Another process is running.
Use the 'show system process' command to verify that another process is running.
Unable to obtain a lock on filename, program-name[pid] is still running
The process could not obtain the mutual exclusion lock that prevents more than one instance from running simultaneously. The system terminated this instance.
Error: An error occurred
error
Another process is running.
Use the 'show system process' command to verify that another process is running.
peer peer-name timed out waiting for input
Daemon timed out waiting for management input.
Error: An error occurred
warning
Examine the messages that immediately follow this message in the system log for information about possible causes.
An internal software failure occurred.
Using size KB of memory, percentage-value percent of available
The process is using the indicated amount and percentage of Routing Engine memory, which is considered excessive.
Error: An error occurred
error
Either the process is leaking memory or the use of system resources is excessive.
Increase the amount of RAM in the Routing Engine.
function-name: excessive runtime time during action of module
The indicated submodule of this process ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The duration was noted because task accounting is enabled. The function might be implemented inefficiently.
function-name: excessive runtime (total of time in count callbacks) after action of module
Several submodules of this process ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The duration was noted because task accounting is enabled. The function might be implemented inefficiently.
function-name: excessive runtime time during action of module
Several submodules of this process ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The duration was noted because task accounting is enabled. The function might be implemented inefficiently.
function-name ran for total-time (user-time user, system-time system) doing action
A task callback within this process ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The duration was noted because task accounting is enabled. The function might be implemented inefficiently.
signal-name termination signal received
In response to the indicated termination request, the process terminated and shut down.
Event: This message reports an event, not an error
notice
Start executable-name[pid] version version built date
Process started.
Event: This message reports an event, not an error
info
reason: error-message
A system call made by this process failed.
Error: An error occurred
error
It is possible that the kernel lacked the resources to fulfill the request.
Commencing virtual chassis control daemon, version process-version, built date by builder
The process started.
Event: This message reports an event, not an error
notice
task-name terminated by SIGsignal-namecore-dump-status
While a child process was performing the indicated operation, it terminated in response to the indicated signal.
Event: This message reports an event, not an error
error
task-name stopped by SIGsignal-name
While a child process was performing the indicated operation, it stopped in response to the indicated signal.
Event: This message reports an event, not an error
error
Unable to fork task-name: error-message
This process failed to create the indicated child process.
Error: An error occurred
error
getwd: error-message
The getwd() system call failed.
Error: An error occurred
error
It is possible that the kernel lacked the resources to fulfill the request.
Reinitialization not possible
This process (VCCPD) failed to reinitialize as requested, because it was running in a state that did not allow reconfiguration.
Error: An error occurred
error
Unable to close and remove filename: error-message
This process tried to close and remove the file that records its process ID (PID), which serves to prevent multiple instances from running simultaneously. The attempt failed.
Error: An error occurred
error
flock(filename, LOCK_EX): error-message
This process issued the flock() system call on the file that records its process ID (PID), which serves to prevent multiple instances from running simultaneously. The system call failed.
Error: An error occurred
error
Unable to write filename: error-message
This process tried to write to the file that records its process ID (PID), which serves to prevent multiple instances from running simultaneously. The attempt failed.
Error: An error occurred
error
Reinitializing
This process reinitialized.
Event: This message reports an event, not an error
info
sigaction(SIGsignal-name): error-message
This process informed the kernel that it wished to ignore the indicated signal, but the kernel failed to process the request.
Error: An error occurred
error
Unable to write to trace file filename
This process could not write to the indicated trace file, and stopped attempting to do so. The next commit of the configuration database will reenable tracing.
Event: This message reports an event, not an error
error
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |