Skip to content
This repository has been archived by the owner on Apr 16, 2021. It is now read-only.

Starting Suricata results in "Illegal instruction" #26

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 8 comments
Closed

Starting Suricata results in "Illegal instruction" #26

GoogleCodeExporter opened this issue Mar 24, 2015 · 8 comments
Labels
auto-migrated Priority-Critical Type-Defect

Comments

@GoogleCodeExporter
Copy link 

Suricata was tested and working properly.  Perhaps libraries changed and so now 
Suricata results in "Illegal instruction".  Re-compiling suricata allows it to 
start successfully.

Original issue reported on code.google.com by doug.bu...@gmail.com on 1 Nov 2010 at 5:13
@GoogleCodeExporter
Copy link
Author

Original comment by doug.bu...@gmail.com on 1 Nov 2010 at 7:51

  • Added labels: Priority-Critical
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author 

Perhaps this is machine-specific.  I have one machine that works and one that 
doesn't (same ISO).  Still troubleshooting.

Original comment by doug.bu...@gmail.com on 1 Nov 2010 at 8:49

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Installed all updates and recompiled Suricata.  Resulting binary was identical 
to the original binary.  Still troubleshooting.

Original comment by doug.bu...@gmail.com on 5 Nov 2010 at 10:59

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Upgrading to Suricata 1.1beta1.  Hoping this will help.

Original comment by doug.bu...@gmail.com on 27 Dec 2010 at 2:29

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by doug.bu...@gmail.com on 30 Dec 2010 at 7:19

  • Changed state: Started
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

http://securityonion.blogspot.com/2011/01/security-onion-20110101.html

Original comment by doug.bu...@gmail.com on 5 Jan 2011 at 3:35

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

http://bailey.st/blog/2011/03/30/smooth-sec-1-1-the-first-bug/

"Few days ago a Smooth-Sec user have reported a problem running suricata with a 
pre-SSE3 Xeon processor. The error was an “illegal instruction” caused by 
some CPU architecture issue. With the help of Victor Julien we managed to fix 
the bug adding the “–disable-gccmarch-native”  flag in the configure 
option. "

./configure --disable-gccmarch-native
make

Original comment by doug.bu...@gmail.com on 30 Mar 2011 at 12:17

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Weird Xeon. Still triggering this bug 4 years later.

It did the trick on FreeBSD.

cd /usr/ports/security/suricata && make 
CONFIGURE_ARGS+=-disable-gccmarch-native -DBATCH install clean

Original comment by eks...@bsd.com.br on 16 Feb 2015 at 1:13

  • Added labels: ****
  • Removed labels: ****

fichtner added a commit to opnsense/ports that referenced this issue Jul 2, 2015
@fichtner
security/suricata: prevent illegal instruction crashes
47b9ba4 
via: Security-Onion-Solutions/security-onion#26
@kgleason kgleason mentioned this issue Oct 29, 2016
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-migrated Priority-Critical Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter