lockd: cannot monitor
I'm having trouble, probably with locking. logcheck reports:
> This email is sent by logcheck. If you wish to no-longer receive it,
> you can either deinstall the logcheck package or modify its
> configuration file (/etc/logcheck/logcheck.conf).
>
> Security Events
> =-=-=-=-=-=-=-=
> Sep 23 10:08:45 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> Sep 23 10:08:45 lovesong kernel: lockd: failed to monitor 172.25.1.11
> Sep 23 10:08:45 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> Sep 23 10:08:45 lovesong kernel: lockd: failed to monitor 172.25.1.11
> Sep 23 10:08:45 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> Sep 23 10:08:45 lovesong kernel: lockd: failed to monitor 172.25.1.11
> Sep 23 10:08:46 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> Sep 23 10:08:46 lovesong kernel: lockd: failed to monitor 172.25.1.11
> Sep 23 10:08:46 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> Sep 23 10:08:46 lovesong kernel: lockd: failed to monitor 172.25.1.11
> Sep 23 10:08:46 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> Sep 23 10:08:46 lovesong kernel: lockd: failed to monitor 172.25.1.11
> Sep 23 10:08:55 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> Sep 23 10:08:55 lovesong kernel: lockd: failed to monitor 172.25.1.11
> Sep 23 10:08:55 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> Sep 23 10:08:55 lovesong kernel: lockd: failed to monitor 172.25.1.11
>
> System Events
> =-=-=-=-=-=-=
> Sep 23 10:08:45 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:45 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:45 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:46 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:46 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:46 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:55 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:55 lovesong kernel: lockd: cannot monitor 172.25.1.11
and I think I'm also having (probably related) locking problems. The
following is from a discussion of woe I encountered while building
monotone 0.30:
> > Looking at the output, the consistent problem seems to be that the data base is locked.
>
> Which is strange, because the database in question is a temporary one
> that was just created a few milliseconds before.
>
>
> > mtn found at /farhome/hendrik/install/monotone-0.30/mtn
> ^^^^^^^
> But you probably are running on NFS, and your NFS server has broken
> locking that always fails, is my guess.
Now lovesong is running Debian etch (that's the machine the monotone
compilations and test suite were run on, and the machine generating
all the messages); whereas the NFS server holding all the files
(/farhome) is an AMD 64 running Ubuntu dapper drake.
I suspect it's a networking problem involving the lock demon.
I've googled, have found a number of places where the problem
was reported, but none so far says what to do to solve it.
-- hendrik
Reply to: