IBM Support

Operation "view_ws_is_ws_view" failed: view storage directory or control files unavailable

Technote (troubleshooting)


Problem(Abstract)

This technote provides troubleshooting tips related to the IBM Rational ClearCase error, Operation "view_ws_is_ws_view" failed: view storage directory or control files unavailable, whose views are stored on Microsoft Windows, Linux and UNIX.

Symptom

Any of the following symptoms may be observed:

  1. Views stored on a UNIX/Linux server cannot be set (cleartool setview) without resulting in the following error:

    cleartool: Error: Operation "view_ws_is_ws_view" failed: view storage directory or control files unavailable --
    additional information may be present in the view server host's view log.
    Starting myview view...


    Note: An entry similar to that above appears in the view_log as well.
  2. Attempting to start a view results in the following:
    [root@aoiyuki test.vws]# cleartool startview test

    cleartool: Error: Operation "view_ws_is_ws_view" failed: view storage directory or control files unavailable --

    additional information may be present in the view server host's view log.


    The following will appear in the view server's view log:


    [root@aoiyuki test.vws]# tail /var/adm/atria/log/view_log

    2008-05-13T13:52:06-04:00 view_server(7447): Ok: View server addr = 0, port= 32918

    2008-05-13T13:52:06-04:00 view_server(7447): Ok: View server addr = 0, port= 40975

    2008-05-13T13:52:06-04:00 view_server(7447): Ok: Db initialized

    2008-05-13T13:52:06-04:00 view_server(7447): Ok: Db initialized

    2008-05-13T13:52:06-04:00 view_server(7447): Ok: Using 512000 bytes of cache

    2008-05-13T13:52:06-04:00 view_server(7447): Ok: Using view /cc_stg/viewstore/root/vroot.vws, on host: aoiyuki

    2008-05-13T13:53:03-04:00 view_server(7462): Error: Unable to open .pid: Permission denied

    2008-05-13T13:53:03-04:00 view_server(7462): Ok: View server addr = 0, port= 32925

    2008-05-13T13:53:03-04:00 view_server(7462): Ok: View server addr = 0, port= 38904

    2008-05-13T13:53:03-04:00 view_server(7462): Warning: Temporary server starting for unusable view at '/cc_stg/viewstore/testuser/test.vws'


Cause

For Symptom 1
There are various possible causes related to this error:

    • A view was moved from one system to another and the new file system was not mounted to allow setuid operation (UNIX/Linux only).

    • The uid and or gid files from the .identity directory on UNIX/Linux are not available.

    • The view was restored from a backup and the uid and gid are misprotected. On UNIX the .identity file doesn't have the correct setuid bits set.
    • There was a power failure and the view server process is in a confused (or stale) state.

    • There may be an application conflicting with the ClearCase view_server process (such as Data Replication Software).
For Symptom 2
  1. This error can appear if a view server has been restarted and the .pid file is left behind in the view storage directory.

  2. This may also be the result of the ClearCase Administrators group being improperly set in the Windows registry.

Diagnosing the problem

Steps to diagnose:

  1. UNIX & LINUX ONLY: If a view was moved from one system to another, check whether, on the new file system, the view is mounted to allow setuid operation or not. This can be tested by listing the mount options for the file system (using the UNIX mount command, with no options). If the setuid operation is disallowed it will be seen as a "nosuid" flag in the mount options for that file system.

    For example, on HP-UX, the following file system has setuid disallowed:
    % mount
    /tmp on /dev/vg00/lvol4 nosuid on Fri May 19 09:20:25 2002


    If the setuid is disallowed it must be turned on for that file system. This involves remounting it or a choosing a different location for the view storage.

    For more details on changing UNIX mount options, review the UNIX man pages for 'mount' and 'mount_<fstype>' where <fstype> is 'hfs', 'nfs','jfs'.

  2. UNIX & LINUX ONLY: Recreate the uid and or gid files and set the appropriate setuid bits.
    The appropriate setuid bits for .identity file should be the following:

    -r----s--- gid
    -r-S------ uid


    If the setuid bits entry was set incorrectly, it can be fixed by running a UNIX chmod command:

    % chmod 4400 uid
    % chmod 2410 gid


    Refer to technote 1204876 Setting the UNIX setuid and setgid bits in a ClearCase VOB or view storage directory for further information.
  3. WINDOWS, LINUX and UNIX: Run the cleartool recoverview command to try and restore the view to its normal state. Review the ClearCase Reference Guide on the topic of recoverview (cleartool man recoverview) for more information.

  4. WINDOWS, LINUX and UNIX: Reprotect the view storage by running the fix_prot utility. Refer to technote 1142606 for more information on how to properly run the ClearCase fix_prot utility.

  5. WINDOWS ONLY: Remove any applications conflicting with ClearCase processes. One such application is WANSync by XOsoft Corp. WANSync is a Data Replication Software Suite that replicates data from one server to another for Data Recovery.

Resolving the problem

Solution for Symptom 1

If there is a stale view server process left over from a view which is not currently set, you can kill the view_server process and try setting the view.

WORKAROUND:

If either steps 3 or 4 above do not help and the view still gives errors, then there is no resolution to repair the existing view and it is recommended to remove the view and recreate it.

There may be files in the view that must be recovered or checked in before removing the view. The following steps may provide a temporary solution to perform the necessary cleanup operations to prevent loosing any data when the view is removed:

  1. Find a known good view and cd to the view storage directory (.vws)

  2. Copy the .access_info file from the good view into the corrupt view.

  3. Try to set into the view and perform the necessary operations (copy view private or checkin elements) before removing the view.

    Note: If this workaround does not allow you to set into the view, try repeating step 4 under Diagnosing the problem. If that still fails, the view is unusable and can only be restored from backup (if applicable) or removed.

Solutions for Symptom 2

  1. If the view is a dynamic view, you will need to remove the current view process by either running cleartool endview -server or by killing the view server process manually.

    Otherwise or afterwards, you will need to remove the .pid file from the view storage directory.
  2. Ensure that the following Windows registry key is set to the proper ClearCase administrators group name:

    32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase\CurrentVersion\ClearCaseGroupName

    64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Atria\ClearCase\CurrentVersion\ClearCaseGroupName

    Refer to these sections of the IBM Rational ClearCase Administrators Manual for further details:

    Privileged Users and Groups
    Domain User and Group Accounts

Document information

More support for: Rational ClearCase
View: Dynamic

Software version: 7.0, 7.0.0.1, 7.0.0.2, 7.0.1, 7.0.1.1

Operating system(s): AIX, HP-UX, IRIX, Linux, Solaris, Windows

Reference #: 1131145

Modified date: 16 March 2010


Translate this page: