Siteminder policy sever cannot start up with TCP Socket error:9999
search cancel

Siteminder policy sever cannot start up with TCP Socket error:9999

book

Article ID: 425813

calendar_today

Updated On:

Products

SITEMINDER

Issue/Introduction

Policy sever cannot startup, already tried the KB below,

https://knowledge.broadcom.com/external/article/103909/failed-to-initialize-tcp-server-socket-s.html

 

smps.log

[CServer.cpp:8793][ERROR][sm-Server-01660] Failed to initialize TCP server socket: Socket error:9999

Cause

Run strace command to get strace.log,

strace -f -t -i -v -o strace.log -s 16384 ./start-ps

The strace.log shows failure of binding port 44441,

1859996 13:31:41 [00007fbfd678122b] bind(23, {sa_family=AF_INET, sin_port=htons(44441), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EADDRINUSE (Address already in use)

The netstat command doesn't show any process listening on port 44441, but follow command shows that 44441 is used on an established connection

# ss -Htanp 'sport = :44441'
ESTAB   0  0   127.0.0.1:44441   127.0.0.1:55426   users:(("cvd",pid=2008,fd=6))

Resolution

The port 44441 is used by another application, the application needs to use another port, or run on another server to avoid the port conflict.