ncpmount problem on SLES 1-SP3

SUSE Linux Enterprise Server SLES Configure-Administer
1

To whom it may concern

We are having a ncpmount mount problem that needs to connect to our 2 new GroupWise SLES11-SP3 ,OES11SP2 Servers for restores.The undermentioned is the following.

Starting kernel based NFS server:exportfs: /etc/exports [1]: Neither ‘subtree_check’ or ‘no_subtree_check’ specified for export “192.168.0.50/255.255.255.0:/opt/gwdata/gkrl”.
Assuming default behaviour (‘no_subtree_check’).
NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: /etc/exports:2: unknown keyword “no_root_sqaush”

mountdrpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
statd nfsdrpc.nfsd: address family inet6 not supported by protocol TCP

Could somebody please assist me.

Regards

2

On 09/01/2014 03:24 AM, plaubscher wrote:[color=blue]

We are having a ncpmount mount problem that needs to connect to our 2
new GroupWise SLES11-SP3 ,OES11SP2 Servers for restores.The
undermentioned is the following.[/color]

It’d help to see the command you are running to mount the remote directory
but this next error is not talking about NCP at all but instead NFS, so
I’m guessing you are using the wrong command somehow.
[color=blue]

Starting kernel based NFS server:exportfs: /etc/exports [1]: Neither
‘subtree_check’ or ‘no_subtree_check’ specified for export
“192.168.0.50/255.255.255.0:/opt/gwdata/gkrl”.
Assuming default behaviour (‘no_subtree_check’).
NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: /etc/exports:2: unknown keyword “no_root_sqaush”[/color]

If you are actually trying to use NFS, then no_root_squash (see spelling)
is the correct variable. Still, you said this was an NCP mount, not an
NFS mount, so I do not know why you would be doing anythin gin
/etc/exports right now.
[color=blue]

mountdrpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
statd nfsdrpc.nfsd: address family inet6 not supported by protocol TCP[/color]

I do not know what any of this is about, but since your title and initial
description mentioned NCP while your errors mention NFS, I’d start with
using the correct command/protocol and then post back results.

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…

3

Yes sorry the title should read nfs problem not ncpmount.Did check the spelling for squash.All my other SLES 11 SP1 nfs is working.

cat /etc/exports
/opt/gwdata/gkrldpo 192.168.0.50/255.255.255.0(rw,no_root_squash,sync)

  1. After restart NFS getting another error.

Shutting down kernel based NFS server: nfsd mountd done
Starting kernel based NFS server:exportfs: /etc/exports [1]: Neither ‘subtree_check’ or ‘no_subtree_check’ specified for export “192.168.0.50/255.255.255.0:/opt/gwdata/gkrl”.
Assuming default behaviour (‘no_subtree_check’).
NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: /etc/exports:2: unknown keyword “no_root_sqaush”

mountdrpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
statd nfsdrpc.nfsd: address family inet6 not supported by protocol TCP
sm-notify

4

Problem is solved took out IP version 6.I followed this TID https://www.novell.com/support/kb/doc.php?id=7011354 .

5

Good to hear; thank-you for posting back your results.

Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…