Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

PRB: Firewall syslog service is showing 100% CPU utilization.

Expand / Collapse


This article applies to:

  • Firewall Suite

Symptoms:

  • Firewall syslog service is showing 100% CPU utilization.

Causes:

When using the syslog service to retrieve firewall log files the CPU utilization may increase to 100% every time the syslog service is accessed.

Most often this is caused by one of the two scenarios listed below.

If multiple profiles are using the syslog service to retrieve the same log file(s), this can cause issues with the syslog service. Only one profile should be specified to use the syslog service. The other profiles should be using the log files generated by the syslog. The log files, by default, are stored in the following directory, which is specified within the profile that is retrieving the syslog:

    \WebTrends Firewall Suite\SyslogLogs

The Network Interface Card (NIC) driver may not be the correct driver to use the syslog. Experience has shown that some network card drivers have issues using the syslog service.

  • Specifically the Compaq NETFLEX 3 10/100 TX UTP, using driver NETFLX3.SYS V 4.22 causes such an issue. If the driver is switched to NETFLX3.SYS V4.36 the issue should be corrected.

This article was previously published as:
NETIQKB1639

To contact LevelBlue about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.