I have a problem with "cleartool setcs -stream" command?
It generates the following error
cleartool: Error: Unable to copy "\\nyatc\rrs\view_store\gsm\jpillo\jpillo_atc_1.vws\config_spec" to "\\nyatc\rrs\view_store\gsm\jpillo\jpillo_atc_1.vws\config_spec.bak": Permission denied.
cleartool: Error: Unable to change configuration specification: Permission denied.
Note: I changed permission on config_spec but still the same result.
This is generally linked to a permission issue.
Check:
if you have at least access to that view storage shared directory:
dir \\nyatc\rrs\view_store\gsm\jpillo\
your CLEARCASE_PRIMARY_GROUP.
your creds:
<ClearCaseInstallation>/etc/utils/credmap yourClearCaseServer
that you are not part of more than 32 groups (see this IBM article)
that a simple cleartool edcs (from within the view) also fails
Related
I need some help. Two years ago I inherited the responsibilities of maintaining our ClearCase system which is extremely outdated and I have no previous experience working with it at all. Today, users are having problems checking out files from two of our ClearCase servers and I am not even sure where to begin. I have searched the internet to no avail. I ran the following commands to try and troubleshoot it but I am stuck now and I don't know where to go from here.
Below is what happends when the user tries to checkout a file:
cleartool co Makefile
Checkout comments for "Makefile":
.
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Unable to locate versioned object base with object id:"e2a51855.b3f511d3.ad28.00:01:80:8e:4e:e8".
cleartool: Error: Trouble finding the global definition for local type "development".
cleartool: Error: Unable to check out "Makefile".
I have looked around and can't seem to find out how to resolve this.
These particular servers are running an older version of RedHat (Linux 3.10.0-123); and the logs I found don't give me enough information to know what to do next. Our ClearCase version is 8.0.1.5
Below are the results of various commands I have run to try and troubleshoot the issue:
[vobadm#lgbuild3] cleartool desc /vob/admin_vob
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
Non-MVFS directory "/vob/admin_vob"
Modified: Thu 16 Dec 1999 03:10:58 PM EST
Protection:
User : vobadm : rwx
Group: eng : r-x
Other: : r-x
Finally, I read that the VOB may be locked, but this is what happens when I run the unlock command:
[vobadm#lgbuild3]$ cleartool unlock /vob/admin_vob
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Unable to access "/vob/admin_vob": error detected by ClearCase subsystem.
Per VonC, I ran the following commands and here is the results:
[vobadm#lgbuild3 log]$ ct descr -l vob:/vob/admin_vob
cleartool: Error: Unable to determine VOB for pathname "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Unable to determine VOB for pathname "/vob/admin_vob".
Any help or guidance as to where I should look at next would be greatly appreciated.
It depends on your version of ClearCase and OS (for ClearCase server and client), but the four main command you need to look at are:
cleartool describe
cleartool lsview
cleartool fix_prot
cleartool protectvob
First, you can describe your vob, to check its associated ACL (owner/group), as I did here:
cleartool descr -l vob:/vobs/vobtag
Then you can check the same for your user views, as in here:
cd /path/to/my/view
cleartool lsview -l -full -pro -cview
Depending on the rights you see, you might need to fix_prot the vob itself (maybe even protectvob if you need additional groups.
Or simply fix_prot the views to make them compatible with the main group of the Vob.
For the error:
cleartool: Error: Unable to determine VOB for pathname "/vob/admin_vob"._vob
You need to at least create a tag for that vob:
ct mktag -vob -tag /vob/admin_vob -pub -password clearcase -host yourVobServer -gpath /shared/path/to//vob/admin_vob.vbs /shared/path/to//vob/admin_vob.vbs
The first message had a clue that may be significant:
cleartool: Error: Unable to locate versioned object base with object id:"e2a51855.b3f511d3.ad28.00:01:80:8e:4e:e8".
You should run either
cleartool lsvob -long /vob/admin_vob
or
{cc install}/rgy_check -vobs
It is possible that the VOB got unregistered. It's not supposed to happen... But... You may get lucky and only need to run cleartool register -vob {vob storage path} or the equivalent with -host and -hpath if the VOB is on a NAS.
You should also look at the db_server logs on the VOB server to see if there are additional messages. The simplest way is go to the vob server host (ssh, local login, etc) and open /var/adm/rational/clearcase/log/db_server_log. Alternatively, immediately after you get the error on cleartool desc vob:/vob/admin_vob, run cleartool getlog -host {vob server name} db
That will at least get you started. Without knowing what's actually happening under the hood, I can't offer too many suggestions, and for various reasons dealing with my employment, I can't get into too much detail after we know, but I can at least offer pointers and other questions.
You're right that 8.0.1.5 is gloriously out of date. 8.0.1.x has been out of support since April 30th 2018. The current versions are 9.0.1.10 and 9.0.2.1(or 2). If you're also using ClearQuest, you'll have to move to 9.0.2.x to upgrade to the current release as CQ 9.0.1.0 is no longer available for download.
This issue is not related to the old version of CC, but you may need to work with support in order to resolve the issue, which may necessitate an upgrade to a supported release.
I am not able to set view on the server even though I have re-mounted the file system , getting below error :
$ cleartool setview view_name
cleartool: Error: Timed out trying to start view_server for view PATH
cleartool: Error: See view server error log and/or look for view_server problem on host Hostname
cleartool: Error: Couldn't set view tag tagename: error detected by ClearCase subsystem
First, try to avoid *enter code here: it spawns a subshell which is tricky for your current session and environment variables.
Then, check if the issue us the same when you simply try to start that dynamic view:
cleartool start <aDynamicViewName>
Typically, looking at the logs might tell you more about the issue:
cleartool getlog error *
cleartool getlog -host <clearcaseServer> view
(Remember: you had database timeout before)
I try to add to source control a file, and get:
Error adding 'M:\niyazmom_SYN_AUG_ASIA_NONASIA_WASHBOOK\bo_goit_synthetic_pb\Synfiny\Development\Executables\MDI\frmRegionMappingBrowser.frm' to source control.
Error from VOB database: "\bo_goit_synthetic_pb".
How can I avoid/diagnose this error?
It depends on your exact ClearCase version and on the full error message.
For instance, this documentation mentions:
cleartool: Error: Error from VOB database: "\test_vob".
cleartool: Error: Trouble opening VOB database: "\test_vob".
cleartool: Error: Not a vob object: "vob:\test_vob".
The main point to check is the various logs (both local and on the clearCase server) using cleartool getlog.
Performed fix_prot on a VOB database dump from Linux into Windows. Fix_prot said the re-protection was complete. So, I tried to run a cleartool reformatvob - load and receive the following: cleartool: Error: Permission denied: not VOB owner or priveleged user.
cleartool: Error: Trouble loading versioned object base .
Don't understand why it's still not letting me load the VOB.
It is one limitation of the cleartool reformatvob command:
You must have one of the following identities:
VOB owner
root (UNIX and Linux)
Member of the ClearCase administrators group (ClearCase on Windows)
I usually perform a load as root (on Linux), or, in your case on Windows, as a member of the ClearCase admin group.
Then I do a cleartool protectvob to change the vob ownership.
In that order, it works.
I have received really weird error while sync of replicas:
$ /usr/atria/bin/multitool syncreplica -import -receive
multitool: Error: Permission denied: not VOB owner or privileged user.
multitool: Error: Can not import into vob:/vobs/***, permission denied.
multitool: Error: INTERNAL ERROR detected and logged in "/var/adm/rational/clearcase/log/error_log".
multitool: Error: Permission denied: not VOB owner or privileged user.
multitool: Warning: Could not disable replay in vob: Operation not permitted.
Does anyone know what could be the root cause of the issue?
vobadm is owner of all files under /usr/atria.
Being the owner for the file has nothing to do with being the owner of the vob.
Do a cleartool descr -l vob:\yourVob to see who the owner is (you might also have to use multitool chreplica –npreserve, as described in "Preservation Mode").
A cleartool protectvob can change the owner of a vob (make sure the vob is locked on all site, though, to avoid race condition similar to this one)
The Op confirms:
the issues is resolved by changing the ownership from "nobody" to "vobadm"