The UTMD_MALLOC_FAILURE message is reported into the system message file when the Unified Threat Management process (utmd) could not allocate memory for a resource. This article documents an approach to troubleshoot this problem. Unified Threat Management is currently only supported on J-Series and SRX devices. The UTMD_MALLOC_FAILURE message is logged each time the umtd … [Read more...]
ACCT_MALLOC_FAILURE
ACCT_MALLOC_FAILURE The accounting statistics process could not allocate memory from the heap. The problem related to this syslog message is described in the following sections: The ACCT_MALLOC_FAILURE message appears when there is an error allocating memory for the accounting statistics process. When a ACCT_MALLOC_FAILURE event occurs, a message will be logged similar … [Read more...]
KERNEL: rdp retransmit error
The kernel on the controller (e.g., Routing Engine) is having difficulty communicating with the PFE (Packet Forwarding Engine). The problem related to this syslog message is described in the following sections: The KERNEL: rdp retransmit error message is logged whenever the kernel on the controller is having difficulty communicating with the Packet Forwarding Engine … [Read more...]
CHASSISD_IPC_WRITE_ERR_NULL_ARGS
The chassis process (chassisd) could not send a message to the indicated component (Field-Replaceable Unit or FRU) because one or more required parameters had a null value. The problem related to this syslog message is described in the following sections: The CHASSISD_IPC_WRITE_ERR_NULL_ARGS message is logged each time the chassisd process is not able to send a message to … [Read more...]
VPN related traps are not seen in syslog
This article describes the issue of traps from the JnxVpn MIB not being seen in syslog; but sent as expected to a trap collector. When a VPN flaps or fails, JnxVpn traps are not seen in the messages log; but are seen by the trap collector. The types of traps that are logged to the message log varies between major releases. Use the help syslog | no-more | match trap … [Read more...]
SYSTEM:.*snp_igmp_io_flood: relay failed.*
The snp_igmp_io_flood: relay failed error message is seen on the EX platform and is harmless. This message indicates that the device has corrected a condition in which it would have flooded an IGMP packet with an unknown type field back out the same port on which it was received. This message is cosmetic. Example of log messages generated: May 24 19:47:08 … [Read more...]
SRCHIP[(].[)]: (%PFE-.*: )?RKME int_status1 ox100
RKME is a key match engine located in the FPC SRCHIP/RCHIP hardware. The RKME engine received the 'interrupt shown' error. When an RKME event occurs, a message similar to the following is reported: fpc0 SRCHIP(1): RKME int_status1 0x100 fpc4 SRCHIP(0): %PFE-3: RKME int_status1 0x100 The cause could be due to poor link quality on one of the FPC transit traffic … [Read more...]