Troubleshooting
Problem
This technote outlines some troubleshooting tips to help address IBM® Rational® ClearCase® view_server died on startup; marking it as down errors.
Symptom
When running cleartool setview on UNIX®, the following error is observed in the albd_log.
Error: server: view_server died on startup, marking it as down.
Cause
There are many reasons for this to happen, moving the view and NOT killing the view_server process, changing permissions, or like actions.
Resolving The Problem
TROUBLESHOOTING TIPS:
- cd to the storage directory (.vws directory)
- Check the ".pid" file.
This file should contain the UNIX process id of the active view_server process.
It should be owned by the view owner, writable only for owner and readable by all.
Display the indicated process: ps -fp `cat .pid`
Generally speaking you can just remove this file. If the above command finds a process that looks like a view_server for this view, then kill the process.
- Verify the permissions on the view storage directory (ls -la .)
-r--r--r-- view-owner view-prim-grp .access_info
-rw-rw-rw- view-owner view-prim-grp .compiled_spec
-rwxrwxrwx view-owner view-prim-grp .flexlmrc
-r--r--r-- view-owner view-prim-grp .hostname
drwx------ view-owner view-prim-grp .identity
-rw-r--r-- view-owner view-prim-grp .pid
drwxrwxrwx view-owner view-prim-grp .s
-r--r--r-- view-owner view-prim-grp .view
drwxr--r-- view-owner view-prim-grp admin
-rw-rw-rw- view-owner view-prim-grp config_spec
drwxrwxrwx view-owner view-prim-grp db
-r--r--r-- view-owner view-prim-grp readme.txt
-rw-rw-rw- view-owner view-prim-grp view_db.state
To generically correct problems in view storage permissions do:
/opt/rational/clearcase/etc/utils/fix_prot -force -root -recurse -chown view-owner -chgrp view-prim-grp <view-storage-dir>
cd into .identity and verify the permissions of the files (ls -l).
All files are zero bytes and owned by view owner.
Mandatory files - file group is view's primary group:
-r-S------ uid
-r----s--- gid
Optional files - corresponding to view's additional groups:
-r----s--- group.123
The number (123 in the example) is the UNIX GID of the additional group and the file's group should be (the name of) the additional group.
Commands to set these are:
chown view-owner *
chgrp view-prim-grp uid gid
chgrp view-add-grp-nnn group.nnn
chmod 4400 uid
chmod 2410 g*
- cat the view_db.state file. This file should only contain the lower case 'i' (echo i > view_db.state)
- grep view_server (ps -ef | grep view_server | grep view-storage-path-name). If one is running for this view, then kill it (kill -9 <pid>)
Note: Running cleartool endview -server <view-tag> does not always work in this situation since the view server is not accessible.
Related Information
[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"View: Dynamic","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"7.0;7.0.1;7.1;7.1.2;8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21133980