请各位大虾帮忙分析一条报错信息，谢谢！

秦风

重起机器后，得到以下信息，大家帮忙看看；

"Calendar error

rcp.cmsd is not responding for your user name.
Make sure the inetd process is running and the entry in inetd.conf for rcp.cmsd is correct for your host.
User name:root,Hostmc

unable to open callog file.Make sure the inetd.conf for rpc.cmsd
iscorrect for your host"

bear

sunsolve 有2个帖子有点联系，你看看
============================================
Problem Statement: Top

When invoking dtcm, a user is getting an error message in a popup window:

     rpc.cmsd not responding for user@host
     Make sure the inetd process is running
     and the entry in /etc/inetd.conf for
     rpc.cmsd is correct on host
                Continue

Selecting <Continue>; dismisses the popup and the dtcm
window comes up. But user could not use the calendar.

However, root has no problem.

Resolution: Top

Here are the steps that were followed to resolve this problem:

- The callog file for the user and /var/spool/calendar have the
  correct permission and ownership (SRDB 4775).

- /etc/inetd.conf has correct entry for rpc.cmsd and modifying
  it to include full path /usr/dt/bin/rpc.cmsd (as shown below)
  does not resolve the problem

      100068/2-5 dgram rpc/udp wait root /usr/dt/bin/rpc.cmsd
      /usr/dt/bin/rpc.cmsd

- rpc.cmsd -d shows this:
       rpc.cmsd: ping
       rpc.cmsd: ping
       cms_open_calendar_5_svc called
       sending host: SPECTRUM (SPECTRUM)
       rpc.cmsd: No space left on device

- /var/adm/messages states that / is full.- Clean up root partition

- Remove any /var/spool/calendar/.lock.$USER files  

============================================
Problem Statement: Top

On a Solaris[TM] 2.x system, when attempting to start /usr/openwin/bin/cm,
the user receives the following in a popup window:

        rpc.cmsd not responding for user@host
        Make sure the inetd process is running
        and the entry in /etc/inetd.conf for
        rpc.cmsd is correct on host
                Continue


Calendar Manager does come up, but does not contain the correct calendar.

What could be causing this problem?Resolution: Top

This error is generated if Calendar Manger ( /usr/openwin/bin/cm )
can not access/find the specified calendar.

If the user was trying to reach a calendar called user1@machine1,
then maybe machine1 does not exist, or it is not in the local machines
/etc/hosts file or NIS/NIS+ hosts map.

To find out if this host exists, use the following command:

        % ping host1

If the machine is really out there on the net, maybe there is a problem in
your /etc/hosts file or NIS/NIS+ hosts maps.  Either the host does not
have an entry, or the entry is incorrect.

The following commands can be used to check the host entry in /etc/hosts or
your NIS/NIS+ hosts map.

        - for /etc/hosts:

                % more /etc/hosts | grep <host>;

        - for NIS:

                % ypmatch <host>; hosts

        - for NIS+:

                % nismatch <host>; hosts.org_dir

If modifications needed to be made in your NIS/NIS+ maps, please don't forget
to remake the maps.


For more information, please see:

        - man cm
        - man rpc.cmsd
        - InfoDoc 12319: Explanation of how Calendar Manager works.
        - SRDB 12320: Basic Calendar Manager trouble shooting tips.