After Rebooting AEM publisher all custom logs diverted to stdout.log | Community
Skip to main content
A
at_mahajan23
Level 2
April 12, 2022
Solved

After Rebooting AEM publisher all custom logs diverted to stdout.log

  • April 12, 2022
  • 1 reply
  • 768 views

Hi Team ,

I have rebooted AEM publisher server and it is observed that all custom logs configuration are not picked by publisher process. All logs are diverted to stdout.log with INFO level and below logger configuration is added automatically with additivity to True.

org.apache.sling.commons.log.CONSOLE (ch.qos.logback.core.ConsoleAppender)

This causing Disk space full since all INFO level logs are generated.

Following steps are followed to reboot AEM publisher.

 

1. Stop  publisher process

2. Reboot Server

3. Start publisher process.

 

Please let me know , how can   AEM publisher force to pickup custom log configurations from logger.

Thanks

 

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

Hi Mahajan,

 

There's nothing wrong with CONSOLE appender it's OOTB appender, when it gets triggered it means other configs for logs got messed up.

 

Take backup of your instance,

Open system console on slinglog page and compare your misconfigured log state with the OOTB instance config.

Once you identify differences configure both same way.

 

In case of issue restore from backup.

 

Regards.

Peter

1 reply

Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity AdvisorAccepted solution
Community Advisor
April 13, 2022

Hi Mahajan,

 

There's nothing wrong with CONSOLE appender it's OOTB appender, when it gets triggered it means other configs for logs got messed up.

 

Take backup of your instance,

Open system console on slinglog page and compare your misconfigured log state with the OOTB instance config.

Once you identify differences configure both same way.

 

In case of issue restore from backup.

 

Regards.

Peter

    Terms & ConditionsAccessibility statement

    Loading footer...