First, thanks to all those who responded. Most of the replies were from those
running Solaris 1.x.y. No one quite nailed the solution.
While waiting for Sun to call back, I happened upon a workaround to the
problem. It seems that /usr/openwin/bin/rpc.cmsd looks for the existence of
/usr/spool/calendar/.lock.${hostname} before starting. If the file exists, it
assumes rpc.cmsd is currently running and immediately exits. I guess the
".lock" file is left around in between reboots/crashes which means I have
to remove the ".lock" file by hand and restart rpc.cmsd.
My original posting (below) stated that rpc.cmsd WAS running on the server.
In some cases it is running but not talking. In this case, it never even
started running.
Thanks to:
bern@[TI.]Uni-Trier.DE (J. Bern)
Jean-Christophe.Touvet@inria.fr
rich_b@oldham.gpsemi.COM
louis@meg.meg.saic.com
danny@ews7.dseg.ti.com
lcollera@amgen.com
meystma@duvm.ocs.drexel.edu (Michael A. Meystel)
Original post:
> OK I give up!
>
> I have been fighting with this problem off and on since I installed Solaris 2.3.
> I have all the pertinent patches as of May 23. None of the patches directly
> addressed Calendar Manager as far as I know.
>
> The problem is that Calendar Manager is not talking to the rpc.cmsd daemon
> which IS running on the server. Usually I can workaround the problem by
> rebooting the Calendar Manager server machine, but this is becoming tiring.
> Sometimes I will take the server down for maintenance and upon reboot, I get
> the familiar "rpc.cmsd is not responding..." message when users start up
> Calendar Manager. Sometimes I have to reboot the machine 2-3 times to get it
> to work.
>
> There MUST be a better way. Please let me know if you know of the way.
Steve.
---
Steve Kirkpatrick | Steve.Kirkpatrick@artecon.com | Artecon, Inc.
MIS Group Leader | (619) 431-4478 (Voice) | 6305 El Camino Real
| (619) 931-5527 (FAX) | Carlsbad, CA 92009
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:03 CDT