Re: Problems with statd and lockd

[Bernd Schubert <bernd-schubert@web.de>]

On Saturday 05 April 2003 16:27, Trond Myklebust wrote:
> >>>>> " " == Bernd Schubert <bernd-schubert@web.de> writes:
>      > we also see those messages when we use the rpc.statd from
>      > debian packages. I think the debian nfs-utils packages got
>      > "--enable-secure-statd" as configure option. After recompiling
>      > the nfs-utils without this option and starting the new
>      > rpc.statd on the clients, those messages should disappear, even
>      > without restarting the nfs-server.  (I discovered this odd
>      > behaviour by accident.)
>
> --enable-secure-statd is there for a good reason. I wouldn't recommend
> that anybody turn it off. In any case, if that is the problem, then
> you should see a warning from 'statd' in your syslog (assuming you
> have enabled 'warn' messages in syslog.conf).
>
> Cheers,
>   Trond
>

Hello,

here are the entries from our /etc/syslog.conf about warnings:

*.=info;*.=notice;*.=warn;\
        auth,authpriv.none;\
        cron,daemon.none;\
        mail,news.none          -/var/log/messages

So I think warnings are enabled. Recently the self-created nfs-utils packages 
(with disabled --enable-secure-statd) got replaced by an automatic update. 
Some time afterwards our clients began to give those messages (here as 
dmesg-output):

statd: server localhost not responding, timed out
nsm_mon_unmon: rpc failed, status=-5
lockd: cannot monitor <server IP>
lockd: failed to monitor <server IP>

So on our systems not the server, but the clients are reporting those 
messages. Though I have to admit that our server is also running nfs-utils 
without secure-statd support, but as much as I can remember there where 
similar messages on the server when secure-statd was enabled.

The /var/log/messages has this entries: 

Apr  5 15:28:16 maxwell kernel: statd: server localhost not responding, timed 
out
Apr  5 15:28:16 maxwell kernel: lockd: cannot monitor <server IP>
Apr  5 15:28:16 maxwell kernel: lockd: failed to monitor <server IP>

What other messages do you expect ?

As soon as I stop the debian-statd and start the new statd (that has 
secure-statd disabled), those messages disappear.
Furthermore, some programs as e.g. KDE have some problems to run when those 
messages appear (our home directory is served by this server).

What problems can be caused by a statd without the secure option ? 


Thanks in advance,	
	Bernd


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs