Project

General

Profile

Bug #9415

Firewall log is empty in the GUI

Added by Jim Pingle 7 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Logging
Target version:
2.5.0
Start date:
03/20/2019
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.5.0
Affected Architecture:
All

Description

On SG-3100 (and likely others), the GUI firewall log is empty. The contents of /var/log/filter.log appear correct, but no entries are parsed and shown in the GUI. Additionally, filterparser.php produces no output. Thus it's likely a problem parsing the log and not a problem with the GUI page.

Might have some relation to #9411, but still happens on systems that appear to have valid/properly formatted log files.

Associated revisions

Revision af85efec (diff)
Added by Jim Pingle 7 months ago

Fix empty log files in the GUI. Fixes #9415

Two ways they were empty that I found:
  • filterlog log entries now have a pid after the process
  • CARP/VRRP entries did not set a source and so were not logged

While here, add CARP details to proto field of GUI log view.

History

#1 Updated by Jim Pingle 7 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#2 Updated by Jim Pingle 7 months ago

  • Status changed from Feedback to Resolved

Tested firewall logs on a variety of platforms, works everywhere now.

Also available in: Atom PDF