[OpenAFS] What changed after 1.4.1?

[Lars Richter]

Tomorrow I will test the other versions in the office and try to locate  
the version, where the problem occurs.

Lars

Jeffrey Altman wrote:
> All beta and release candidate installers are available from
>
>   /afs/grand.central.org/software/openafs/candidate/
>
> Jeffrey Altman
>
>
> Lars Richter wrote:
>   
>> Hi,
>>
>> this was the last version I used for tests because of problems with
>> delayed write operations. I decided to wait for further tests, until
>> 1.4.2 was released. I don't have the other beta releases. If I could get
>> them, I can test it tomorrow, where the problem occurs.
>>
>> Is it possible to download the other beta releases?
>>
>> Lars
>>
>>
>> Jeffrey Altman wrote:
>>     
>>> Lars:
>>>
>>> Are you saying that the breakage occurred in 1.4.2-beta2 ?
>>>
>>> Jeffrey Altman
>>>
>>> Lars Richter wrote:
>>>  
>>>       
>>>> Hi,
>>>>
>>>> I have the same problem after update from version 1.4.1 to 1.4.2.
>>>>
>>>> Version 1.4.1:
>>>> Packets were send through the network to check the connectivity to
>>>> kasserver. Integrated login works!
>>>>
>>>> Version 1.4.2:
>>>> There are not any network packets send to check the connectivity to
>>>> kasserver. Integrated login fails!
>>>>
>>>> Last version I used with success: 1.4.2beta1
>>>>
>>>> Regards,
>>>> Lars
>>>>
>>>> Jeffrey Altman wrote:
>>>>    
>>>>         
>>>>> The behavior is that of a lack of network connectivity.
>>>>> I don't know what the cause of the problem is but I am
>>>>> attempting to help you narrow it down.   Is there traffic
>>>>> being exchanged with the kaserver?
>>>>>
>>>>> If so, are there responses being sent back?
>>>>>
>>>>> If there is no traffic being sent, then the question becomes
>>>>> why not?
>>>>>
>>>>>
>>>>> Andrew Radamis wrote:
>>>>>  
>>>>>      
>>>>>           
>>>>>> But it works with out issue with 1.4.1, with no other changes to the
>>>>>> system. I tried 1.4.2 and had the same issue. As soon as I downgrade
>>>>>> back to 1.4.1 it works again. I can login to the machine as soon as
>>>>>> the login box appears. System authentication is on an NT domain, using
>>>>>> Samba. The  Samba PDC and BDC are also the AFS servers, so I don't
>>>>>> think
>>>>>> it's a network conductivity issue.
>>>>>>
>>>>>> Andrew
>>>>>> On 12/13/06, *Jeffrey Altman* <jaltman@secure-endpoints.com
>>>>>> <mailto:jaltman@secure-endpoints.com>> wrote:
>>>>>>
>>>>>>     You privately sent the event log entries.
>>>>>>     I see nothing in there that is wrong.
>>>>>>     Although I must wonder whether or not the machine
>>>>>>     actually has network access at the time it is
>>>>>>     failing.
>>>>>>
>>>>>>     The error indicates that none of the KdC addresses
>>>>>>     that are being contacted are responding.  You might
>>>>>>     want to monitor traffic with a tcpdump on the server
>>>>>>     to see whether in fact you are getting traffic to
>>>>>>     the kaservers that you are expecting to see.
>>>>>>
>>>>>>     Jeffrey Altman
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>>>>>             
>>>> _______________________________________________
>>>> OpenAFS-info mailing list
>>>> OpenAFS-info@openafs.org
>>>> https://lists.openafs.org/mailman/listinfo/openafs-info
>>>>     
>>>>         
>> _______________________________________________
>> OpenAFS-info mailing list
>> OpenAFS-info@openafs.org
>> https://lists.openafs.org/mailman/listinfo/openafs-info
>>