Error on add to source control - Unable to transfer a file: error detected by clearcase subsystem

1
votes

We are setting up new servers at CC 8.1.1.11 and going through basic tests.

From a CC Explorer client we try and add a simple .txt file to source control and get the error

Error adding "path to filename.txt" to source control Unable to transfer file : 
error detected by Clearcase Subsystem.

Selecting Ok on the error pop-up we can then see the "Green Tick" against the file showing it checked out but when we try to check in we get the same error.

In the mvfs log on the client machine we see the following

Fetch cleartext view=viewname vob=\vobname dbid=0x43 - I/O error
See view log on  view server for more info.

View Log on view Server -

Error: view_server.exe error unable to construct cleartext for object "0x43" in vob "path to vob" 
Error detected by clearcase subsystem
Error unable to transfer a file.

Client machine and view server are windows. Vob server aix
No significant errors when running ClearCase doctor.

How can I avoid this error?

3
clearcase
What is the config spec of your view? - VonC
I'm using a dynamic view with cs of element * CHECKEDOUT element * /main/LATEST. so just the standard basic config spec. I'll check through the other points and update. Thanks - D Beange

3 Answers

1
votes

All, Thanks both for the input. The issue resolution was -

  • samba was missing username mapping to map the albd account to the vob owner account.
  • In smb.conf vobstore section was updated to have the write list group defined with an @ so that the group did not need to be the users Primary Group.
  • Getting Samba and nmbd properly stopped and started not just restarted.
  • Disabling CCFS on both the client and view server through the clearcase control panel, then stopping and restarting Clearcase "As Administrator" not just as an account with admin permissions.
0
votes

The phrase "unable to transfer" is a key indication that the client application (cleartool.exe) and the view server process are using CCFS to get to the pools.

If this just started happening, please verify that your user account still maps to the unix server correctly. (...\clearcase\etc\utils\credmap server_name) @Vonc's lsview option will also tell you the view's user and group credentials, which can also be an issue -- particularly for CCFS transfers.

You may also want to see what happens on disabling CCFS on the client host and view server host (ClearCase control panel, options page). Be aware that this may merely change the nature of the failure if the albd account on Windows is not able to directly access the pools.

0
votes

As mentioned in this thread

The usual reason is access rights in the cleartext pool (down from the 'c' directory in the vob storage).

But I recently got this in conjunction with a clearer report in the vobrpc log (I think), for 'group not declared in the vob' (or similar).
The user was actually work as root, and his group was 'other'. Although he was allowed to write to the (local) cleartext pool, the type_manager would refuse with this (misleading?) error...

So double-check your vobrpc logs, and check your CLEARCASE_PRIMARY_GROUP (whose group needs to be part of the primary or secondary groups of the Vob involved with those files)

Check also the protections associated with your view:

cd /path/to/my/view 
cleartool lsview -l -full -pro -cview