Hello Jason,

there is definitely no firewall rule that would block any UDP
packets between the fileserver and the AFS-Client.
And as you see in the output, the host does reply to
whoareyou() packets ... just sometimes it doesn't which
is very painful.
We did some investigation in the network but tracked the
problem down to the AFS-client itself. Maybe there is a
lock, a semaphore or something else that must be crossed
before the client sends out the answer to whoareyou().
At least this is my suspicion ...

With kind regards,

Carsten Jacobi (*120-4468)
Firmware Development in Böblingen

IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294


                                                                           
             Jason Edgecombe                                               
             <[EMAIL PROTECTED]                                             
             eek.com>                                                   To 
                                       Carsten Jacobi/Germany/[EMAIL PROTECTED] 
   
             08-03-01 00:07                                             cc 
                                       openafs-info@openafs.org            
                                                                   Subject 
                                       Re: [OpenAFS] openafs client on     
                                       Linux-s390x sometimes not replying  
                                       to whoareyou() calls                
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Carsten Jacobi wrote:
> Hello,
>
> starting from last month we have been facing "Lost contact with
fileserver"
> [...]
> 10:30:00.945453 IP fs13.xxx.xx.xx.xx.afs3-fileserver >
> mclinx.xxx.xx.xx.xx.afs3-callback:  rx data cb call whoareyou (32)
> 10:30:00.945499 IP mclinx.xxx.xx.xx.xx.afs3-callback >
> fs13.xxx.xx.xx.xx.afs3-fileserver:  rx data cb reply whoareyou (460)
                                                       ^^^^^^^^^^^^^^^
> 10:30:08.941373 IP fs20.xxx.xx.xx.xx.afs3-fileserver >
> mclinx.xxx.xx.xx.xx.afs3-callback:  rx data cb call whoareyou (32)
> 10:30:08.941455 IP mclinx.xxx.xx.xx.xx.afs3-callback >
> fs20.xxx.xx.xx.xx.afs3-fileserver:  rx data cb reply whoareyou (460)
                                                       ^^^^^^^^^^^^^^^
> [...]
> are reported "back up" again.
>
> My question is: What can block an AFS-Client from answering
> whoareyou() for several minutes? Are there any limits or restrictions
> that can lead an AFS client to a situation where it is internally
blocked?
> Are there parameters one can adjust for tuning in order to avoid this
> situation?
> We have had those "Lost contact" time slots once every two days
> lately and they are painful for users who are logged on our system
> during that time. I would be happy to get rid of them somehow ...
>

This may be a silly question, but are there any firewalls or NAT running
on the fileserver, client, or in between?

If the firewall blocks the who are you message, then that would explain
why there is no reply.

Sincerely,
Jason
:��T���&j)b�   b�өzpJ)ߢ�^��좸!��l��b��(���~�+����Y���b�ا~�����~ȧ~

Reply via email to