ClearCase ERRORs

[Sara Smith]

We are running HP 10.20 on a 800 server, installed a new monitor and now ClearCase will not start. We have been talking with Rational about Clearcase for 4 days and they have NO idea!!!
Get this after #/sbin/init.d/atria start
ClearCase daemons: albd_server lockmgr
mount:cannot determine file system type for /view
Trouble mounting the viewroot "/view"
/usr/atria/etc/mvfslog: unable to open view root:not a ClearCase object
Trouble setting MVFS kernel log file to /var/atria/log/mvfs_log
Mounting public VOBs...
cleartool:Error:The MVFS file system is not installed or not loaded, or the 'viewroot' is not mounted or is inacessable: not a ClearCase object.
Trouble mounting public VOBs

[Bill McNAMARA_1]

can you try to mount /view

check for it in /etc/fstab
and compare that to the output of mount -p

Later,
Bill

[Sara Smith]

I tried to mount it but no such luck

[Denver Osborn]

Would you also be able to provide the mount syntax being used from command line or the clearcase script?

What error was returned when mounting it?

Also provide the output of this command;

fstyp -v /dev/vg_name/rlvol_name

[Angus Crome]

I haven't touched Clearcase in about 3 years now, but I remember having to get the /vob directory mounted (usually from some other server via the proprietary mvfs filesystem). I can't remember if /vob needed to be mounted before /view or vice/versa. Anyway, if this is your view server, then a fresh restart of the kernel (translated as reboot) should fix it. If it is a client, then you might have to deinstall and reinstall the atria software to get it back.

One last thing, make sure you have nproc and maxuproc set high enough. I remember on the SGI platform that nproc defaulted to 384 and we used to get conflicts with the really small instance of oracle that co-incided, and would run the number of processes up pretty high. That would generally cause problems with atria if we tried to stop and restart it.

[Timothy Butler]

I hope this is too late for the original poster, but that is a known failure when one of the HP patches required by ClearCase has not been installed. The release notes will have more detail.

(I'm following up just in case someone else searches on that same error.)