I am also experiencing some strange behavior, but I am not really sure what the reason is, because there have been no significant changes in this part of the code since 3.2. I'll look into it once we are back from the current meeting.
Greetings, Sebastian 2014-10-13 11:48 GMT+02:00 Fabian Cretton <[email protected]>: > Hi, > > Since an update of my Marmotta 3.3.0 fork a few weeks ago, the logging > functionality behaves strangely. > I was thinking having configuration problems, but after some trials this > morning I can't find the reason. > > In my 'log' folder, since that update, only "marmotta-security.log" is > daily updated and seems to contain the valid log. > But the other files "marmotta-debug.log" and "marmotta-main.log" didn't > change since 22.09.2014. > The information displayed in the console also seems corrupted. > On the "admin/logging.html" page, if I set Console to "DEBUG", those debug > information are not displayed. > > Before that code update a few weeks ago, logs were working as expected. > > Willing to investigate the problem, this morning I did add some > "System.out.println()" informations in the > org.apache.marmotta.platform.core.services.logging.LoggingServiceImpl > But everything seems fine: the referenced log files are correct, the paths > are correct, the modules configuration debut levels are correct... > > Any pointer would be appreciated. > Thanks > Fabian >
