ACCT_MALLOC_FAILURE

The accounting statistics process could not allocate memory from the heap.

ASP_L2TP_NO_MEM

The Layer 2 Tunneling Protocol (L2TP) could not allocate the memory it needed to create a flow for the indicated tunnel and session.

CFMD_RTSOCK_OPEN_FAILURE

The connectivity fault management process (cfmd) could not successfully open a routing socket to the kernel, for the indicated reason.

CHASSISD_BUS_DEVICE_OPEN_FAILURE

The chassis process (chassisd) could not open the indicated bus device for the indicated reason.

CHASSISD_CLOCK_FAILURE

The chassis process (chassisd) determined that the indicated clock source failed in the indicated way.

CHASSISD_COMMAND_ACK_ERROR

The chassis process requested that the indicated component (field-replaceable unit, or FRU) confirm that it was online. The indicated error occurred when the FRU sent its response. In the normal case, the chassis process performed any additional action necessary to guarantee that the FRU came online.

CHASSISD_COMMAND_ACK_SFM_ERROR

The chassis process (chassisd) requires an acknowledgment from each Switching and Forwarding Module (SFM) before it registers a Flexible PIC Controller (FPC) as online. The acknowledgment message from the indicated SFM failed for the indicated FPC.

CHASSISD_CMB_READBACK_ERROR

The chassis process (chassisd) could not read back information from the Chassis Management Bus (CMB) about the indicated component (field-replaceable unit, or FRU).

CHASSISD_FAN_FAILURE

The indicated fan or impeller failed. The chassis process (chassisd) raised an alarm and increased the speed of the remaining fans (and impellers, if applicable) to full speed.

CHASSISD_FASIC_FTOKEN_ERROR

The chassis process (chassisd) detected an underflow or overflow error on the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_PLL_ERROR

The chassis process (chassisd) could not lock a phased-lock loop (PLL) for the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_FTOKEN_INIT_ERROR

The chassis process (chassisd) encountered an error while initializing memory at the indicated address for the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_HSL_CONFIG_ERROR

The chassis process (chassisd) could not configure high speed links (HSL) for the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_HSL_LINK_ERROR

The chassis process (chassisd) detected an error for the indicated high-speed link (HSL) for the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_INIT_ERROR

The chassis process (chassisd) detected that F chips were not yet initialized on the Control Board (CB).

CHASSISD_FASIC_INPUT_DROP

The Packet Forwarding Engine divides packets into smaller units called cells for more efficient processing. As the indicated F chip on the indicated Control Board (CB) processed data that was received from the indicated Packet Forwarding Engine on the indicated Flexible PIC Concentrator (FPC), it dropped the indicated number of cells per second.

CHASSISD_FASIC_OUTPUT_DROP

The Packet Forwarding Engine divides packets into smaller units called cells for more efficient processing. As the indicated F chip on the indicated Control Board (CB) processed data before sending it to the indicated Packet Forwarding Engine on the indicated Flexible Port Concentrator (FPC) for outgoing transmission, it dropped the indicated number of cells per second.

CHASSISD_FASIC_PIO_READ_ERROR

The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link on the indicated Control Board (CB).

CHASSISD_FASIC_PIO_WRITE_ERROR

The indicated routine failed with a write error at the indicated address and register for the indicated F chip and link on the indicated Control Board (CB).

CHASSISD_FASIC_PLL_ERROR

The chassis process (chassisd) could not lock a phased-lock loop (PLL) for the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_RESET_ERROR

The chassis process (chassisd) could not reset the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_SRAM_ERROR

The chassis process (chassisd) detected that SRAM failed to initialize for the indicated F chip on the indicated Control Board (CB).

CHASSISD_FCHIP_CONFIG_MD_ERROR

The chassis process (chassisd) detected an invalid number of Md chips for the indicated F chip, Packet Forwarding Engine and Flexible PIC Concentrator (FPC).

CHASSISD_FCHIP_HSR_ERROR

The chassis process (chassisd) detected an error in the high-speed receiver (HSR) subsystem for the F chip with the indicated characteristics.

CHASSISD_FCHIP_HST_ERROR

