IBM Support

File descriptors too large for select, limiting

Troubleshooting


Problem

This technote discusses how to resolve the error, file descriptors too large for select, limiting, when using IBM® Rational® ClearCase® on UNIX® or Linux®.

Symptom

There may be instances where the above error message is reported in the logs for an unknown reason.

The error has also been reported in the logs as a result of a ClearCase 2003.06 installation on a Solaris 10 host where the error Unable to contact albd_server on host <hostname> was also reported.

The albd_log file reports the following errors:

2007-11-06T11:48:14-05 albd_server(10845): Ok: Server up and running
2007-11-06T11:48:14-05 albd_server(10845): Error: File descriptors too large for select, limiting

Although the installation didn't actually fail, it did report the following warning message when attempting to mount the public VOBs.

Loading MVFS ...
Mounting public VOBs...
cleartool: Error: Unable to contact albd_server on host 'sbdevsvr420'  
cleartool: Error: Unable to find albd_server.
Trouble mounting public VOBs(32:1)
----
End of command output.
WARNING:
**** Something went wrong while mounting public VOBs.  Please review the
**** above output from the "/opt/rational/clearcase/etc/clearcase" script for
**** information on the problem.
***************************************************************************
>> Begin component final customization
***************************************************************************
FINAL: sbdevsvr420      Errors:0        Warnings:1

The MVFS did get installed.

Cause


The operating system file descriptor limit has been set to a value higher than ClearCase can use, and ClearCase automatically sets the limit down to 1024 (or 1023+1).

Environment


ClearCase Start-up Script Location:

2003.06.00 and later

$ /opt/rational/clearcase/etc/clearcase

2002.05.00

# /usr/atria/etc/atria_start

Diagnosing The Problem


Check the output of the command "ulimit -a" which will show the current file descriptors value.


Example:

%>ulimit -a
nofiles(descriptors) 260000

Resolving The Problem

To correct this problem add the following line to the ClearCase startup script:

ulimit -n 1023

Note: This entry can be added on any line within the startup script.

After you make this change, you need to stop and restart ClearCase for the change to take effect.

This change only effects the ClearCase start-up script. This change prevents any of the subsequent forked server processes, such as db_server or vobrpc_server, from trying to use any file descriptors greater than 1023 matching an internal limit.

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Operating System Configurations","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF015","label":"IRIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"2002.05.00;2003.06.00;7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21142704