ERROR log: Log level changes not getting reflected | Community
Skip to main content
A
a_mn1
September 18, 2017

ERROR log: Log level changes not getting reflected

  • September 18, 2017
  • 4 replies
  • 12238 views

Hello All, I am trying to change the log level of error log through system/console. However this changes are not getting reflected in the logs. What could be the reason for this.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    4 replies

    VeenaVikraman
    Community Advisor
    VeenaVikramanCommunity Advisor
    Community Advisor
    September 18, 2017

    What specific logs are you trying to capture ? Debug or info ?

    A
    a_mn1Author
    September 19, 2017

    I am trying to switch to Debug and Trace.

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    September 18, 2017

    What are you trying to achieve? Which loglevel? And what have you tried and was not working?

    Jörg

    A
    a_mn1Author
    September 19, 2017

    Hello Jorg,

    I am trying to debug an issue . I wanted to enable Debug/Trace in my logs. Whenever i try to change the log levels in my local /dev servers from configMgr, it reflects immediately. But not sure what could be the reason that the same is not happening in my Production env. I am able to change the log level from configMgr, but after saving, it again go back to Info mode.

    Thanks,

    Anand

    Jörg Hoh

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    September 21, 2017

    Hello Jörg,

    I am facing problem there only. Whenever I edit the logger configuration from this console, the changes are not getting reflected. Sorry if I confused you.

    Regards,

    Anand


    Configuration created through the OSGI webconsole should go int /apps/system/config, so can you please check there? Also check the error.log if something is written at the time you try to create that logging configuration.

    Jörg

    Sh1ju
    Sh1ju
    September 18, 2017

    Restart AEM and then check

    A
    a_mn1Author
    September 19, 2017

    I want to know what is causing this issue. This is happening in my Production env.

    edubey
    edubey
    September 20, 2017

    Hi,

    IIRC, I have seen this once in AEM 6.3 in a production environment. I think for some reason (probably bug) duplicate configs get created.

    When you change the log level, you will be seeing config Id in log files. You may not find the config in Felix console.

    However, there wasn't any straight solution from Adobe support team.

    Can you please verify the Felix console's configuration and check the if there are any duplicate category created for these configurations? if so, delete them.

    As you mentioned, that you are still seeing duplicate configurations of

    • Apache Sling Job Queue Configuration
    • Apache Sling Login Admin Whitelist Configuration Fragment

    I would suggest you delete them and then restart the instance.

    Thanks

      Terms & ConditionsAccessibility statement

      Loading footer...