> could this have to do with some kind of bug in timestamps
> at GMT: Thursday, January 14, 2021 8:25:36 AM
> the Unix hex timestamp was 6000
Interesting. Setting date to "14 JAN 2021 08:21:36” seems to solve the
problem on my test cell.
On Jan 14, 2021, at 10:32 AM, Andreas Weiss
Dear all,
could this have to do with some kind of bug in timestamps
at GMT: Thursday, January 14, 2021 8:25:36 AM
the Unix hex timestamp was 6000
maybe just a wild-goose chase
clients with openafs 1.8.6 are problematic, 1.6 seems to be fine.
best
andi
On 1/14/21 2:27 PM, Florian
On 14/01/2021 14:12, Heinz-Ado Arnolds wrote:
Dear colleagues,
thanks for your notes!
We have the same problem with 1.8.6 clients since this morning and are
working hard to find the problem. Our complete cell is not able to work
any more. Any help would be greatly appreciated.
Another "me
Dear all,
same problem here. Our complete cell does not work any more. Any ideas?
Best,
Florian
--
Dr. Florian Möller
Universität Würzburg
Institut für Mathematik
Emil-Fischer-Straße 30
97074 Würzburg, Germany
Tel. +49 931 3185596
Am 14.01.21 um 14:02 schrieb Neil Brown:
Sorry, struggling
Dear colleagues,
thanks for your notes!
We have the same problem with 1.8.6 clients since this morning and are working
hard to find the problem. Our complete cell is not able to work any more. Any
help would be greatly appreciated.
Cheers,
Ado
--
Sorry, struggling with a connection today, but yes. Our site was working
fine up until about 8:30am GMT this morning, and then we started having
similar issues. We've been thinking it was a local configuration change,
though we hadn't made any AFS changes, only an openssl update.
But yes,
