Preview Tool

Cisco Bug: CSCvh81142 - Snort Core Generated while running 6.2.3

Last Modified

Aug 31, 2019

Products (32)

  • Cisco Firepower Management Center
  • Cisco Firepower Management Center 2500
  • Cisco FirePOWER Appliance 8260
  • Cisco FirePOWER Appliance 7050
  • Cisco FirePOWER Appliance 8120
  • Cisco FirePOWER Appliance 8360
  • Cisco AMP 7150
  • Cisco FirePOWER Appliance 8130
  • Cisco FirePOWER Appliance 8140
  • Cisco FirePOWER Appliance 8350
View all products in Bug Search Tool Login Required

Known Affected Releases

6.2.2 6.2.3 6.3.0

Description (partial)

This is the sequence of events that is happening when this bug occurs:
1. First snort instance produces the error: "FATAL ERROR: Duplicate preprocessor keyword: ssl." and proceeds to shut down.
2. Second snort instance receives a SIGTERM: "*** Caught Term-Signal"
3. Second snort instance then produces the same error as the first instance: "FATAL ERROR: Duplicate preprocessor keyword: ssl." after receiving the term-signal.
4. At this point, a race condition is hit: as can be observed in the stack trace, snort goes into the cleanup phase, and tells all the control socket threads to stop processing, and then waits on them to terminate. However, one of the control socket threads does not get cleaned up. You can see this in the stack trace in frame 2, sfcontrol.c:792, the thread list has one element in it still. So it is just waiting forever for that thread to finish.
5. After 30 seconds of waiting, CM sees that the process it not dead yet, so it sends a SIGABRT. This is what causes the core.

It seems like this is just a case where things happen in the wrong order and it causes a race condition. It happens very occasionally during the snort reload process. I think if there is a way to repro the duplicate preprocessor, then we will likely be able to repro the bug.

Fatal Error occurred due to mismatch in config and reload happened causing this issue
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.