Recently we have the following notices in the alarm console:
In SLNet logs this error is associated with different events:
- What does this error mean and what are the implications for the DMS ?
- Any advise on how we can troubleshoot this further and stop the errors ?
Hey Wale,
Part of the inter-process communication (IPC) in DataMiner ends up through pipes, basically 2 processes share some memory through which data can be exchanged. When there is an issue with these pipes you will see this kind of error popping up, it indicates that the pipe is considered closed so no communication can be done through it.
As stated, these pipes get used for communication between processes so this kind of issues can result in a wide array of symptoms as it essentially means one or more processes are cut of from communicating with another. From the screenshot it seem yours are mainly situated in SLNet, so the issues will likely result in being unable to connect clients, data not coming through to clients, ....
Whilst it is hard to tell exactly what caused you particular issue, this error usually seems to pop up after a period of high resource usage, or after other issues such as RTE, exceptions. So it is a good idea to check the logging for anything conspicuous around the time the error first appeared. Short term a DataMiner restart will get rid of the issues, but they might return if there is an underlying issue.