COR_Listen error: binding socket 8001 error 125 reported in IBM FileNet Image Services

Technote (troubleshooting)


Problem(Abstract)

Users cannot connect to IBM FileNet Image Services and the elog reports that these failed connections are unable to bind to port 8001

Symptom

User connections to IBM FileNet Image Services fail and report the following errors in the elog


2012/06/03 23:35:03.216 155,18,126 <fnsw> COR_Listen -pt -s32769 -t3600 -d100  (14473.1.51 0x3889.1) ...
WARNING: binding socket 8001 error 125 retry #2 in 30 seconds

2012/06/03 23:35:33.216 155,18,126 <fnsw> COR_Listen -pt -s32769 -t3600 -d100  (14473.1.51 0x3889.1) ...
WARNING: binding socket 8001 error 125 retry #3 in 30 seconds


Cause

This issue is caused by 3rd party processes running as root, binding to the reserved IBM FileNet Image Services port 32768 (8001 in hex is 32769 in dec)

Diagnosing the problem

Using the UNIX utility lsof identify the process as follows:

lsof -i :cor
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF    NODE NAME
kill.me  383 root   10u  IPv4 0x6002bb7ca80      0t0  TCP localhost:32769 (LISTEN)

Resolving the problem

The procedures are as follows:

  1. Identify the process binding to port 32769 as detailed above (using the lsof command)
  2. Kill that process via the UNIX kill command, and restart the IBM FileNet Image Services software
  3. Reconfigure the rogue process to prevent it taking ownership of port 32769 in the future

Rate this page:

(0 users)Average rating

Document information


More support for:

FileNet Image Services
Image Services

Software version:

4.1.1, 4.1.2, 4.2

Operating system(s):

AIX, HP-UX, Linux, Solaris

Reference #:

1597413

Modified date:

2013-06-24

Translate my page

Machine Translation

Content navigation