000020637 - Error: 'SIGPIPE  write with no one to read  resending' returned by sdadmind in system log

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000020637
Applies ToRSA ACE/Server 5.1 (no longer supported as of 7-14-2006)
Sun Solaris 2.8
IssueError: "SIGPIPE, write with no one to read, resending" returned by sdadmind in system log
The full error is reported in the system log with the following format:
<date & time> <server name> sdadmind[308]: [ID 735426 daemon.crit] SIGPIPE, write with no one to read, resending
Customer reports no anomalous behavior by Remote Administration clients
ResolutionPlease note this solution refers to an issue where there are no problems with running Remote Administration. If you are having problems running Remote Administration, please refer to Sdadmind causing Remote Administration hang and connect failure

The SIGPIPE signal is received by a process when it attempts to write to a connection that has no reader. Most processes experience SIGPIPE errors in the normal course of execution if they are client/server based or using inter process communication. The sdadmind is client/server based so a certain number of SIGPIPEs are expected.

When a server side process receives a SIGPIPE signal, this signifies that the client has gone away unexpectedly. An end-user may have shut down the machine with a remote administration console running, or a plug was pulled for example. In this case, there had been no complaints about the remote administration consoles acting irregularly so it is safe to assume that the problems occur during shutdown. The messages being seen in the system log are from the in-built RSA signal handler. This handler is catching these signals, handling them gracefully and returning to the business at hand so the product is working correctly.
Legacy Article IDa17922