statd/lockd startup failure
ml at netfence.it
Tue Mar 1 06:48:08 UTC 2011
On 02/17/11 22:06, Andrea Venturoli wrote:
>>> seem to remember a similar problem I had a long time ago. I opted to
>>> use a consistent, not-used port and haven't seen the problem since
>>> (this was years ago, so I can't remember if the error you're seeing
>>> was identical to mine).
>>> rpc_statd_flags="-p 898"
>>> rpc_lockd_flags="-p 4045"
> I have:
> rpc_statd_flags="-p 918"
> rpc_lockd_flags="-p 868"
> Still statd occasionally fails to start.
> It might be that something else has already bound to port 918, though I
> don't know what.
> I'll check as soon as I have the chance.
It happened this morning: lockd could not start and I verified it was an
NFS mount which used port 868 as a client.
Now I'm trying the noresvport to mount_nfs...
More information about the freebsd-stable