The chassis process (chassisd) detected an error in the high-speed transmitter (HST) subsystem for the F chip with the indicated characteristics.

CHASSISD_FCHIP_LINK_ERROR

The chassis process (chassisd) detected an error for the indicated high-speed receiver (HSR) or high-speed transmitter (HST) link for an F chip on the indicated Switch Interface Board (SIB).

CHASSISD_FCHIP_MONITOR_ERROR

The chassis process (chassisd) detected an invalid F-chip module while enabling or disabling the monitoring of F-chip functional blocks.

CHASSISD_FCHIP_PIO_READ_ERROR

The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link.

CHASSISD_FCHIP_PIO_WRITE_ERROR

The indicated routine failed with a write error at the indicated address and register for the indicated F chip and link.

CHASSISD_FHSR_READ_REG_ERROR

The high-speed receiver (HSR) read routine failed at the indicated address on an F-chip register.

CHASSISD_FHSR_WRITE_REG_ERROR

The high-speed receiver (HSR) write routine could not record the indicated value at the indicated address on an F-chip register.

CHASSISD_FHST_READ_REG_ERROR

The high-speed transmitter (HST) read routine failed at the indicated address on an F-chip register.

CHASSISD_FHST_WRITE_REG_ERROR

The high-speed transmitter (HST) write routine could not record the indicated value at the indicated address on an F-chip register.

CHASSISD_FILE_OPEN

The chassis process (chassisd) could not open the indicated file for the indicated reason.

CHASSISD_FM_ERROR

During execution of the indicated fabric management routine, the indicated error occurred between the indicated Switch Interface Board (SIB) and the indicated Packet Forwarding Engine on the indicated Flexible PIC Concentrator (FPC).

CHASSISD_FM_ERROR_SIB_L_FB_HSR

In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the T640 routing nodes (called SIB-Ls) and the SIBs in the TX Matrix platform (called SIB-Ss). The chassis process (chassisd) on the routing node that houses the indicated SIB-L detected an error in the electrical path between the indicated ports on the SIB-L and the corresponding SIB-S.

CHASSISD_FM_ERROR_SIB_L_FB_SMF

In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (the switch-card chassis, or SCC) and the SIBs in the T640 routing nodes (called SIB-Ls). The chassis process (chassisd) on the routing node that houses the indicated SIB-L detected the indicated error as packets that were traveling in the indicated direction were translated between electrical and optical media.

CHASSISD_FM_ERROR_SIB_S_FB_HSR

In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (called SIB-Ss) and the SIBs in the T640 routing nodes (called SIB-Ls). The chassis process (chassisd) on the TX Matrix platform detected an error in the electrical path between the indicated port on the indicated SIB-S and the indicated port on a SIB-L installed in the indicated routing node (line-card chassis, or LCC).

CHASSISD_FM_ERROR_SIB_S_FB_SMF

In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (called SIB-Ss) and the SIBs in the T640 routing nodes (line-card chassis, or LCCs). The chassis process (chassisd) on the TX Matrix platform detected the indicated error as packets that were traveling to or from the indicated LCC were translated between electrical and optical media.

CHASSISD_FM_SIB_ERROR

The chassis process (chassisd) detected the indicated type of error on the indicated Switch Interface Board (SIB) and performed the indicated action.

CHASSISD_FPC_PIC_DETECT_TIMEOUT

The chassis process (chassisd) expects to receive notification within a timeout period that each Flexible PIC Concentrator (FPC) has attached the Physical Interface Cards (PICs) that it houses. It did not receive notification from the indicated FPC.

CHASSISD_GBUS_NOT_READY

The GBUS was not ready when the chassis process (chassisd) first tried to power it on, and the power-up operation timed out.

CHASSISD_GBUS_READBACK_ERROR

There was an error when the chassis process (chassisd) tried to read back information from the GBUS on the indicated component (field-replaceable unit, or FRU).

CHASSISD_HSR_FIFO_ERROR

A first-in, first-out (FIFO) read error occurred during execution of the indicated routine on the indicated high-speed receiver (HSR).

CHASSISD_IPC_DAEMON_WRITE_ERROR

