lockd problems
- From: hendrik@xxxxxxxxxxxxxx
- Date: Fri, 3 Nov 2006 09:45:51 -0500
Now I get a lot of these messages
On Fri, Nov 03, 2006 at 08:02:09AM -0500, logcheck@xxxxxxxxxxxxxx wrote:
...
Nov 3 07:30:07 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
Nov 3 07:30:07 lovesong kernel: lockd: failed to monitor 172.25.1.11
It would appear that my lockd is not configured properly for an NFS
mount.
The issue is complicated by having the NFS mount bridge two
distributions -- as a result I'm not where where to ask questions, nor
how to translate advice about one system to another. I'm finding advice
on the Ubuntu sites to be a bit skimpy and optimistic.
The messages appear on lovesong, a Debian stable 32-bit Athlon system.
172.25.1.11 is an AMD-64 system running Ubuntu dapper for reasons
explained in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379480.
It's causing me trouble because monotone very legitimately insists on
locking its data base during transactions. That data base is
NFS-mounted. Although I have a workaround (to run monotone on
172.25.1.11), it is inconvenient, and will not work for file-locking
software that has not been ported to AMD-64.
Detailed documentation about how NFS and the lock daemon are *supposed*
to interact would be helpful, but I suspect I will need someone to
advise on diagnostic commands and help interpret results.
-- hendrik
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Prev by Date: Re: [OT] M$ collaborates with Suse
- Next by Date: Re: [OT] M$ collaborates with Suse
- Previous by thread: [OT] M$ collaborates with Suse
- Next by thread: Debian on an Asus A6JM laptop
- Index(es):
Relevant Pages
|
|
