Expand my Community achievements bar.

Elevate your expertise and be recognized as a true influencer! Nominations for the exclusive Adobe Community Advisor program 2023 are now OPEN.
SOLVED

Aem dispatcher.log size surges suddenly

Avatar

Level 1

Hi, 

 

Our systems dispatcher.log file size surges suddenly. Even after nullifying the file, it increases upto 500mb/min. This file eats all the disk space in the dispatcher server. 

Can anyone advice how to resolve this issue. 

 

Thanks in advance. 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @karthikfordreal 

 

You should check for few things on why the logs are filling at this rate:

  1. Check if the log level for dispatcher logs is ERROR, not DEBUG or TRACE. TRace can produce  a lot of lines of log for a single request. Log level can be changed from httpd.conf or apache2.conf file by changing dispatcher global configuration 
    <fModule disp_apache2.c>
    DispatcherConfig conf/dispatcher.any
    DispatcherLog logs/dispatcher.log 
    DispatcherLogLevel 0 DispatcherNoServerHeader 0
    DispatcherDeclineRoot 0 DispatcherUseProcessedURL 0 DispatcherPassError 0 DispatcherKeepAliveTimeout 60 </IfModule>
    Make sure DispatcherLogLevel is 0 or ERROR
  2. Try to analyse what type of requests are filling up the logs whether there are logs of flushing/invalidation of content request or page request etc. Then try to work on that part, you might new an extra pair of dispatcher/publisher if single publisher is serving a lot more than its capacity.

Hope it helps!

Thanks!

Nupur

0 Replies

Avatar

Correct answer by
Community Advisor

Hi @karthikfordreal 

 

You should check for few things on why the logs are filling at this rate:

  1. Check if the log level for dispatcher logs is ERROR, not DEBUG or TRACE. TRace can produce  a lot of lines of log for a single request. Log level can be changed from httpd.conf or apache2.conf file by changing dispatcher global configuration 
    <fModule disp_apache2.c>
    DispatcherConfig conf/dispatcher.any
    DispatcherLog logs/dispatcher.log 
    DispatcherLogLevel 0 DispatcherNoServerHeader 0
    DispatcherDeclineRoot 0 DispatcherUseProcessedURL 0 DispatcherPassError 0 DispatcherKeepAliveTimeout 60 </IfModule>
    Make sure DispatcherLogLevel is 0 or ERROR
  2. Try to analyse what type of requests are filling up the logs whether there are logs of flushing/invalidation of content request or page request etc. Then try to work on that part, you might new an extra pair of dispatcher/publisher if single publisher is serving a lot more than its capacity.

Hope it helps!

Thanks!

Nupur

Avatar

Employee Advisor

 As Nupur mentioned, first check what kind of calls are being logged and the log level set for those requests in the conf file.