The chassis process (chassisd) could not write to a socket, because of the indicated error. The socket is for a connection to another process that runs on the Routing Engine and helps manage the chassis.

CHASSISD_IPC_MSG_DROPPED

The chassis process (chassisd) dropped an interprocess communication (IPC) message because the message queue had already reached maximum capacity.

CHASSISD_IPC_MSG_UNHANDLED

The chassis process (chassisd) received an interprocess communication (IPC) message about the indicated FRU. The message had the indicated characteristics. The chassisd process could not handle the message.

CHASSISD_MAC_ADDRESS_FABRIC_ERR

The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated fabric interface because of an internal error.

CHASSISD_MALLOC_FAILURE

The chassis process (chassisd) could not allocate memory. The chassisd process tried to continue functioning, but the lack of memory usually causes the process to fail. An administrator needs to restart it.

CHASSISD_MBE_DETECTED

A multi-bit ECC parity error was detected in Routing Engine DRAM.

CHASSISD_OVER_TEMP_CONDITION

The temperature of one or more components (field-replaceable units, or FRUs) exceeded the indicated temperature, which is the upper of two thresholds. The fans (and impellers, if applicable) were in the indicated state. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, the chassisd process shuts down the routing platform. When this message was logged, the indicated number of seconds remained before shutdown.

CHASSISD_PEM_OVERLOAD

The indicated power entry module (PEM) reported an output voltage overload condition.

CHASSISD_PEM_VOLTAGE

The indicated power entry module (PEM) reported a problem with its output voltage.

CHASSISD_RE_OVER_TEMP_CONDITION

The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds.

CHASSISD_RE_OVER_TEMP_WARNING

The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, the chassisd process shuts down the indicated component. When this message was logged, the indicated number of seconds remained before shutdown.

CHASSISD_SBE_DETECTED

Too many single-bit correctable ECC parity errors were detected in Routing Engine DRAM.

CHASSISD_SMB_IOCTL_FAILURE

The indicated ioctl() operation failed at the indicated address on the system management bus (SMB).

CHASSISD_SMB_READ_FAILURE

A read() operation failed at the indicated address on the system management bus (SMB).

CHASSISD_TEMP_SENSOR_FAILURE

The temperature sensor for the indicated component (field-replaceable unit, or FRU) either did not respond to a request from the chassis process (chassisd) for a temperature reading or sent a value that is outside the normal operating range.

CHASSISD_UNEXPECTED_EXIT

The chassis process (chassisd) exited unexpectedly and reported the indicated error.

COSD_MALLOC_FAILED

The class-of-service (CoS) process (cosd) could not dynamically allocate memory, for the indicated reason.

COSD_RTSOCK_LIB_ERR

COSD uses rtsock library for reading and writing data from and to kernel. The specified error occured while using rtsock library to read/write data.

COSD_RTSOCK_WRITE_FAILED

COSD uses rtsock to read/write data from kernel. If the write fails kernel returns an error.

COSD_UNEXPECTED_EXIT

COSD waits for the event notifications and processes the events that it is registered for. There was an error during event-handling initialization.

Daemon Crash

A JUNOS daemon crash occurred with a core dump.

DCD_PARSE_STATE_EMERGENCY

The interface process (dcd) encountered an unhandled internal state during interface parsing.

DCD_TRASHED_RED_ZONE

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. If it does not find the previously written pattern, it means the memory was overwritten, which indicates an error in DCD.

DFWD_MALLOC_FAILED

DFWD must dynamically malloc memory for its needs. This allocation request failed. The specific data structure that was being allocated is listed in the message.

DFWD_PARSE_STATE_EMERGENCY

The firewall process (dfwd) encountered an unhandled internal state while parsing an interface.

DFWD_TRASHED_RED_ZONE

When DFWD 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, DFWD checks for the pattern. If it does not find the previously written pattern, it means the memory was overwritten, which indicates an error in DFWD.

DH_SVC_RTSOCK_OPEN_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not successfully open a routing socket to the kernel. The error string accompanying this log entry indicates the specific error.

DH_SVC_RTSOCK_REGISTER_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not successfully register a callback function with a routing socket. The error string accompanying this log entry indicates the specific error.

