 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the LIBJNX prefix. They are generated by processes that call routines in the libjuniper library, which includes routines for creating and managing child processes, parsing machine and interface addresses, tracing, file I/O, and other functions.
function-name: error-message
A JUNOS process could not notify the audit process (auditd) about user activity related to system accounting, because of an interprocess communication (IPC) error.
Error: An error occurred
error
Possible reasons include (a) auditd was not running (b) auditd was still initializing after a restart (c) there was a socket error.
Contact your technical support representative.
Unable to compress file 'filename' using program-name: error-message
A JUNOS process tried to use the indicated utility to create a compressed version of the indicated old system log file. The attempt failed for the indicated reason.
Error: An error occurred
info
An internal software failure occurred.
Contact your technical support representative.
Unable to retrieve system default IP address: not set in kernel (error-message)
A JUNOS process could not retrieve the system default IP address from the kernel, because the address is not defined there.
Error: An error occurred
critical
An internal software failure occurred.
Contact your technical support representative.
function-name: error-message
A JUNOS process called the indicated function in the event library. The function failed for the indicated reason.
Error: An error occurred
emergency
An internal software failure occurred.
Contact your technical support representative.
Command stopped: PID pid, signal='return-value'core-dump-status, command 'command'
A JUNOS process created a child process to execute the indicated command for it. The child process stopped unexpectedly.
Error: An error occurred
notice
An internal software failure occurred.
Contact your technical support representative.
Child exec failed for command 'command': error-message
A JUNOS process called the exec() system call while creating a child process to execute the indicated command for it. The system call failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to create pipes for command 'command': error-message
A JUNOS process created a child process to execute the indicated command for it. Its attempt to create pipes for communication with the child failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Command received signal: PID pid, signal signal-namecore-dump-status, command 'command'
A JUNOS process created a child process to execute the indicated command for it. The child process received the indicated signal and exited.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Command exited: PID pid, status return-valuecore-dump-status, command 'command'
A JUNOS process created a child process to execute the indicated command for it. The child process exited abnormally with the indicated exit code.
Error: An error occurred
notice
An internal software failure occurred.
Contact your technical support representative.
Failed to copy from source-filename to destination-filename
A JUNOS process could not copy the indicated source file to the indicated destination name or location.
Error: An error occurred
error
pathname: error-message
A JUNOS process could not obtain status information for the indicated file system.
Event: This message reports an event, not an error
error
Not enough space left on device pathname
A JUNOS process found that the indicated file system did not have the free space needed for storing temporary files.
Event: This message reports an event, not an error
warning
function-name: invalid chassis ID chassis-id
A JUNOS process could not determine the hostname for the master Routing Engine on a routing node in a routing matrix, because the indicated chassis ID provided for the routing platform was invalid.
Error: An error occurred
error
function-name: invalid Routing Engine slot ID routing-engine-slot
A JUNOS process could not determine the hostname for a Routing Engine, because the indicated Routing Engine slot ID was invalid.
Error: An error occurred
error
Invalid XML data '\\data'
The XML parser closed its session with a client application because the indicated XML data sent by the client was invalid.
Error: An error occurred
error
Unable to lower privilege level: error-message
A JUNOS process attempted to revert its effective user ID to the original user. The attempt failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to raise privilege level: error-message
A JUNOS process attempted to set its effective user ID to the root user. The attempt failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
operation: operational-status
The rcp command failed during replication.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
rcp failed: error-message
A JUNOS process created a child process to copy a file to the other Routing Engine. The copy operation failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
function-name: operation: operation filename: error-message
A JUNOS process could not perform the indicated operation on the indicated SNMP engine data file.
Error: An error occurred
critical
An internal software failure occurred.
Contact your technical support representative.
operation: error-message
Various system processes use Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Reliable Data Protocol (RDP) sockets. The indicated socket operation failed for the indicated reason.
Error: An error occurred
emergency
An internal software failure occurred.
Contact your technical support representative.
Invalid XML encoding 'data', skipping to ';'
The XML parser ignored the indicated XML data sent by a client application, because the XML encoding of the data was invalid. The parser skipped ahead to the likely endpoint for the invalid data.
Error: An error occurred
error
A possible cause is improper escaping of character constants in the data stream.
Contact your technical support representative.
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |