Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Log & Event Manager (LEM) > Barracuda Web Filter Syslog Events Not Appearing in Console

Barracuda Web Filter Syslog Events Not Appearing in Console

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,192 Votes: 0 Revisions: 10


None of the syslog events from your Barracuda Web Filter are appearing in LEM.


  • All Barracuda Web Filters
  • All LEM versions


Barracuda Web Filter will send its syslog data to local4.log. It can't be configured to send data to a different facility. The presence of another device pointing to the same logging facility as the Barracuda triggers this issue. 

The Barracuda device and Cisco ASA device connector are set to receive and send data to local4.log by default. Since the Barracuda can't be adjusted, the other device(s) must be configured to send their syslog data to a different facility.


  1. Configure the Barracuda Web Filter to send its syslog data to the LEM appliance.
  2. Verify that the Barracuda Web Filter connector is enabled under Manage > Appliances.
  3. Reconfigure any other device sending its syslog data to local4.log (such as Cisco ASA devices) and their connectors in the LEM appliance so they point to an empty logging facility. This frees up local4.log for the Barracuda Web Filter.


Last modified