Clearcase Error Unable To Contact Albd Server
Contents |
a view remote server; albd_server; albd; view; mkview; startview; CC Technote (troubleshooting) Problem(Abstract) Attempts
How To Start Albd_server In Windows
to start or create an IBM Rational ClearCase view causes cleartool error unable to contact albd_server on host linux "cleartool: Error: Unable to contact albd_server on host 'remote server'" error. Symptom The following errors occur
Cannot Bind An Admin_server Handle On Host
when you attempt to either start a view or create a view. Windows Example: # cleartool startview my_view
cleartool: Error: Unable to contact albd_server on host unable to find albd_server 'remote server'
cleartool: Error: Couldn't set view tag my_view: ClearCase object not found The server to which the view is stored does not have the ClearCase ALBD service running. UNIX / Linux Example:
# cleartool mkview -tag mtest /net/server/views/my_view.vws
cleartool: Error: Unable to contact albd_server on host 'remote server'
cannot bind an admin_server handle on host clearcase object not found cleartool: Error: Cannot bind an admin_server handle on "remote server": ClearCase object not found.
cleartool: Error: Unable to create view "/net/server/views/my_view.vws". Cause Possible causes for the error: The view is being stored in a mounted directory, but the system that the mounted directory is stored on does not have ClearCase running or installed. If ClearCase is installed, there might be an issue with MVFS on that host. (Windows) This error can also result if the network password for the "Atria Location Broker" service account (by default: clearcase_albd) has been changed. Resolving the problem Solution 1 Check your configuration performing following steps: Investigate the host where the view storage resides ensuring that ClearCase is running and for dynamic views, that there are no problems with the MVFS. Check if ClearCase is installed and started on each server host that is in use in a ClearCase environment, unless you are using alternate protocols like ClearCase Remote Client (CCRC) or ClearCa
1298788 Technote (troubleshooting) Problem(Abstract) This technote explains why the error "multitool: Error: Unable to contact albd_server on host 'hostX'" occurs when using IBM Rational ClearCase MultiSite
Albd_server Must Run In The Clearcase Group
to send update packets or performing a multitool lsepoch -actual command. Symptom After cleartool: error: couldn't set view tag clearcase object not found creating a new replica at a remote site the following error is reported when trying to ship synchronization packets
Albd Service
or trying to run lsepoch -actual to communicate with the new replica: $ multitool lsepoch -actual fin_bm_bm@/scm_bm_bm For VOB replica "/scm_bm_bm": multitool: Error: Unable to contact albd_server on host 'hostX' http://www.ibm.com/support/docview.wss?uid=swg21131088 multitool: Error: Server host "hostX" may be running a ClearCase release that does not provide this service multitool: Error: Could not get handle for remote VOB replica "fin_bm_bm": ClearCase object not found Cause Network traffic on port 371 which is used by ClearCase may be blocked. Refer to the ClearCase Knowledge Center for further information. This can also happen if ClearCase is not installed on http://www-01.ibm.com/support/docview.wss?uid=swg21298788 the host reported in the error. Note: The host does have to exist for this error to occur. Diagnosing the problem Ping is working fine but a traceroute on port 371 cannot find the target host. ccadmin@vobserver ~¨$ traceroute -p 371 10.84.72.208 traceroute to 10.84.72.208 (10.84.72.208), 30 hops max, 46 byte packets 1 129.1.0.1 (129.1.0.1) 0.437 ms 2.991 ms 0.401 ms 2 129.1.30.14 (129.1.30.14) 0.241 ms 0.226 ms 0.221 ms 3 10.64.64.1 (10.64.64.1) 0.989 ms 1.095 ms 0.991 ms * * * * * * ... Refer to technote 1152315 - Determine network connectivity to a remote ClearCase server using albd_list for further information about how to test for ClearCase network connectivity. Resolving the problem Resolve the network issue that may be blocking port 371 to ensure that ClearCase communications between the machines is possible. Also, check that the replica wasn't created with an incorrect host name. You can run a multitool lsreplica -long to check the host name. Docume
'myhost' albd_contact call failed: RPC: Unable to receive; errno = [WINSOCK] Connection reset by peer rgy_upgrade; 1207025 Technote http://www-01.ibm.com/support/docview.wss?uid=swg21207025 (troubleshooting) Problem(Abstract) This technote explains why IBM Rational ClearCase has problems contacting the albd_server process after upgrading to Service Release 4 (SR4) on Microsoft Windows. Cause After upgrading to version 2003.06 Service Release 4 and following the restart results in the below error: rgy_upgrade.exe: Error: Unable to contact albd_server on host 'myhost'albd_contact call failed: RPC: Unable to unable to receive; errno = [WINSOCK] Connection reset by peer These errors are produced while rgy_upgrade waits for the ClearCase Atria Location Broker (albd) service. The albd service may not have been started prior to the rgy_upgrade command being run. The rgy_upgrade command is run once automatically after a restart following the Service Release 4 upgrade. Since it error unable to can not be predicted which order the Windows Services start, rgy_upgrade may be started before the albd server process is started. In most cases, the albd service will start in time for the rgy_upgrade to proceed and no intervention is required. Resolving the problem If you see the following message, you will need to ensure that the albd service is running and then run rgy_upgrade again: "The rgy_upgrade tool timed out waiting for the albd server. Please check system and albd error logs. When the issue is resolved, run rgy_upgrade to update the ClearCase registry entries for VOB replicas that reside on this host." Ensure that the albd service is running and then run rgy_upgrade as follows: