Cause
This message appears on an NFS client that requested a service from an NFS server
that has failing hardware. Often the message NFS read failed appears along with
this message. If the server were merely down or slow to respond, the NFS server
not responding message would appear instead. Data corruption on the server
system is possible.
Action
Because this message usually indicates server hardware failure, initiate repair
procedures as soon as possible. Check the memory modules, disk controllers, and
CPU board.
date time host rpc.cmsd[pid]: rpc.cmsd :
NFS mounted callog file Not Supported - user@host
date time host rpc.cmsd[pid]: rpc.cmsd :
NFS mounted callog file Not Supported - user@host
The calendars would have worked under the Solaris software versions including and
prior to 2.5.1, however.
Action
It has long been known that NFS-mounted calendars are not supported. The calendar
can be corrupted when more than one person uses the calendar at the same time. If
two rpc.cmsd daemons write to the callog file at the same time, the file becomes
corrupt. However, two rpc.cmsd daemons could be run simultaneously on the
Solaris 2.5.1 release, even though this is not a supported configuration.
With the Solaris 2.6 release, this concurrency is no longer an option. rpc.cmsd does
not allow the user to start a calendar that is NFS-mounted and produces the
previous error message.
This message appears on an NFS client that requested a service from an NFS server
that has failing hardware. Often the message NFS read failed appears along with
this message. If the server were merely down or slow to respond, the NFS server
not responding message would appear instead. Data corruption on the server
system is possible.
Action
Because this message usually indicates server hardware failure, initiate repair
procedures as soon as possible. Check the memory modules, disk controllers, and
CPU board.
nfs mount: Couldn’t bind to reserved port
Cause
This message appears when a client attempts to use NFS to mount a file system from
a server that has more than one Ethernet interface configured on the same physical
subnet.
Action
Always connect multiple Ethernet interfaces on one router system to different
physical subnetworks.
This message appears when a client attempts to use NFS to mount a file system from
a server that has more than one Ethernet interface configured on the same physical
subnet.
Action
Always connect multiple Ethernet interfaces on one router system to different
physical subnetworks.
nfs mount: mount: string: Device busy
Cause
This message appears when the superuser attempts to NFS mount on top of an
active directory. The busy device is actually the working directory of a process.
Action
Determine which shell on the workstation is currently located below the mount point,
and change that directory. Be wary of subshells (such as su(1M) shells) that could be
in different working directories while the parents remain below the mount point.
This message appears when the superuser attempts to NFS mount on top of an
active directory. The busy device is actually the working directory of a process.
Action
Determine which shell on the workstation is currently located below the mount point,
and change that directory. Be wary of subshells (such as su(1M) shells) that could be
in different working directories while the parents remain below the mount point.
NFS mount: /string mounted OK
Cause
While booting, the system failed to mount the directory specified after the first colon,
probably because the NFS server involved was down or slow to respond. The mount
ran in the background and successfully contacted the NFS server.
While booting, the system failed to mount the directory specified after the first colon,
probably because the NFS server involved was down or slow to respond. The mount
ran in the background and successfully contacted the NFS server.
Action
This is strictly an informative message to notify you that the mount process has
completed.
This is strictly an informative message to notify you that the mount process has
completed.
NFS mounted callog file Unsupported.
Cause
After installing the Solaris 2.6 software on a system, when users try to start their
calendars either with CDE’s calendar manager (/usr/dt/bin/dtcm) or
OpenWindows’ calendar (/usr/openwin/bin/cm), they see this dialog box:
Calendar :Informational - NFS mounted callog file Unsupported.
Your default startup Calendar file appears to be NFS mounted or
a symlink to the same. This is Not Supported.
Continue
The following error is displayed in the console window when the Continue button is
clicked:
After installing the Solaris 2.6 software on a system, when users try to start their
calendars either with CDE’s calendar manager (/usr/dt/bin/dtcm) or
OpenWindows’ calendar (/usr/openwin/bin/cm), they see this dialog box:
Calendar :Informational - NFS mounted callog file Unsupported.
Your default startup Calendar file appears to be NFS mounted or
a symlink to the same. This is Not Supported.
Continue
The following error is displayed in the console window when the Continue button is
clicked:
date time host rpc.cmsd[pid]: rpc.cmsd :
NFS mounted callog file Not Supported - user@host
date time host rpc.cmsd[pid]: rpc.cmsd :
NFS mounted callog file Not Supported - user@host
The calendars would have worked under the Solaris software versions including and
prior to 2.5.1, however.
Action
It has long been known that NFS-mounted calendars are not supported. The calendar
can be corrupted when more than one person uses the calendar at the same time. If
two rpc.cmsd daemons write to the callog file at the same time, the file becomes
corrupt. However, two rpc.cmsd daemons could be run simultaneously on the
Solaris 2.5.1 release, even though this is not a supported configuration.
With the Solaris 2.6 release, this concurrency is no longer an option. rpc.cmsd does
not allow the user to start a calendar that is NFS-mounted and produces the
previous error message.
No comments:
Post a Comment