Actions
Bug #1500
closedsuricata.log
Affected Versions:
Effort:
Difficulty:
Label:
Description
Suricata version 2.1dev (rev 45fc619)
I am noticing for some time now that suricata.log is not correctly populated/written to. - example:
[10989] 7/7/2015 -- 22:37:42 - (source-af-packet.c:1069) <Info> (AFPSynchronizeStart) -- Starting to read on AFPacketeth26 [10997] 7/7/2015 -- 22:37:42 - (source-af-packet.c:1069) <Info> (AFPSynchronizeStart) -- Starting to read on AFPacketeth214 [10988] 7/7/2015 -- 22:37:42 - (source-af-packet.c:1069) <Info> (AFPSynchronizeStart) -- Starting to read on AFPacketeth25 [10984] 7/7/2015 -- 22:37:42 - (source-af-packet.c:1069) <Info> (AFPSynchronizeStart) -- Starting to read on AFPacketeth21 [10999] 7/7/2015 -- 22:37:42 - (source-af-packet.c:1069) <Info> (AFPSynchronizeStart) -- Starting to read on AFPacketeth216 [10994] 7/7/2015 -- 22:37:42 - (source-af-packet.c:1069) <Info> (AFPSynchronizeStart) -- Starting to read on AFPacketeth211 [10987] 7/7/2015 -- 22:37:42 - (source-af-packet.c:1069) <Info> (AFPSynchronizeStart) -- Starting to read on AFPacketeth24 [10995] 7/7/2015 -- 22:37:42 - (sou root@suricata:/home/pevman/oisf#
This is just one case. I also have cases where the suricata.log is entirely empty or not updated properly after a kill -15 signal.
Thank you
Updated by Victor Julien over 9 years ago
- Target version set to 3.0RC1
Strange. Your disk isn't full?
Updated by Peter Manev over 9 years ago
- Status changed from New to Closed
I think this was a case specific to my set up scenario.
Not related to Suricata.
Actions