shibd Aborted, No Error in Logs

[Kannan, Satheesh (ELS-CON)]

Thanks, Scott.

I wonder, when shibd communicates over TCP/IP sockets, usually listening on localhost (127.0.0.1) at a configured port.

No socket file (like /var/run/shibboleth/socket) is created unless explicitly configured to use a Unix socket

Shibboleth2.xml configured using

 <TCPListener acl="207.25.181.78 138.12.84.29 138.12.84.30 127.0.0.1" address="127.0.0.1" port="25009" stackSize="0"/>

Regards,
Satheesh


________________________________
From: Cantor, Scott <cantor.2 at osu.edu>
Sent: Friday, July 18, 2025 6:24 PM
To: Shib Users <users at shibboleth.net>
Cc: Kannan, Satheesh (ELS-CON) <s.kannan.1 at elsevier.com>
Subject: Re: shibd Aborted, No Error in Logs

*** External email: use caution ***



> Thanks for explaining. I haven't seen this issue in earlier versions.

Then it's your environment that's changed because there haven't been any changes in the relevant code for years. That probably points to load changing more than anything else, or less likely that Linux has changed in some way that's just incompatible with the design under some conditions.

Given that it's dying inside the socket call, it occurs to me to wonder if, assuming it's operating with the default use of a domain socket, whether something is improperly removing the domain socket file from /var/run/shibboleth and whether that might have that kind of impact.

-- Scott



________________________________

Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33158992, Registered in The Netherlands.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250718/b62afe6c/attachment.htm>