-
Notifications
You must be signed in to change notification settings - Fork 190
mysql Fatal Error: Duplicate key #256
Comments
Might not be relevant to answering this question, but could you please tell me what OS and version you are using? |
Ubuntu Server 19.10 eoan for arm64 on a raspberry pi 4 |
I thought BASE requires a php 5.5 version to run on, which is not supported for 19.10 eoan. you can only run php 5.6+ on ubuntu 14.04 onward... how did you achieve this? |
I got a fork of base that runs with php 7 |
Thank You, better late than never. |
Yeah, BASE is an awesome front end for SNORT. In a twitter conversation with @secureideas at the beginning of 2019, I was asked if I was planning on maintaining BASE. Wasn't sure then, as I had only ported it to PHP 7x for my own use. At the time, I really didn't know a lot about PHP or SQL. However, several years earlier, I heard an interview with Kevin on a podcast. He was sharing about how he had come to develop BASE in the first place. During the podcast he jumped out of the middle of the interview for five minutes to tell his kids goodnight. You can't help but respect that. What I remember Kevin sharing on that podcast was:
When Kevin told me last year that:
Seriously, I could not say no to the man who inspires me to get involved even though I am definitely not the best out there. 😄 I told him:
Kevin replied:
As I told him then:
Thank you @secureideas for the inspiration. 😄 |
I am not sure how to respond to this. :). I am glad to see others building cool things! I am not sure I should inspire, but am thrilled you were! |
@NathanGibbs3 as a newcomer to the world of open-source i find your contribution extremely helpful and inspiring as well. Would love to contribute to this wholesome community consisting of people like @secureideas... You guys are great! |
"output database: log " or "output database: alert"
|
I'm using
Then using barnyard2 to log into DB
|
At some point I get duplicate key errors for barnyard. I'm not sure what caused it. There are multiple possibilities
kill -SIGHUP
signal orservice barnyard2 restart
The main issue here is that this is deemed a fatal error and the demon stops. At this point systemd tries to restart it, but it then runs into the same failure again until systemd gives up.
It would be nice if duplicate keys would be checked on insert and if this would be handled more gracefully. (i.e. Report error to log, rollback transaction, skip event, carry on)
The error in question is:
Also please fix your indentation in spo_database.c
The text was updated successfully, but these errors were encountered: