Error Unable Contact Albd_server
a view remote server; albd_server; albd; view; mkview; startview; CC Technote (troubleshooting) Problem(Abstract) Attempts to start or create an IBM Rational ClearCase view causes "cleartool: Error: Unable to contact albd_server on host 'remote server'" error. Symptom The following errors occur 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 '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'
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 ClearCase Web (CCWeb). Refer to Rational ClearCase server processes for further information about the processes that are run on view and VOB server hosts. Ensure that ClearCase is installed on the view server host and it is started; otherwise, create or move the view to a system that has ClearCase installed and running. Review the Starting and stopping Rational ClearCase section of IBM Rational ClearCase Administrators Guide under the topic of Rational ClearCase network planning and administration for information about starting and stopping ClearCase. Solution 2 (Windows) If the ClearCase service account network password has been changed, it also needs to be updated on the local machine. Refer to 1146
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 to send update packets or performing a multitool lsepoch -actual command. Symptom After creating a new replica at a remote site the following error is reported when trying to ship synchronization packets 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: http://www.ibm.com/support/docview.wss?uid=swg21131088 Error: Unable to contact albd_server on host 'hostX' 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 http://www-01.ibm.com/support/docview.wss?uid=swg21298788 ClearCase Knowledge Center for further information. This can also happen if ClearCase is not installed on 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
Error: Unable to contact albd_server on host; unable to contact; albd_server; hostname; IP; DNS; NIS; http://www-01.ibm.com/support/docview.wss?uid=swg21134492 NIS+; Unable to find albd_server; 1134492 Technote (troubleshooting) Problem(Abstract) This technote explains why IBM Rational ClearCase hosts running on UNIX or Linux configured with multiple IP addresses can cause the error, cleartool: Error: Unable to contact albd_server on host 'myserver', along with recommendations to resolve the problem. Symptom After starting the ClearCase daemons, error unable attempts to mount public VOBs yield the following errors: Mounting public VOBs... cleartool: Error: Unable to contact albd_server on host 'myserver' cleartool: Error: Unable to find albd_server. Trouble mounting public VOBs(32:1) Cause If your host has more than one IP address, ClearCase uses what is returned by the method you have predetermined, such as error unable contact nslookup, to match hostname with IP address. While these methods may include DNS, NIS/NIS+, or local files, chances are that you are not going off local files. Diagnosing the problem On the host referenced in the albd error (myserver), cat the /etc/hosts file and look at the IP address. Example: %cat /etc/hosts 127.0.0.1 localhost.localdomain localhost aaa.bb.ccc.dd myserver myserver.rational.com Run nslookup to determine which IP address is returned. Example: % nslookup myserver Server: nis3.rational.com Address: aaa.bb.ccc.dd Name: myserver.rational.com Address: aaa.bb.ccc.ee Note: The host myserver returns 2 entries. One named nis3 and the other myserver. Resolving the problem Change the IP address for the hostname in /etc/hosts. If you are using NIS/NIS+, put the actual IP address returned by nslookup If you are using DNS, copy the relevant entry from the DNS server's routing table Example: aaa.bb.cc