DH_SVC_SETSOCKOPT_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not set the indicated socket option.

DH_SVC_SOCKET_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not create a socket.

EVENTD_EVENT_SEND_FAILED

JUNOS processes can request that the event processing process (eventd) notify them when a specific event occurs. The eventd process could not send an event notification for the indicated reason.

EVENTD_FORK_ERR

The event processing process (eventd) could not create a child process for executing policies.

EVENTD_PIPE_ERR

The event processing process (eventd) could not create a pipe for interprocess communication.

FPCLOGIN_IP_ADDRESS_GET_FAILURE

The fpclogin module attempted to get the IP address of the physical interface module. The attempt failed.

FSAD_ERROR

The File System Access process (fsad) internal error message.

FUD_MEMORY_ALLOCATION_FAILURE

The UDP forwarding process (fud) could not allocate the indicated amount of memory from the heap.

FUD_RTSOCK_WRITE_FAILURE

The UDP Forwarding process (fud) could not write to its routing socket for the indicated reason.

FUD_SENDMSG_FAILURE

The UDP Forwarding process (fud) could not send data to the indicated destination port and address using the indicated interface and routing instance, which it needs to do during normal operation.

FUD_SENDMSG_NOINT_FAILURE

The UDP Forwarding process (fud) could not send data to the indicated destination port and address using the indicated routing instance, which it needs to do during normal operation.

FUD_SETSOCKOPT_FAILURE

The UDP Forwarding process (fud) could not set the indicated socket option.

FUD_SOCKET_FAILURE

The UDP Forwarding process (fud) could not create a socket.

GGSN_ALARM_TRAP_SEND

An alarm trap to be relayed by the Services PICs process (serviced) failed to initialize.

GGSN_TRAP_SEND

The system sent a GGSN trap of an unrecognized type.

GRAPH_NO_MEMORY

The graphing process could not allocate memory while trying to create a graph.

JCS_MM_COMMUNICATION_ERROR

The JCS process (jcsd) could not send an SNMP request to the Management Module because of the indicated error.

JCS_READ_BANDWIDTH_ERROR

The indicated error occurred when attempting to read the current switch bandwidth.

JCS_READ_BBD_ERROR

The indicated error occured when attempting to read the current blade bay data via a sysctl call.

JCS_SWITCH_COMMUNICATION_ERROR

The JCS process (jcsd) could not send an SNMP request to the indicated Switch Module because of the indicated error.

L2CPD_ABORT

The Layer 2 Control Protocol process (l2cpd) terminated because of an internal error.

L2CPD_ASSERT

The source code for the Layer 2 Control Protocol process (l2cpd) includes internal self-consistency tests. The l2cpd process with the indicated executable name and process ID (PID) terminated because the indicated test failed at the indicated line number in the indicated source file. The process created a diagnostic core file for analysis by technical support personnel.

L2CPD_ASSERT_SOFT

The source code for the Layer 2 Control Protocol process (l2cpd) includes internal self-consistency tests. The l2cpd process with the indicated executable name and process ID (PID) terminated because the indicated type of check failed at the indicated line number in the indicated source file. The process continued to run, but created a diagnostic core file for analysis by technical support personnel.

L2TPD_EVLIB_CREATE_FAILED

The Layer 2 Tunneling Protocol process (l2tpd) could not create a context for handling asynchronous events.

L2CPD_PPM_WRITE_ERROR

The Layer 2 Control Protocol process (l2cpd) could not write a message on the pipe to the periodic packet management process (ppmd).

L2CPD_SCHED_SLIP

L2CPD delayed an event, such as issuing an adjacency establishment message, that was supposed to occur at a particular time. The event did not occur at the right time.

L2TPD_SERVER_START_FAILED

The Layer 2 Tunneling Protocol (L2TP) server did not start.

L2CPD_SYSTEM_CALL_FAILED

A system call made by the Layer 2 control protocol process (L2CPD) failed.

LACPD_DAEMONIZE_FAILED

The Link Aggregation Control Protocol process (lacpd) could not create a version of itself to run in the background as a daemon.

LIBESPTASK_SNMP_CONN_PROG

