IBM Support

Albd(*): Error: Unable to allocate port in specified range

Troubleshooting


Problem

This technote explains some causes and resolutions to the "Unable to allocate port in specified range" error seen when performing various IBM Rational ClearCase operations.

Symptom

  • The following errors may be seen in the albd log



    ClearCase Error ALBD 1024 Albd(74): Error: PFM_ASSERT:(dup_size == sizeof(*reply)) failed: '.../albd_svc.c':2881

    ClearCase Error ALBD 1024 Albd(74): Error: bind: [WINSOCK] Address already in use ClearCase Error ALBD 1024 Albd(74): Error: Unable to allocate port in specified range: 8888, 8898


    albd_server 1788 Albd(1788): Error: bind: 0
    albd_server 1788 Albd(1788): Error: Unable to allocate port


  • The following error may be seen in various ClearCase logs depending on the operation being performed.


    albd_contact call failed: RPC: Timed out cleartool: Error: Unable to contact albd_server on host '<hostname>'

  • Errors similar to the following may be found in the operating system Event Logs:


    Albd(1788): Error: Unable to allocate port in specified range: 49152, 65535
    Albd(1788): Error: bind: 0

Cause


Cause #1

This error is most often seen in the MultiSite shipping and synchronization logs and means that the shipping server operation required more ports than were available through the CLEARCASE_MIN_PORT and CLEARCASE_MAX_PORT settings at the current time.

Occasional errors of this nature related to shipping can usually be ignored. If they become more frequent it may be necessary to make additional ports available to the shipping_server.

See "Store-and-forward through a firewall" for more information on using the CLEARCASE_MIN_PORT and CLEARCASE_MAX_PORT settings.

When these errors are seen in logs other than the shipping and synchronization logs it indicates that the CLEARCASE_MIN_PORT and CLEARCASE_MAX_PORT have been set on a server that is not a dedicated shipping server. Configuring VOB, and View servers as well as ClearCase clients to work through a firewall is not supported and will cause problems. All ClearCase processes are affected by the CLEARCASE_MIN_PORT and CLEARCASE_MAX_PORT settings so they should not be used to configure the shipping_server operation directly on a VOB server.

Cause #2

A socket allocation issue of Windows 2008 Server SP1.

Resolving The Problem

Solution#1

Do not set the ClearCase MultiSite variable CLEARCASE_MIN_PORT and CLEARCASE_MAX_PORT on a ClearCase host that is running ClearCase processes other than the Shipping Server.

These variables are meant ONLY for a host where only the ClearCase MultiSite Shipping Server is installed.

Refer to the ClearCase Knowledge Center for more information.



As of ClearCase versions 7.1.0.2, 7.0.1.5, 7.0.0.6, or later it is possible to restrict the ports available to the shipping server without affecting other ClearCase operations by using the albd_rt_params.conf file. This is now available for both Windows and Unix operating systems.

Refer to technote 1233313 for more information on the albd_rt_params.conf file. Take note of the MSSHP_STRICT option mentioned in that technote as this reverses a change to the default behavior of the MIN and MAX port settings introduced in the albd_rt_params.conf file for port restrictions.


Solution #2

Upgrading the host to Windows 2008 Server with SP2 may solve the problem. This symptom has been observed to disappear after applying SP2. No more specific details are known.

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Environment Variables","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.0.1;7.0.0.2;7.0.0.3;7.0.0.4;7.0.0.5;7.0.1;7.0.1.1;7.0.1.2;7.0.1.3;7.0.1.4;7.1;7.1.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Environment Variables","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 September 2018

UID

swg21122554