Domlogs Processing Buffer Location

Bob1965

• August 30, 2018 09:45

Hi, I have an issue on a VPS that I would like to resolve for a very low traffic website. When tailing a low traffic website in SSH, the domlog does not update in real time, it waits until 17 files are accessed then it processes it. I guess this would be called a buffer and I would like to know where this setting is so I can lower it. Here is the VPS version info: /etc/redhat-release:CentOS Linux release 7.5.1804 (Core) /usr/local/cpanel/version:11.74.0.6 /var/cpanel/envtype:kvm CPANEL=release Thanks for the information in advance. Regards, Bob

• 

  cPanelLauren

  • August 31, 2018 15:51

  Hi @Bob1965 Can you tell me where you're tailing them from? The domlogs at /etc/apache2/logs/domlogs/domain.tld
  should be updating in real time.

  0
• 

  Bob1965

  • August 31, 2018 16:04

  Hello Lauren, tail -f /usr/local/apache/domlogs/website.com I have checked every website on the server and it only updates when 17 files have been accessed. If no one visits the website for even 3 days, I do not see any updates to the file. But if I pull up a file I can see it in the apache status in WHM. If I pull up 17 different files or even refresh 17 times, the tail will all of a sudden post all 17 at once. So there must be some buffer configuration somewhere. lso to be noted, I have Piped Log Configuration enabled. Maybe I should disable this? Regards, Bob

  0
• 

  cPanelLauren

  • August 31, 2018 16:35

  Hi @Bob1965 I believe piped logging will do something like this though it's not exactly 17 files as the settings. Information on this can be found here:

  0
• 

  Bob1965

  • August 31, 2018 17:09

  turning off the piped logging worked :)

  0
• 

  cPanelLauren

  • August 31, 2018 17:15

  Hi @Bob1965 I am glad to see that resolved the issue. Just keep in mind that piped logging does have some resource benefits and if you start seeing higher usage than normal attributed to Apache the disabling of piped logging is most likely the cause. You would most likely only notice this if you had a moderately busy server. Thanks!

  0

Please sign in to leave a comment.