There are a few of us in the local linux users group afflicted with this
problem, but my situation's the worst. And it's mine so I want to fix it
ASAP!

  I have two workstations and a firewall/router on a 100 Mbps ethernet;
there are two portables which are sporatically connected. Everything is now
running RH 6.1 (2.2.12-20 kernel). And this is when the problem started,
when I upgraded the server from 5.2 to 6.1.

  The client host quietly dies overnight, every few days. Always at night
and on a variable schedule (2-5 days). What I mean is that the system just
locks up. The screen (which is blanked automatically after a period of
quiescence) cannot be revived by pressing the shift key or trackball. A
crtl-alt-del reboot attempt fails. Only pressing the reset switch works. The
message which I can see in /var/log/messages (and sometimes on the screen
when it hasn't yet gone comatose) is: lockd: failed to monitor
<server-IP-address>.

  Everyone here is puzzled; we have a server at an elementary school which
does the same thing.

  Could this be nfs/knfsd related? If so, what do I do about it?  I've
turned off power management in the system's BIOS and disabled apmd in the
kernel. Makes no difference.

  When the client was running RH 6.0 and the server running RH 5.2, this did
not occur.

  I'd be very grateful for any insight into the cause of the problem and --
especially -- for any solutions. Not only is it distracting from business
and frustrating for me, but it keeps the daily backups from running via cron
jobs and causes other disruptions. I'd sure like to fix it once and for all!

Thanks in advance,

Rich

Dr. Richard B. Shepard, President

                       Applied Ecosystem Services, Inc. (TM)
              Making environmentally-responsible mining happen. (SM)         
                       --------------------------------
            2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
 + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | [EMAIL PROTECTED]


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to