EasyApache4 using wrong log file?

PabloC

• December 01, 2017 21:33

Hi checking my lfd.log, I have found this. Could anyone tell me, if they are wrong, how to make it right? Nov 27 00:00:02 server4 lfd[26676]: EasyApache4, using /etc/apache2/logs/error_log instead of /usr/local/apache/logs/error_log (Web Server) Nov 27 00:00:02 server4 lfd[26676]: EasyApache4, using /etc/apache2/logs/error_log instead of /usr/local/apache/logs/error_log {ModSecurity} Thanks!

• 

  dalem

  • December 03, 2017 15:44

  Those log file locations are correct /usr/local/apache/ is the old location for EA3 there is symbolic links there so you can view them

  0
• 

  PabloC

  • December 03, 2017 21:08

  thanks!

  0
• 

  cPanelMichael

  • December 04, 2017 18:14

  Hello, I'm happy to see the question was answered. I'm marking this thread as solved. Thank you.

  0
• 

  Marius

  • January 28, 2018 06:51

  In the last 2 days I have the same problem. In CSF -> /var/log/lfd.log:
  Jan 28 08:53:12 server lfd[958]: EasyApache4, using /etc/apache2/logs/error_log instead of /usr/local/apache/logs/error_log (Web Server) Jan 28 08:53:12 server lfd[958]: EasyApache4, using /etc/apache2/logs/error_log instead of /usr/local/apache/logs/error_log {ModSecurity}
  Since this error CSF stop to analyse & ban from Modsecurity logs. My server: Easy Apache 4 (Apache 2.4, PHP 7.0, mpm_prefork) Cloudlinux CageFS Kernelcare CSF v11.05 OWASP ModSecurity Core Rule Set V3.0 Its an Easyapache 4 BUG?

  0
• 

  cPanelMichael

  • January 30, 2018 16:24

  Hello, That's not a bug, as it's correctly noting the changed path with EasyApache 4. As far as CSF functionality not working as expected, I suggest reporting the issue to the CSF support team so they can take a closer look. Thank you.

  0

Please sign in to leave a comment.