Troubleshooting
Problem
This technote explains why the error []Process not running on registry specified hostname (hostname)[] might occur intermittently in db_server logs on an IBM® Rational® ClearCase® VOB server host.
Symptom
There are a number of the following events in db_server logs which appear at seemingly intermittent times:
2007-12-04T10:08:18+09 db_server(9279): Error: Process not running on registry specified hostname (hostname01.domain.com)
2007-12-04T10:08:27+09 db_server(9279): Error: Process not running on registry specified hostname (hostname01.domain.com)
Also, running multitool chepoch or lsepoch commands on the remote system will fail as follows:
multitool chepoch -actual Boston@/vobs/VOB_core
multitool: Error: Error from VOB database:
"hostname01.domain.com:/clearcase/vb001/vobs/VOB_core.vbs".
multitool: Error: Trouble opening VOB database:
"hostname01.domain.com:/clearcase/vb001/vobs/VOB_core.vbs".
multitool: Error: Operation "remote_get_replica_properties" failed
("Boston"): error detected by ClearCase subsystem.
Cause
It is possible that a VOB is tagged to a correct hostname but a replica in the VOB family is using an incorrect hostname, such as hostname01.domain.com in the error message above.
If a remote IBM Rational ClearCase MultiSite host attempts an operation such as multitool chepoch or lsepoch against the "Boston" replica (in this scenario), the local db_server handling the request will get "hostname01.domain.com" for this replica and that db_server will fail to open the database, returning the db_server(9279): Error: Process not running on registry specified hostname (hostname01.domain.com).
Diagnosing The Problem
Use the following steps to show the discrepancy:
- Use lsvob to find the correct hostname of the VOB
cleartool lsvob -long /vobs/VOB_core
Tag: /vob/VOB_core
Global path: /clearcase/vb001/vob/VOB_core.vbs
Server host: hostname02.domain.com
Vob on host: : hostname02.domain.com
- Describe the VOB to determine the local replica
cleartool describe vob:/vobs/VOB-core
versioned object base "/vobs/VOB-core"
created 15-Jan-07.10:20:21 by User1
master replica: original@/vobs/VOB_core
replica name: Boston
- Use lsreplica to confirm the hostname of the local replica
multitool lsreplica -long Boston@/vobs/VOB_core
For VOB replica "/vobs/VOB_core":
replica "Boston"
host: "hostname01.domain.com"
identities: not preserved
permissions: not preserved
feature level: unknown
From the above output we can see that the server host listed for the VOB object in the lsvob output shows "hostname02.domain.com" while lsreplica for the local replica, "Boston", shows the host is "hostname01.domain.com."
Note: If you are unable to identify the VOB server that contains the replica which is causing the issue, the above steps may need to be run on every VOB server in question until the problem replica is found.
It can be difficult to track down the VOB and replica with the incorrect hostname as the db_server does not provide VOB information, it only provides a PID for the db_server process. However, if you are able to identify the replica hostname that needs to be corrected, the hostname can be changed.
The following forms of the above commands can be run to limit the output on UNIX and Linux systems:
cleartool lsvob -short -host hostname01.lexma.ibm.com -quick | awk
'{print "vob:"$0}' | xargs -l cleartool describe -fmt
"replica:%[replica_name]p@%n\n" | xargs -l cleartool describe -fmt
"%[replica_host]p\t%Xn\n" | grep -v hostname01.lexma.ibm.com
The command will list VOBs hosted on a system whose replica host does not match.
Resolving The Problem
To fix the problem, use the following command at the objects mastering replica to update the replica object with the correct hostname:
multitool chreplica -host <correct-host-name> <replicaname>
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21292002