Menu
▾
▴
unity-idm-discuss
|
From: Sander A. <sa....@fz...> - 2022-05-02 07:03:49
Attachments:
smime.p7s
|
Good Morning Krzysztof, we updated on Friday afternoon one of our unity instances to 3.9.0. Today we saw that the log exploded after the update within 7 hours unity wrote 25GB log file. We had parts running on trace level but had not that size before. The gzip-compressed log-files for the days before the update are 61MB. Because there is nothing about updating from 3.8 to 3.9 in the manual, do we need to change the log config? Of course there can be another reason for the log size and we are investigating the log at the moment. Best regards, Sander -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
|
From: Sander A. <sa....@fz...> - 2022-05-02 08:30:44
Attachments:
smime.p7s
|
Good morning again, we inspected a few things. 1. The unity.saml.requester.metadataSource .*.refreshInterval is ignored. Instead of updating the metadata every 12 hours it updated it every hour. 2. The output of metadata updated increases very much. Having the same log config unity 3.8.1 created in one hour ~150.000 lines, unity 3.9.0 created in the first hour after startup 145.000.000 lines. Mainly by updating the IdPs from Metadatasource Best regards, Sander On Mon, 2022-05-02 at 09:03 +0200, Sander Apweiler wrote: > Good Morning Krzysztof, > we updated on Friday afternoon one of our unity instances to 3.9.0. > Today we saw that the log exploded after the update within 7 hours > unity wrote 25GB log file. We had parts running on trace level but > had > not that size before. The gzip-compressed log-files for the days > before > the update are 61MB. Because there is nothing about updating from 3.8 > to 3.9 in the manual, do we need to change the log config? Of course > there can be another reason for the log size and we are investigating > the log at the moment. > > Best regards, > Sander -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
|
From: Roman K. <ro...@un...> - 2022-05-05 09:49:44
|
Hi Sander, Thanks for reaching out, indeed we are in the process of enhancing the saml metadata processing - which is not yet fully completed. Would it be possible to provide the anonymized sample of the log file with representative records that floods the file? Thank you, Roman pon., 2 maj 2022 o 10:30 Sander Apweiler <sa....@fz...> napisał(a): > Good morning again, > we inspected a few things. > > 1. The unity.saml.requester.metadataSource .*.refreshInterval is > ignored. Instead of updating the metadata every 12 hours it updated it > every hour. > > 2. The output of metadata updated increases very much. Having the same > log config unity 3.8.1 created in one hour ~150.000 lines, unity 3.9.0 > created in the first hour after startup 145.000.000 lines. Mainly by > updating the IdPs from Metadatasource > > Best regards, > Sander > > On Mon, 2022-05-02 at 09:03 +0200, Sander Apweiler wrote: > > Good Morning Krzysztof, > > we updated on Friday afternoon one of our unity instances to 3.9.0. > > Today we saw that the log exploded after the update within 7 hours > > unity wrote 25GB log file. We had parts running on trace level but > > had > > not that size before. The gzip-compressed log-files for the days > > before > > the update are 61MB. Because there is nothing about updating from 3.8 > > to 3.9 in the manual, do we need to change the log config? Of course > > there can be another reason for the log size and we are investigating > > the log at the moment. > > > > Best regards, > > Sander > > -- > Federated Systems and Data > Juelich Supercomputing Centre > > phone: +49 2461 61 8847 > fax: +49 2461 61 6656 > email: sa....@fz... > > ----------------------------------------------------------------------- > ----------------------------------------------------------------------- > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 > Vorsitzender des Aufsichtsrats: MinDir Volker Rieke > Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), > Karsten Beneke (stellv. Vorsitzender), Prof. Dr. Astrid Lambrecht, > Prof. Dr. Frauke Melchior > ----------------------------------------------------------------------- > ----------------------------------------------------------------------- > > > > > _______________________________________________ > Unity-idm-discuss mailing list > Uni...@li... > https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss > |
|
From: Sander A. <sa....@fz...> - 2022-05-05 09:53:17
Attachments:
smime.p7s
|
Hi Roman, we will check this and search for a solution, where we can store it. Cheers, Sander On Thu, 2022-05-05 at 11:49 +0200, Roman Krysiński wrote: > Hi Sander, > > Thanks for reaching out, indeed we are in the process of > enhancing the saml metadata processing - which is not yet fully > completed. > Would it be possible to provide the anonymized sample of the log file > with representative records that floods the file? > > Thank you, > Roman > > > pon., 2 maj 2022 o 10:30 Sander Apweiler <sa....@fz...> > napisał(a): > > Good morning again, > > we inspected a few things. > > > > 1. The unity.saml.requester.metadataSource .*.refreshInterval is > > ignored. Instead of updating the metadata every 12 hours it updated > > it > > every hour. > > > > 2. The output of metadata updated increases very much. Having the > > same > > log config unity 3.8.1 created in one hour ~150.000 lines, unity > > 3.9.0 > > created in the first hour after startup 145.000.000 lines. Mainly > > by > > updating the IdPs from Metadatasource > > > > Best regards, > > Sander > > > > On Mon, 2022-05-02 at 09:03 +0200, Sander Apweiler wrote: > > > Good Morning Krzysztof, > > > we updated on Friday afternoon one of our unity instances to > > > 3.9.0. > > > Today we saw that the log exploded after the update within 7 > > > hours > > > unity wrote 25GB log file. We had parts running on trace level > > > but > > > had > > > not that size before. The gzip-compressed log-files for the days > > > before > > > the update are 61MB. Because there is nothing about updating from > > > 3.8 > > > to 3.9 in the manual, do we need to change the log config? Of > > > course > > > there can be another reason for the log size and we are > > > investigating > > > the log at the moment. > > > > > > Best regards, > > > Sander > > -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X