Juniper ADVANCED INSIGHT SCRIPTS 2.5 - RELEASE NOTES REV 1 Release Note page 13

Table 1: Events Detected by AI-Scripts (continued)
EVENT ID
CONNECTION_RTLOGD_FAIL
CONNECTION_SEND_ERROR
COSD_GENCFG_WRITE_FAILED
COSD_MALLOC_FAILED
COSD_RTSOCK_LIB_ERR
COSD_RTSOCK_WRITE_FAILED
COSD_UNEXPECTED_EXIT
COSD_UNKNOWN_TRANSLATION_TABLE
Daemon Crash
DCD_CONFIG_WRITE_FAILED
DCD_GET_ERROR
DCD_PARSE_STATE_EMERGENCY
DCD_RTSOCK_READ_SYNC_NOBUF
DCD_RTSOCK_SEND_NOBUF
DCD_TRASHED_RED_ZONE
©
Copyright 2010, Juniper Networks, Inc.
DESCRIPTION
The alarm process (alarmd) was unable to connect to the Juniper
Networks J Series Services Router (JSR) log process (rtlogd).
The alarm process (alarmd) received an error while it was trying to send a
message.
The class-of-service (CoS) process (cosd) uses GENCFG to read and
write data from the kernel. If the write fails, the kernel returns an error.
The class-of-service (CoS) process (cosd) could not dynamically allocate
memory, for the indicated reason.
The class-of-service (CoS) process (cosd) uses rtsock library for reading
and writing data from and to kernel. The specified error occurred while
using rtsock library to read/write data.
The class-of-service (CoS) process (cosd) uses rtsock to read/write data
from kernel. If the write fails kernel returns an error.
The class-of-service (CoS) process (cosd) waits for the event notifications
and processes the events that it is registered for. There was an error
during event-handling initialization.
The class-of-service (CoS) process (cosd) did not recognize the indicated
translation table type from the rtsock library.
A Junos daemon crash occurred with a core dump.
The interface process (dcd) encountered an error while trying to send an
interface configuration to the kernel over the routing socket.
The interface process (dcd) encountered an error while trying to load the
kernel interface configuration over the routing socket.
The interface process (dcd) encountered an unhandled internal state
during interface parsing.
The interface process (dcd) communicates with the kernel by writing
messages to and reading messages from routing sockets. The DCD could
not allocate memory to use to read messages from the kernel.
If the Routing Engine is busy or operating under a heavy load, messages
between the interface process (dcd) and the kernel may be dropped. To
detect whether messages have been dropped, dcd and the kernel place
sequence numbers in messages. dcd detected that a message was
dropped. In an attempt to recover the message, dcd retries the operation.
When DCD is allocating heap memory, it uses a private memory allocator
that writes a special pattern at the end of each allocated segment of heap
memory. Later, when de-allocating this memory, DCD checks for the
pattern. Not finding the previously written pattern means the memory was
overwritten, which indicates an error in DCD.
Events Detected by AI-Scripts
13