Troubleshooting
Problem
We have configured the ObjectServer and clients for FIPS authentication however PA fails to start with the following message:
Error: Authentication being used is not FIPS compliant. Use PAM for external authentication.
There are also "Net-Lib protocol driver call to register a listener failed" messages observed in the ObjectServer.log file.
Symptom
The following output is generated on the start screen:
omniserv</opt/IBM/tivoli/netcool/omnibus/bin># ./nco_pad -name NCO_PA -messagelevel debug
Netcool/OMNIbus Process Agent Daemon - Version 8.1.0 64-bit
Netcool/OMNIbus PA API Library Version 8.1.0 64-bit
Sybase Server-Library Release: 15.0
Sybase Server-Library Release: 15.0
Server Settings :
Name of server : NCO_PA
Path of used log file : /opt/IBM/tivoli/netcool/omnibus/log/NCO_PA.log
Configuration File : /opt/IBM/tivoli/netcool/omnibus/etc/nco_pa.conf
Child Output File : /dev/null
Maximum logfile size : 1024
Thread stack size : 307200
Message Pool size : 45568
PID Message Pool size : 50
Rogue Process Timeout : 30
Truncate Log : False
Instantiate server to daemon : True
Internal API Checking : False
No Configuration File : False
Start Auto-start services : True
Authentication System : UNIX
Trace Net library : False
Trace message queues : False
Trace event queues : False
Trace TDS packets : False
Trace mutex locks : False
Host DNS name : omniserv
PID file (from $OMNIHOME) : ./var/NCO_PA.pid
Kill Process group : False
Secure Mode : False
Administration Group Name : ncoadmin
Properties file : /opt/IBM/tivoli/netcool/omnibus/etc/NCO_PA.props
Message level : Debug
Host Alias Lookups : True
Error: Authentication being used is not FIPS compliant. Use PAM for external authentication.
Forking to a Daemon Process.............
In the ObjectServer.log file we see:
Fatal: F-IVM-005-001: OpenServer - Fatal Error: 16029/20/0: Failed to start any network listeners
Error: E-IVM-005-002: OpenServer - Error: 16240/10/0: Net-Libraryroutine sybnet_listen() failed in srv__start_net
Network error: status = 23 - Net-Lib protocol driver call to register a listener failed
Error -1:Socket bind failed - errno 67 The socket name is already in use.
We are however able to connect clients including nco_sql to the ObjectServer
Document Location
Worldwide
[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSSHTQ","label":"Tivoli Netcool\/OMNIbus"},"ARM Category":[{"code":"a8m50000000L0B6AAK","label":"Core Omnibus-\u003EProcess Agent nco_pad-\u003Enco_pad Configuration-\u003EPAM"},{"code":"a8m50000000L0B6AAK","label":"Core Omnibus-\u003EProcess Agent nco_pad-\u003Enco_pad Configuration-\u003EPAM"},{"code":"a8m50000000L0B6AAK","label":"Core Omnibus-\u003EProcess Agent nco_pad-\u003Enco_pad Configuration-\u003EPAM"}],"ARM Case Number":"TS005095593","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Version(s)"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
09 May 2025
UID
ibm16420395