The indicated error occurred while the process using libesptask was connecting to the SNMP master agent.

LIBESPTASK_SNMP_SOCKOPT_RECVBUF

The process using libesptask could not set the size of the kernel receive buffer, which allows it to accept the largest possible packet from the Simple Network Management Protocol (SNMP) master agent.

LIBESPTASK_SNMP_SOCKOPT_SENDBUF

The process using libesptask could not set the size of the kernel send buffer, which allows it to send the largest possible packet to the Simple Network Management Protocol (SNMP) master agent.

LIBJNX_DEFAULT_IP_ADDR_NOT_SET

A JUNOS process could not retrieve the system default IP address from the kernel, because the address is not defined there.

LIBJNX_REPLICATE_RCP_ERROR

The rcp command failed during replication.

LIBMSPRPC_CLIENT_INIT_FAILED

A JUNOS process (mspinfo) could not establish initialization of the RPC client.

LIBMSPRPC_CLIENT_KCOM_FAILED

A JUNOS process (mspinfo) could not establish initialization of the kcom subsystem.

LIBMSPRPC_CLIENT_NO_CONNECTION

Remote execution of the command given from the Routing Engine to the PIC . The Routing Engine cannot connect to the PIC.

LIBMSPRPC_CLIENT_NO_REPLY

Remote execution of the command given from the Routing Engine to the PIC failed. There was no reply from the PIC.

LIBMSPRPC_CLIENT_PIC_DOWN

Remote execution of the command given from the Routing Engine to the PIC failed. The PIC is down.

LIBMSPRPC_CLIENT_WRONG_OUTPUT

Remote execution of the command given from the Routing Engine to the PIC failed. The PIC returned unexpected output.

LIBSERVICED_CLIENT_CONNECTION .

An attempt to establish a client connection failed.

LIBSERVICED_SOCKET_BIND

An attempt to bind a server socket for receiving client requests failed.

LIBSERVICED_SOCKET_PRIVATIZE

An attempt to attach a socket to the management routing instance for communication between the Routing Engine and GGSN-C PICs failed.

MIB2D_SNMP_INDEX_DUPLICATE

The first interface name was assigned the same SNMP index as the second interface name.

MIB2D_SNMP_INDEX_UPDATE_STAT

MIB2D cannot get the status of the SNMP index file.

MIB2D_SNMP_INDEX_WRITE

MIB2D cannot write to a file containing all the indices.

PFE Crash

Any PFE board crash that occurs in conjunction with a system exception message.

PPMD_ASSERT_SOFT

The source code for the periodic package management process (ppmd) includes internal self-consistency checks. As the ppmd process with the indicated process ID (PID) executed the binary compiled from the indicated source file, a check failed at the indicated line number in the file. The ppmd process created a diagnostic core file for analysis by technical support personnel and continued to run.

RDD_EVLIB_CREATE_FAILURE

The redundant interfaces process (rdd) could not create a context used for handling all asynchronous events (such as timers and message availability).

RPD_ABORT

The routing protocol process (rpd) terminated because of an internal error.

RPD_ACTIVE_TERMINATE

After receiving multiple termination requests, the routing protocol process (rpd) exited without performing the indicated cleanup tasks.

RPD_ASSERT

The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, causing the instance of rpd that was using the indicated binary and had the indicated process ID (PID) to terminate. The process created a diagnostic core dump for analysis by technical support personnel.

RPD_ASSERT_SOFT

The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, but the instance of rpd that was using the indicated binary and had the indicated process ID (PID) continued running. The process created a diagnostic core dump for analysis by technical support personnel.

RPD_DYN_CFG_BAD_REQ_OPCODE

The routing protocol process (rpd) received a dynamic configuration request with an unexpected operation code.

RPD_DYN_CFG_GET_PROFILE_FAILED

The routing protocol process (rpd) tried to load a profile from the database and failed.

RPD_DYN_CFG_GET_SNAPSHOT_FAILED

The routing protocol process (rpd) tried to load client session data from the database and failed.

RPD_DYN_CFG_PDB_CLOSE_FAILED

The routing protocol process (rpd) tried to close the profile database and failed.

RPD_DYN_CFG_PDB_OPEN_FAILED

