The periodic packet management process (ppmd) could not read a message on a pipe for the indicated protocol.
The problem related to this syslog message is described in the following sections:
The periodic packet management process daemon (ppmd) handles the generation and processing protocol of hello packets and monitors and manages router adjacencies. The goal of ppmd is to permit scaling to large numbers of protocol peers by offloading the mundane processing tasks associated with periodic packet generation. The ppmd process can run directly in the PFE to offload RE cycles on application-specific integrated circuit (ASIC)-based systems.
When a PPMD_READ_ERROR event occurs, it writes a message similar to the following:
ppmd[1580]: PPMD_READ_ERROR: Read error on pipe from OSPF2: premature EOF (connection closed) ppmd[3205]: PPMD_READ_ERROR: Read error on pipe from ISIS: premature EOF (connection closed) ppmd[3205]: PPMD_READ_ERROR: Read error on pipe from LDP: premature EOF (connection closed) ppmd[3205]: PPMD_READ_ERROR: Read error on pipe from ESIS: premature EOF (connection closed) eventd[91901]: EVENTD_ESCRIPT_EXECUTION: Trying to execute the script 'PPMD_READ_ERROR.slax' from '/var/db/scripts/event/' ppmd[1256]: PPMD_READ_ERROR: Read error on pipe from OSPF2: premature EOF (connection closed)
The periodic packet management process (ppmd) could not read a message on a pipe for the indicated protocol. The PPMD_READ_ERROR messages may be seen when the pipe between RPD and PPMD goes down. The PPMD_READ_ERROR messages could also possibly be seen with any type of protocol flapping or protocol going down.
Examine the following output to help determine the cause of this message:
show log messages
Look for any related events that occurred at or just before the PPMD_READ_ERROR message that may have contributed to this error.
Also, check for possible RPD (routing protocol daemon) core dumps with the command show system core-dumps.
Note: PPMD disconnecting from the RPD pipe will not always cause a core-dump.
Perform these steps to troubleshoot this issue:
- Open a case with your technical support representative to investigate the issue further.