Joseph Loo wrote:
On Mon, 2007-11-26 at 16:56 -0800, Linda Walsh wrote:
I'm trying to see why mountd appears to be
dying. Haven't used nfs4 enough to know "normal", but I see
4*[nfsd] but only 1 [nfsd4]. Not sure if that is right or
not...
Did you enable the server on startup? You can enable the nfs server to
start on run level 5. YAST->System->system services (run level).
Your exports looks okay.
Remember firewalls will block the nfs server being access from the
client.
----
Problem is(was) in the "rpc.mountd" included in suse10.3.
It was dying shortly after any client did an "ls /net/<server>" of the
server with err:
"rpc.mountd: symbol lookup error: rpc.mountd: undefined symbol:
blkid_probe_all_new"
I "backgraded" the rpm to the nfs-utils from suse10.2 and
it's now working. (>2GB files visible now as well)
So initial problem was I had 'some' user-space nfs-server that
didn't support the >2GB files, then tried nfs-server rpm from 10.3 -- that
led to an undefined symbol error. So I've installed nfs-utils from
suse10.2 and its now working.
Thanks for the help. Wouldn't have thought to try /net/server
as a debug step. To find the error message, I finally ran rpc.mountd
in foreground with debugging messages turned on.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
