Derrick J Brashear wrote: >On Wed, 1 Dec 2004, David Thompson wrote: > >> time 962.599815, pid 21833: Open 0x422de2c4 flags 0x0 >> time 962.599815, pid 21833: Open 0x422de2c4 flags 0xf423f >> time 962.599815, pid 21833: Analyze RPC op 13 conn 0x2128b4c0 code 0xd user >> 0x417529fa >> time 962.599815, pid 21833: Returning code 13 from 1 >> time 962.599815, pid 21833: Returning code 13 from 3 > >HandleFlock is 1 >afs_lockctl (HandleFlock's caller) is 3. > >both should not be CheckCoding, but that's not really the problem. > >I assume you're hitting the code which either calls over the network to >set or release a lock, and the fileserver is telling you to piss off. >on the clients, tcpdump -vv -s 1500 port 7000 >and then run your test. >
The command I used on the clients was: tcpdump -vv -s 1500 port 7001 ^^^^ Hope that's right... Box 1 (success): (there is no data. No packets across the wire.) Box 2 (failure): 14:57:52.434114 tortoise.cs.wisc.edu.afs3-callback > asok.cs.wisc.edu.afs3-fileserver: [udp sum ok] rx data cid b6ced414 call# 39 seq 1 ser 75 <client-init>,<last-pckt> fs call setlock fid 2004136721/202/3715 (48) (DF) (ttl 64, id 35853, len 76) 14:57:52.434550 asok.cs.wisc.edu.afs3-fileserver > tortoise.cs.wisc.edu.afs3-callback: [udp sum ok] rx abort cid b6ced414 call# 39 seq 0 ser 43 fs reply setlock error #13 (32) (DF) (ttl 254, id 10786, len 60) Dave _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info