Unable to create session data file /var/adm/rational/clearcase/ccweb/me/session.dat Operation not permitted

This technote explains why the error Unable to create session data file "/var/adm/rational/clearcase/ccweb/me/session.dat": Operation not permitted. may occur when attempting to login from an IBM® Rational® ClearCase® Remote Client (CCRC)
Symptom

The following error is reported when a user attempts to log in via CCRC:

Unable to create session data file "/var/adm/rational/clearcase/ccweb/me/session.dat": Operation not permitted.

The user has the appropriate login credentials but still can't login.


Cause

The user may have changed groups which was not properly reflected in the session.dat file which CCRC needs to access.

When looking at the session.dat file:


    me@computer:/var/adm/rational/clearcase/ccweb/me> ls -al

    total 28

    drwxrwxr-x 5 me users 4096 2008-07-10 06:46 .

    drwxrwxrwx 5 root root 4096 2008-03-07 13:33 ..

    -rw------- 1 me users 789 2008-03-17 11:33 session.dat


-rw-r--r-- 1 me pdUsers 7 2008-07-10 06:46 session.dat.pid


In the sample output above we see that the session.dat file has a group of "users" and in this example it was determined that this user was once in the users group. The user changed to the group "pdUsers" at some point. When CCRC tried to open the session.dat file, as the groups were wrong, it created a session.dat.pid file. This still do not allow for the user to login.

Note: Every CCWeb and CCRC user has their own session.dat file that contains references to their Web views. The session.dat files are stored in the following directory (by default) on the CCRC/CCWeb server:

  • Windows: C:\Program Files\Rational\ClearCase\var\ccweb\

  • UNIX and Linux: /var/adm/rational/clearcase/ccweb/

Resolving the problem

The group of the session.dat file needs to be changed to the proper group for the user.

In the above example, running chgrp on session.dat to change to the pdUsers group, as follows:

chgrp pdUsers session.dat

Upon the next login attempt the user was able to successfully login.

No comments:

Post a Comment