SsoConfig settings seem to not take effect fully

book

Article ID: 144182

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

The following error is seen when running SsoConfig:

 

log4j:ERROR exception setting timeout, shutting down server socket.

java.net.BindException: Address already in use (Bind failed)

        at java.net.PlainSocketImpl.socketBind(Native Method)

        at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)

        at java.net.ServerSocket.bind(ServerSocket.java:375)

        at java.net.ServerSocket.<init>(ServerSocket.java:237)

        at java.net.ServerSocket.<init>(ServerSocket.java:128)

        at org.apache.log4j.net.SocketHubAppender.createServerSocket(SocketHubAppender.java:365)

        at org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(SocketHubAppender.java:433)

        at java.lang.Thread.run(Thread.java:748)

Environment

Release : 3.7

Component : IM Reporting / Admin / Configuration

Resolution

This error can be seen when running SsoConfig as a non-Root user.  Either change to the root user or utilize sudo to run SsoConfig.