AllExperts > Experts 
Search      

Sun Operating System

Volunteer
Answers to thousands of questions
 Home · More Questions · Answer Library  · Encyclopedia ·
More Sun Operating System Answers
Question Library

Ask a question about Sun Operating System
Volunteer
Experts of the Month
Expert Login

Awards

About Us
Tell friends
Link to Us
Disclaimer

 
 
 
 
About Kenneth Gullberg
Expertise
Experienced unix admin, Nis+, Clearcase, Veritas, Legato, Sendmail, etc etc.

Experience
I work as senior unix system specialist

Organizations
Centus

 
   

You are here:  Experts > Computing/Technology > Focus on PC Support > Sun Operating System > Solaris error message

Topic: Sun Operating System



Expert: Kenneth Gullberg
Date: 3/26/2001
Subject: Solaris error message

Question
Hi!
I'm a real newbie in the computer field (have only been in it less than a year). I recently got a good buy (?) on a Sun SPARC5 work station (I believe it's either Solaris 5 or 7 that's loaded on it). After it boots up, I get the following error message "rpc lockd. cannot contact status monitor". This error message cascades diagonally across the screen, and the system is completely locked up. Any thoughts on this? Thanks! Shawn R. Daniel

Answer
Hi!

On bootup, a machine might display the following error
message:

         rpc.lockd: cannot contact status monitor!

The machine will complete the boot process, and a login
prompt will appear.  It is possible to login and to work,
but the message will continuously be displayed on screen.
Problem Solution Top

The error message tells us that rpc.lockd cannot
communicate with rpc.statd, the status monitor.  The
rpc.lockd daemon needs the rpc.statd daemon for monitor
services.

To solve:

1. Check to see if both rpc.statd and rpc.lock are running.
  Issue the command "ps -aux | grep rpc" to view the rpc
  processes that are running.

        vanda% ps -aux | grep rpc
    root       119  0.0  0.0   56    0 ?  IW   Mar  4  0:00 rpc.mountd -n
   root       127  0.0  0.0   52    0 ?  IW   Mar  4  0:00 rpc.bootparamd
    root       129  0.0  0.0   52    0 ?  IW   Mar  4  0:00 rpc.statd
   root       135  0.0  0.0   84    0 ?  IWMar  4  0:00 rpc.lockd

2. If both processes are running, check the network
  connection by issuing the command:

             ifconfig -a

The output should look something like this:

        le0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>
   inet 129.145.114.12 netmask ffffff00 broadcast 129.145.114.0
   lo0: flags=49<UP,LOOPBACK,RUNNING>
   inet 127.0.0.1 netmask ff000000

If the output is different, check the /etc/hosts and
/etc/hostname.le0 entries.  Reboot the machine after
making any changes.

// Kenneth  

Add to this Answer    Ask a Question



  Rate this Answer
   Was this answer helpful?
Not at allDefinitely              
   12345  

     
About Us | Advertise on This Site | User Agreement | Privacy Policy | Help
Copyright  © 2008 About, Inc. About and About.com are registered trademarks of About, Inc. The About logo is a trademark of About, Inc. All rights reserved.