The routing protocol process (rpd) tried to open the profile database and failed.

RPD_DYN_CFG_PROCESSING_FAILED

The routing protocol process (rpd) tried to process dynamic configuration and failed.

RPD_DYN_CFG_REGISTER_FAILED

The routing protocol process (rpd) tried to register with the dynamic configuration subsystem and failed.

RPD_DYN_CFG_REQUEST_ACK_FAILED

The routing protocol process (rpd) tried to ACK a dynamic configuration request and failed.

RPD_DYN_CFG_SCHEMA_OPEN_FAILED

The routing protocol process (rpd) tried to open the configuration schema and failed.

RPD_DYN_CFG_SDB_CLOSE_FAILED

The routing protocol process (rpd) tried to close the session database and failed.

RPD_DYN_CFG_SDB_OPEN_FAILED

The routing protocol process (rpd) tried to open the session database and failed.

RPD_ISIS_LSPCKSUM

The indicated IS-IS informational link-state PDU (LSP) failed an internal checksum validity test, implying that it was corrupted.

RPD_ISIS_OVERLOAD

The IS-IS link-state database is full and no additional memory can be allocated for it.

RPD_LMP_UNEXPECTED_OPCODE

The routing protocol process (rpd) received the indicated type of message, which had the indicated invalid operation code.

RPD_OS_MEMHIGH

The routing protocol process (rpd) is using the indicated amount and percentage of Routing Engine memory, which is considered excessive.

RPD_RT_ERROR

A route in the routing table was found to be in an unrecoverable error state.

RPD_TASK_FORK

The routing protocol process failed to create the indicated child process.

SERVICED_CLIENT_DISCONNECTED

The remote client closed the connection or stopped responding.

SERVICED_CLIENT_ERROR

An I/O error caused the termination of a connection with an interface client.

SERVICED_COMMAND_FAILED

An error caused a command being executed on an interface client to be cancelled.

SERVICED_CONNECTION_ERROR

The remote client closed the connection when data was expected.

SERVICED_EVENT_FAILED

The Services PICs process (serviced) could not continue processing a task because a call to a function in the event library failed.

SERVICED_INIT_FAILED

One of the steps in the initialization sequence for the Services PICs process (serviced) failed.

SERVICED_INTERNAL_INCONSISTENCY

An internal consistency check failed due to a mismatch between expected and received values for the specified object.

SERVICED_MALLOC_FAILURE

The Services PICs process (serviced) could not allocate the number of bytes needed to hold the indicated object.

SERVICED_PID_FILE_LOCK

As a part of normal startup, the Services PICs process (serviced) locks a file and writes its process ID (PID) into it. It could not lock the file.

SERVICED_PID_FILE_UPDATE

As a part of normal startup, the Services PICs process (serviced) locks a file and writes its process ID (PID) into it. It could not write to the file.

SERVICED_NETWORK_FAILURE

An attempt to use the indicated network library call failed with an error.

SERVICED_RTSOCK_SEQUENCE

The Services PICs process (serviced) encountered a sequence error while receiving messages from the routing socket library.

SERVICED_SIGNAL_HANDLER

As a part of normal functioning, the Services PICs process (serviced) attempted to initialize a signal-handling function. Part of the initialization failed with an error.

SERVICED_STDLIB_FAILURE

The value returned by a call to a library function indicated that an error occurred.

SERVICED_SOCKET_CREATE

An attempt by the Services PICs process (serviced) to create a new socket for communication with an interface client failed with an error.

SERVICED_SOCKET_IO

A call to a socket library function indicated that an error occurred while attempting to perform I/O.

SERVICED_SOCKET_OPTION

An attempt to set an option on a socket failed.

SPD_DAEMONIZE_FAILED

The adaptive services process (spd) could not create a version of itself to run in the background as a daemon.

SPD_EVLIB_CREATE_FAILURE

The adaptive services process (spd) could not create a context used for handling all asynchronous events (such as timers and message availability).

TASK_OS_MEMHIGH

The process is using the indicated amount and percentage of Routing Engine memory, which is considered excessive.

TASK_SYSTEM

A system call made by this process failed.