BugZero | F5 BugID 590735 - syslog-ng error message in log

F5 - Defect ID: 590735

syslog-ng error message in log

F5 - Defect ID: 590735

syslog-ng error message in log

Last updated on July 18th, 2026

BugZero Risk Score
6.9 Medium

Overall: 6.9

Severity: 7.3

Community: 4.2

Lifecycle: 8.7

What is the BugZero Risk Score?

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Bug Details

Priority: 3-Major
Status: Resolved
Impact Category: TMOS

Description

Symptoms

Very rarely syslog-ng generates error in the log after update. The error message has this signature: info kernel: syslog-ng[3056]: segfault at 0 ip 0000000008055971 sp 00000000ffa55090 error 4 in syslog-ng[8048000+66000]

Impact

If syslog-ng is running, this error can be ignored. If it is not running, you can start it by running the following command: tmsh restart sys service syslog-ng

Conditions

Full condition is still unknown. It was seen on first time boot.

Workaround

Nothing needs to be done.

Fix Information

None

Change history

Links

Original Vendor Announcement

Relevant Products

Click on a version to see all relevant bugs

Affected versions:12.1.0, 12.1.0 hf1, 12.1.0 hf2, 12.1.1, 12.1.1 hf1, 12.1.1 hf2, 12.1.2, 12.1.2 hf1, 12.1.2 hf2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 hf1, 13.0.0 hf2, 13.0.0 hf3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: No known fixed versions

Top F5 Defects

9.6Defect ID: 546260
TMM can crash if using the v6rd profile
9.6Defect ID: 934133
Unable to Create/delete ltm virtual server via CLI transaction when destination is not specified on the ltm virtual object
9.6Defect ID: 1154417
Profile based attack is not mitigated at hardware on L2 wire setup
9.6Defect ID: 913713
Rebooting a blade causes MCPd to core as it rejoins the cluster
9.6Defect ID: 2141125
Multicast traffic is dropped with incorrect VLAN tagging

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Ready to prevent the next vendor outage?

Get a demo

F5 - Defect ID: 590735

syslog-ng error message in log

F5 - Defect ID: 590735

syslog-ng error message in log

Last updated on July 18th, 2026

BugZero Risk Score6.9 Medium

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Links

Top F5 Defects

Ready to prevent the next vendor outage?

F5 - Defect ID: 590735

syslog-ng error message in log

F5 - Defect ID: 590735

syslog-ng error message in log

Last updated on July 18th, 2026

BugZero Risk Score6.9 Medium

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Links

Top F5 Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
6.9 Medium

BugZero Risk Score
6.9 Medium