Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

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

Avatar

Level 2

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

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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

View solution in original post

0 Replies

Avatar

Correct answer by
Community Advisor

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