From: Laura H. <l....@fz...> - 2023-07-26 11:18:01
|
Hi Krzysztof, we wanted to recreate the error, but it seems to be working now. The application error does not appear anymore. Best regards, Laura Am 26.07.23 um 13:15 schrieb Krzysztof Benedyczak: > Hi Sander, > > Are there any updates on the below topic? > > We have some nice performance improvements prepared, that should help > with your perf-problems, but I'd prefer > to release them only after investigating this issue, which sounds > critical. > > Best, > Krzysztof > > W dniu 19.06.2023 o 11:46, Sander Apweiler pisze: >> Dear Roman, >> not yet since we are quite busy with preparing a summerschool. Maybe >> later next week. >> >> Best regards, >> Sander >> >> On Mon, 2023-06-19 at 11:40 +0200, Roman Krysiński wrote: >>> Dear Sander, >>> >>> Are there any news with regards to additional information? >>> >>> Thank you, >>> Roman >>> >>> >>> pon., 12 cze 2023 o 10:35 Sander Apweiler <sa....@fz...> >>> napisał(a): >>>> Dear Krzysztof, >>>> we will bring the information as soon as possible. >>>> >>>> Best regards, >>>> Sander >>>> >>>> On Thu, 2023-06-08 at 10:16 +0200, Krzysztof Benedyczak wrote: >>>>> Dear Laura, Sander, >>>>> >>>>> W dniu 6.06.2023 o 13:19, Laura Hofer pisze: >>>>>> Dear Krzysztof, Dear Roman, >>>>>> >>>>>> we were just about to install unity 3.13.0 and then start >>>>>> testing. >>>>>> To >>>>>> do this, we first switched from unity 3.11.2 to unity 3.12.0, >>>>>> then >>>>>> to >>>>>> 3.13.0. After that, we received an application error message >>>>>> when >>>>>> logging in (see attached screenshot). Unfortunately we could >>>>>> not >>>>>> find >>>>>> any error message in the stack trace, so we switched back to >>>>>> 3.12.0. >>>>>> There we got the same error message at login, but then we could >>>>>> also >>>>>> find an error message in the stack trace. This is also attached >>>>>> as >>>>>> a >>>>>> txt file. >>>>> So we have found the problem in 3.12 causing your error. We can >>>>> fix >>>>> it, >>>>> no problem, however I don't think it makes a lot of sense: it is >>>>> a >>>>> minor >>>>> bug, which will only occur on a database which was run on 3.13, >>>>> and >>>>> then >>>>> used in 3.12. This problem on 3.12 is also for sure 100% not >>>>> related >>>>> to >>>>> the (serious) sign-in problem you observed on 3.13. >>>>> >>>>> That said, to investigate the real issue we need to get back to >>>>> 3.13, >>>>> and diagnose the problem in there. In case of error like in your >>>>> screenshot, you should rather get a stacktrace or at least ERROR >>>>> message >>>>> in log. It is possible we have some omission in logging, but >>>>> unlikely. >>>>> >>>>> Can you please first enable debug logging, then repeat your >>>>> failing >>>>> sign-in on 3.13 and inspect log files one more time (or share it >>>>> with >>>>> us)? We need to find some clues on what is failing. Without >>>>> access to >>>>> your database it will be the only way forward. >>>>> >>>>> Best, >>>>> Krzysztof >>>>> >>>>> > -- Juelich Supercomputing Centre Institute for Advanced Simulation Forschungszentrum Juelich GmbH 52425 Juelich, Germany E-Mail: l....@fz... Phone: +49 2461 61-6576 Fax: +49 2461 61-6656 ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |