> On Mon, 25 Feb 2013 22:35:09 +0200 (EET) > [email protected] wrote: > >> Any particular log you have in mind? > > No, I don't know if any log provides the error I was looking for. I > intended for you to run ls, which you did, so thanks! > >> In Nautilus (file manager), it doesn't give any error message. It >> behaves >> as if the parent directory is empty. On command line, >> >> $ls >> cannot access [directory name]. Connection timed out >> $cd [directory name] >> Connection timed out >> >> The time out happends immediately, BTW. > > Okay, good. One possibility here is that the fileserver for userB is not > accessible over the network from the WAN network. Do you see any > messages from 'afs: ' in kern.log or `dmesg`?
In dmesg, afs was not mentioned. kern.log: (tries to contact local ip) Feb 25 20:40:45 host-name kernel: [ 13.803475] openafs: module license 'http://www.openafs.org/dl/license10.html' taints kernel. Feb 25 20:40:45 host-name kernel: [ 13.803477] Disabling lock debugging due to kernel taint Feb 25 20:40:45 host-name kernel: [ 13.832616] intel8x0_measure_ac97_clock: measured 54242 usecs (6239 samples) Feb 25 20:40:45 host-name kernel: [ 13.832618] intel8x0: measured clock 115021 rejected Feb 25 20:40:45 host-name kernel: [ 13.844642] enabling dynamically allocated vcaches Feb 25 20:40:45 host-name kernel: [ 13.844644] Starting AFS cache scan...Memory cache: Allocating 1562 dcache entries...found 0 non-empty cache files (0%). Feb 25 20:40:45 host-name kernel: [ 14.192757] intel8x0_measure_ac97_clock: measured 56043 usecs (7200 samples) Feb 25 20:40:45 host-name kernel: [ 14.192759] intel8x0: measured clock 128472 rejected Feb 25 20:40:45 host-name kernel: [ 14.554580] intel8x0_measure_ac97_clock: measured 57830 usecs (7680 samples) Feb 25 20:40:45 host-name kernel: [ 14.554590] intel8x0: measured clock 132803 rejected Feb 25 20:40:45 host-name kernel: [ 14.554591] intel8x0: clocking to 48000 Feb 25 20:40:55 host-name kernel: [ 24.244243] eth1: no IPv6 routers present Feb 25 20:42:37 host-name kernel: [ 126.817136] afs: Lost contact with file server 192.168.125.5 in cell company.com (all multi-homed ip addresses down for the server) Feb 25 20:42:37 host-name kernel: [ 126.817140] afs: Lost contact with file server 192.168.125.5 in cell company.com (all multi-homed ip addresses down for the server) Feb 25 20:42:37 host-name kernel: [ 126.817141] RXAFS_GetCapabilities failed with code -1 Feb 25 20:43:18 host-name kernel: [ 167.285849] afs: byte-range locks only enforced for processes on this machine (pid 7031 (trackerd), user 20014). Feb 25 20:43:59 host-name kernel: [ 208.946553] afs: byte-range locks only enforced for processes on this machine (pid 8223 (tracker-indexer), user 20014). Feb 25 20:44:01 host-name kernel: [ 210.537463] afs: byte-range locks only enforced for processes on this machine (pid 7031 (trackerd), user 20014). xxxxxxxxxxxxxxxxxxxx > > Do you know if the volume for the homedir of user B is on a different > fileserver than user A? You can check where they are with 'vos listvldb > <volume.name>'. If you don't happen to know the volume name, you can 'fs > lsmount /afs/cell/user/userA' (or whatever), or run 'fs lq /path/to/dir' > from a client that is able to access both directories. There's currently only one fileserver. fs lsmount gives mount points: %user.userA / %user.userB > > If they are on different fileservers, you may want to see if you can > access the userB fileserver at all. You can list other volumes that are > on that fileserver with 'vos listvldb -server serverB', and try to > access those. Or you can try a basic connectivity test (analagous to a > 'ping') to the fileserver by running 'rxdebug serverB -version' from the > client machine on the WAN. > > -- > Andrew Deason > [email protected] > vos listvldb listed 26 items, but skipped user.userB when run from WAN by userA! br, jukka > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info > _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
