Project

General

Profile

Actions
Copy link

Bug #3130

closed

segfault at 0 ip 0000000000000000 sp 00007fff94ff5878 error 14 in suricata[400000+8be000]

Added by Srijan Nandi over 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Affected Versions:
Effort:
Difficulty:
Label:

Description

Hello Everyone,

I get the following error and suricata gives a segmentation fault. I am running suricata in IPS mode in af-packet.

This is Suricata version 5.0.0-dev (f43584661 2019-08-23). Using Intel X710 NIC cards.

Linux suricata-teletalk 4.19.0-0.bpo.5-amd64 #1 SMP Debian 4.19.37-5+deb10u2~bpo9+1 (2019-08-16) x86_64 GNU/Linux

kernel: [15032.337542] W#04-enp176s0f117422: segfault at 0 ip 0000000000000000 sp 00007fff94ff5878 error 14 in suricata[400000+8be000]
kernel: [15032.337550] Code: Bad RIP value.

I did a gdb trace and here is what I see:

#0 0x00007ffff2fbd28d in nanosleep () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007ffff2fe6dc4 in usleep (useconds=<optimized out>) at ../sysdeps/posix/usleep.c:32
#2 0x00000000006a55ca in SuricataMainLoop (suri=<optimized out>) at suricata.c:2874
#3 main (argc=<optimized out>, argv=<optimized out>) at suricata.c:3025

Thanks and Regards,
-=Srijan Nandi

Actions
Copy link
 #1

Updated by Victor Julien over 5 years ago

  • Tracker changed from Support to Bug
  • Priority changed from Urgent to Normal
Actions
Copy link
 #2

Updated by Victor Julien over 5 years ago

  • Affected Versions deleted (5.0.0)
Actions
Copy link
 #3

Updated by Andreas Herz over 5 years ago

  • Assignee set to OISF Dev
  • Target version set to TBD
Actions
Copy link
 #4

Updated by Peter Manev over 5 years ago

Is it possible to reproduce that at will/repeatedly ?

Actions
Copy link
 #5

Updated by Srijan Nandi over 5 years ago

I did 5 installations of 5.0.0-dev on Debian 9 and did not face this issue. On the 6th installation of 5.0.0-dev on Debian 9, I encountered this issue.

Because I was in a hurry, replaced the OS to Ubuntu -18.04 and changed suricata to 4.1.4 (Stable Release) and it started working without an issue.

Therefore, I am not sure whether it can be reproducible at will or not.

Actions
Copy link
 #6

Updated by Victor Julien almost 5 years ago

  • Status changed from New to Closed
  • Assignee deleted (OISF Dev)
  • Target version deleted (TBD)

Closing as there is no way to find the problem based on the provided info. If you encounter it again, please open a new ticket. Thanks!

Actions
Copy link

Also available in: Atom PDF