Netware 6.5 - NSS - NFS - CATIA CAN´t SAVE :-(
Michael Krzyzanski
as I see in this forum there are quite a lot of people asking about file
locks on NetWare 6.0 on NSS. This is not working and will not, that is the
answer from Novell about a week ago to us. I also found a post below about
hardlinks in NFS and Locks. As I read from the Mails Novell send us, they
are working on some patches for NFS on NW6.5. We have changed our enviroment
to NW6.0 some months ago and one of the targets was to let access our CATIA
V4 UNIX Stations the NFS Share on a Netware Cluster and let the CATIA V5 W2K
Stations access the same Share (Netware Client). We were very dissapointed
when we realized that the UNIX CATIA Stations can´t save any files to the
NFS Share. Even more bad the Flie LOCKS didn´t word. Answer from Novell was
to update all Cluster to NW 6.5.
We have now here a NW6.5 Server with an NFS Share. Everything seems to be
fine but when we try to save a file from the UNIX System to the NFS Share
via CATIA V4 we get the Error Access Memeber not found. On the Trace of XNFS
we have the Error Code:
100003.3.08 <CREATE> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 10004
(I paste the complete Trace bellow).
Do anybody know what the Error could mean or what the Errorcode 10004 mean?
We looked throught the Internet for some Information but we couldn´t find
anything about this Error :-(
aTdHvAaNnKcSe
Bye
Michael
The complete Trace looks like this:
100021.4.04 <> [TCP 10.2.100.94] RStatus 0 Accept 0
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.18 <FS STAT> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.18 <FS STAT> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.01 <GET ATTR> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 0
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.03 <LOOKUP> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 2
100003.3.08 <CREATE> [TCP 10.2.100.94] RStatus 0 Accept 0 NFS 10004
Onno Molenkamp
RFC 1813)
If would be probably more helpful to get a full packet trace (using
PKTSCAN.NLM, or ethereal/tcpdump on the unix box) of the NFS packets, to
see what flags are being used. Creating normal files (ie: no hard links,
fifos, sockets, etc) should work, with both the 6.0 and the 6.5 NFS daemons.
Did you try both NFSv2 and NFSv3?
Onno
PMa...@yahoo.com
- I think exclusive create is not supported and that's the reason for
getting this message.
- Try mounting over NFS version 2 and let us know how it goes.
Regards,
Madhan.
Michael Krzyzanski
as I recognize there is no posting of files allowed. Please try to download
here:
http://www.krzyzanski.de/server.cap
Bye
Michael
"Michael Krzyzanski" <michael_k...@hotmail.com> schrieb im Newsbeitrag
news:9VPPb.3579$P5....@prv-forum2.provo.novell.com...
> Hi,
>
> we tried to trace the traffic on the server. I attached the CAP File at
this
> posting.
> Very strange is, that the Client communicate with the server over NFS V3
and
> both seems to accept the connection. I also trace the write access to the
> UNIX NFS Share they are using now. There is even no one NFS Package only a
> TCP stream. How can this be :-( With NFS V2 is the same Problem (only the
> displayed message tells, that the Volume is full. But I can still copy
files
> with the terminal and create Files with vi etc.). On a traditional Volume
on
> a NW 6.0 SP3 Server with NFS V3 everything works fine. I will trace this
> also and post again when I have the File.
>
> Does anybody have some suggestions what we can do?
>
> aTdHvAaNnKcSe
>
> Bye
> Michael
>
>
> <PMa...@yahoo.com> schrieb im Newsbeitrag
> news:H%KPb.3491$P5....@prv-forum2.provo.novell.com...
Madhan
that's why it was working in Nw6. It would still be good to force mount
over nfs version 2, using nfsvers=2 or vers=2 option and see what
happens. Have the traces, let's see what that shows up.
Regards,
Madhan.
Michael Krzyzanski wrote:
> Hi,
>
> we tried to trace the traffic on the server. I attached the CAP File at this
> posting.
> Very strange is, that the Client communicate with the server over NFS V3 and
> both seems to accept the connection. I also trace the write access to the
> UNIX NFS Share they are using now. There is even no one NFS Package only a
> TCP stream. How can this be :-( With NFS V2 is the same Problem (only the
> displayed message tells, that the Volume is full. But I can still copy files
> with the terminal and create Files with vi etc.). On a traditional Volume on
> a NW 6.0 SP3 Server with NFS V3 everything works fine. I will trace this
> also and post again when I have the File.
>
> Does anybody have some suggestions what we can do?
>
> aTdHvAaNnKcSe
>
> Bye
> Michael
>
>
> <PMa...@yahoo.com> schrieb im Newsbeitrag
> news:H%KPb.3491$P5....@prv-forum2.provo.novell.com...
>
Michael Krzyzanski
we took some traces with NFS V3 & V2 on the NW 6.5 Server without the
possibility to save the File from Catia. But we recognized that the behavior
at NFS V2 is diffrent than on NFS V3. Also the Errormessage on the
Workstation is different. At NFS V3 you get the Message "NOT A MEMBER" and
at NFS V2 "DEVICE FULL".
We also made one test on NW 6.0 SP 3 NFS V2 Traditional File System
(everything works there fine).
There are three Files we captrured and packed into an archive. We also added
a screen shoot from the XNFS debug screen when we captured the NW6.5 NFS V2
traffic.
You can download the Archive from http://www.krzyzanski.de/Server_Traces.rar
If you know what is wrong with the NFS V2 Transfer it would be greate to
here from you. I think there is no way to enable the NFS V3 function with
Catia on NW 6.5, but if someone has an idea how we get both to run please
post.
aTdHvAaNnKcSe
Bye
Michael
"Madhan" <PMa...@Yahoo.Com> schrieb im Newsbeitrag
news:ds1Qb.588$vr5...@prv-forum2.provo.novell.com...
Michael Krzyzanski
Novell Support told me to implement these Patches:
http://support.novell.com/servlet/filedownload/ftf/nw65nssa.exe
http://support.novell.com/servlet/filedownload/sec/ftf/xnfs1.exe
We checked the Patches on our Testsytem. The Version that is set on the
Server is
XNFS.NLM 1.01.08 from 12.November 2003
The Version that is implemented in the Patch is:
XNFS.NLM 1.00 from 02.August 2003
We try both Versions. None works still the same Problem.
I checked some Newsgroups about CATIA and found an old posting about
Problems saving CATIA Files on SUSE Linux 6 with a simmilar Problem. The
Newsgroup tells, that the STATD and LOCKD were not running with root
privileges. The solution was a new kernel Version for SUSE Linux.
I will post when I find or hear something new.
Thanks for your support.
Bye
Michael Krzyzanski
"Michael Krzyzanski" <michael_k...@hotmail.com> schrieb im Newsbeitrag
news:7v9Qb.760$vr5...@prv-forum2.provo.novell.com...
Madhan
access them :( Can you post info on how to access them ? It might be
another 2-3 days before I can have look at it.
Thanks,
michael.k...@keiper.com
you can use Ethereal (www.ethereal.com) or better you use the Network
Chemistry Packetyzer (http://www.networkchemistry.com/products/packetyzer/)
The Packetyzer is based on Ethereal but it is better to follow the Traffic.
Better Try this one.
Thanks for your Support.
Bye
Michael