<html><body><div style="font-family: courier new,courier,monaco,monospace,sans-serif; font-size: 10pt; color: #000000"><div>I forgot to mention that if I restart tomcat, it will stop writing in the tmp files.<br></div><div>Could it be a bug in log4j ?<br data-mce-bogus="1"></div><div><br></div><div data-marker="__SIG_PRE__">Vincent Delhommeau <br>Administrateur Systèmes & Réseaux <br>EHESS - DSI/SERI <br>01 49 54 84 46 <br></div><br><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>De: </b>"Delhommeau Vincent" <vincent.delhommeau@ehess.fr><br><b>À: </b>users@shibboleth.net<br><b>Envoyé: </b>Lundi 20 Avril 2020 17:34:59<br><b>Objet: </b>problem with IdP log files<br></div><br><div data-marker="__QUOTED_TEXT__"><div style="font-family: courier new,courier,monaco,monospace,sans-serif; font-size: 10pt; color: #000000"><div>Hi,<br></div><br><div>I'm finishing the setup of a shibboleth v 3.4.4 IdP.<br></div><div>I have found strange files in the logs folder.<br></div><div>Here is a partial litsting of /opt/shibboleth-idp/logs :<br></div><br><div>-rw-r--r-- 1 tomcat tomcat 21583 Apr 18 00:00 idp-process-2020-04-17.log.gz<br>-rw-r--r-- 1 tomcat tomcat 4770 Apr 18 00:03 idp-process-2020-04-17.log713182882606029.tmp<br>-rw-r--r-- 1 tomcat tomcat 2862 Apr 18 00:00 idp-process-2020-04-17.log713194143509376.tmp<br>-rw-r--r-- 1 tomcat tomcat 11957 Apr 19 00:00 idp-process-2020-04-18.log.gz<br>-rw-r--r-- 1 tomcat tomcat 954 Apr 19 00:00 idp-process-2020-04-18.log799578327391671.tmp<br>-rw-r--r-- 1 tomcat tomcat 954 Apr 19 00:00 idp-process-2020-04-18.log799588595404227.tmp<br>-rw-r--r-- 1 tomcat tomcat 11916 Apr 20 00:00 idp-process-2020-04-19.log.gz<br>-rw-r--r-- 1 tomcat tomcat 954 Apr 20 00:00 idp-process-2020-04-19.log885979225206155.tmp<br>-rw-r--r-- 1 tomcat tomcat 954 Apr 20 00:00 idp-process-2020-04-19.log885988711505334.tmp<br>-rw-r--r-- 1 tomcat tomcat 165221 Apr 20 16:40 idp-process.log<br>-rw-r--r-- 1 tomcat tomcat 2122 Apr 18 00:00 idp-warn-2020-04-17.log.gz<br>-rw-r--r-- 1 tomcat tomcat 4770 Apr 18 00:03 idp-warn-2020-04-17.log713182892530877.tmp<br>-rw-r--r-- 1 tomcat tomcat 2862 Apr 18 00:00 idp-warn-2020-04-17.log713194148379693.tmp<br>-rw-r--r-- 1 tomcat tomcat 861 Apr 19 00:00 idp-warn-2020-04-18.log.gz<br>-rw-r--r-- 1 tomcat tomcat 954 Apr 19 00:00 idp-warn-2020-04-18.log799578331483925.tmp<br>-rw-r--r-- 1 tomcat tomcat 954 Apr 19 00:00 idp-warn-2020-04-18.log799588599983199.tmp<br>-rw-r--r-- 1 tomcat tomcat 820 Apr 20 00:00 idp-warn-2020-04-19.log.gz<br>-rw-r--r-- 1 tomcat tomcat 954 Apr 20 00:00 idp-warn-2020-04-19.log885979229538330.tmp<br>-rw-r--r-- 1 tomcat tomcat 954 Apr 20 00:00 idp-warn-2020-04-19.log885988715547676.tmp<br>-rw-r--r-- 1 tomcat tomcat 5972 Apr 20 09:10 idp-warn.log</div><br><div>After log rotation shibboleth writes in temporary files along with the regular log files.<br></div><div>The problem only concerns idp-process.log and idp-warn.log, the other log files are "normal".<br></div><div>I didnt change the logging settings.<br></div><br><div>Two monthes ago I tried to install v 3.4.6 IdP. I dropped it because I could not make the shibcas plugin work, but kept the installation folder.<br></div><div>I can see the same behaviour with log files.<br></div><br><div>Has someone already met this situation ?<br></div><br><div>My configuration : opensuse leap 15.1, apache 2.4.33, tomcat 9.0.31, java 1.8.0.242 openjdk<br></div><br><div>Regards,<br></div><br><div>Vincent Delhommeau <br>Administrateur Systèmes & Réseaux <br>EHESS - DSI/SERI <br>01 49 54 84 46 <br></div></div><br>-- <br>For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg<br>To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br></div></div></body></html>