Home > Fatal Error > Fatal Error Database Mysql_error Duplicate Entry

Fatal Error Database Mysql_error Duplicate Entry

Please don't fill out this field. Already have an account? UPDATE reference SET ref_tag='blog.sipvicious.org/' WHERE ref_id='65615' AND ref_system_id='5'; So I've executed below SQL too, then other duplicate entry was detected. Which error was it reporting, etc... -elz Re: [Snort-users] Barnyard2 issue w/unified2 ? have a peek at these guys

Get down > to code-level detail for bottlenecks, with <2% overhead. News: Get your appliances, shirts and more!https://store.pfsense.org Home Help Search Login Register pfSense Forum» pfSense English Support» Packages» IDS/IPS» If you are having Barnyard2 troubles with the last Snort update -- What can I do with it? A race condition could develop where two Barnyard2 processes are attempting to insert the same signature at essentially the same time. https://github.com/firnsy/barnyard2/issues/102

Collaborator binf commented Oct 18, 2013 On Fri, Oct 18, 2013 at 6:11 AM, s-takehana [email protected] wrote: I've executed below SQL, but this issue still occurs. The Snort and Suricata packages on pfSense use this updated version since the FreeBSD ports tree was also updated.Bill Logged fearnothing Jr. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_________________________________ \ ______________
Snort-users mailing list
[email protected]
Go to this URL to change user options or unsubscribe:

Read 3 records cool-ids# What is happening? You can either clear the ole table or delete the offending entry in sig_reference and in both case restart the process. Oct 8 19:51:19 suricata barnyard2: #012#012+[ Signature Suppress list ]+#012---------------------------- Oct 8 19:51:19 suricata barnyard2: +[No entry in Signature Suppress List]+ Oct 8 19:51:19 suricata barnyard2: ----------------------------#012+[ Signature Suppress list ]+#012 I would like to get to the bottom of this problem in order to see if I need to change something in the way Barnyard2 is configured within Snort.Did this only

Collaborator binf commented Oct 22, 2013 On Sun, Oct 20, 2013 at 8:56 PM, s-takehana [email protected]: All right. Reload to refresh your session. It has been posted for a while, and hopefully they can soon get some time to review and approve.Bill Logged fearnothing Jr. https://forum.pfsense.org/index.php?topic=75357.0 OS: Debian 7 Wheezy (MySQL 5.5 installed through apt) Suricata IDS 2.0.4 installed from source Barnyard2 2.1.13 (and 2.1.12) installed from https://github.com/firnsy/barnyard — Reply to this email directly or view it

I understand that I can withdraw my consent at any time. For example: > [[email protected] ~]$ sudo grep barn /var/log/messages|grep Duplicate > Aug 13 09:59:08 snort-campus barnyard2[29867]: FATAL ERROR: database > mysql_error: Duplicate entry '167807-1' for key > 'PRIMARY'#012#011SQL=[INSERT INTO sig_reference > It is being reviewed by the pfSense Core Team developers. All instances crash with the same error.

Is barnyard2.conf as follows a cause? This Site SELECT q1.sig_gid,q1.sig_sid,q1.a FROM (SELECT si Skip to content Ignore Learn more Please note that GitHub no longer supports old versions of Firefox. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Snort-users mailing list [email protected] Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://sourceforge.net/mailarchive/forum.php?forum_name=snort-users Please visit http://blog.snort.org to stay current on all the latest Snort(use VRT rules) -> unified2 -> Barnyard2 -> DB1 and DB2 Suricata(use ET PRO rules) -> unified2 -> Barnyard2 -> DB2 This issue happens in DB2.

I've followed all the instructions here and yet I'm still having the problem. More about the author Each sensor has it's own ID: < Sensor > < Name > 23 snort-campus-1:p1p1:p1p1 24 snort-campus-3:p1p1:p1p1 25 snort-campus-2:p1p1:p1p1 26 snort-campus-4:p1p1:p1p1 27 snort-dorms-1:p1p1:p1p1 28 snort-dorms-2:p1p1:p1p1 29 snort-dorms-3:p1p1:p1p1 30 snort-dorms-4:p1p1:p1p1 The "issue" generally My AccountSearchMapsYouTubePlayNewsGmailDriveCalendarGoogle+TranslatePhotosMoreShoppingWalletFinanceDocsBooksBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages To use Google Groups Discussions, please enable JavaScript in your browser settings, and then refresh this page. . I'm planning it.

you definitely do not want more than one instance using the same PID file... I did a quick look in the > configuration, but I didn't see what option is used to differentiate > the instances, so I suspect this is the root of my From: beenph - 2013-08-15 16:17:52 On Thu, Aug 15, 2013 at 11:52 AM, John Ives wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jeff, > > check my blog I attach the output below.

Please refer to our Privacy Policy or Contact Us for more details You seem to have CSS turned off. I don't confirm to change the signature from Oinkmaster logs for two weeks. Make sure you only have 1 barnyard process running on each box Jason ________________________________ From: Jen Andre To: Jeff Kell Cc: [email protected] ; [email protected]

It occurred to me, that two mysql connections were established by by2.

Please tell me why this duplicate error happens. You could check ref's and see what changed and do as above or., you can delete sig_reference table without an issue but i would not recommend that you clear reference table, I do have some overlap rules on my 2 sensors (LAN and WAN), and only 1 will run continually, usually the first one I start. some apps have provisions for this while others do not...

Ss 9:56AM 1:14.18 /usr/local/bin/barnyard2 -r 6190 -f snort_6190_em0.u2 --pid-path /var/run --nolock-pidfile -c /usr/pbi/snort-i386/etc/snort/snort_6190_em0/barnyard2.conf -d /var/log/snort/snort_em06190 -D -q Logged bmeeks Hero Member Posts: 2736 Karma: +622/-0 Re: If you are having What can I do with \ it?


It's fresh and empty DB, that populated when \ barnyard2 starts, but failes in no more than 5 recors with Duplicate entry \ error.


------------------------------------------------------------------------------
So i assume that mabey you have a line in both sid-msg.map file that is conflicting? news Which error was it reporting, etc...

Did you upgrade to 2-1.13 from a previous version? Jeff Re: [Snort-users] Barnyard2 issue w/unified2 ? Oct 8 19:53:15 suricata barnyard2: database: compiled support for (mysql) Oct 8 19:53:15 suricata barnyard2: database: configured to use mysql Oct 8 19:53:15 suricata barnyard2: database: schema version = 107 Oct For example: > > [[email protected] ~]$ sudo grep barn /var/log/messages|grep Duplicate > Aug 13 09:59:08 snort-campus barnyard2[29867]: FATAL ERROR: database > mysql_error: Duplicate entry '167807-1' for key > 'PRIMARY'#012#011SQL=[INSERT INTO sig_reference

Before you upgraded did you read the release notes? John On 8/13/2013 6:11 PM, Jeff Kell wrote: > On 8/13/2013 6:38 PM, Weir, Jason wrote: >> I've experienced this issue when I mistakenly start a second >> barnyard process without I'm a bit loathe to recreate the database (loss of current events) but if beenph insists that's the only sure fix, I may have to bite the bullet. It will not be fixed with a different database engine.

Barnyard2 exiting database: Closing connection to database "snort" database: Closing connection to database "snort" =============================================================================== Record Totals: Records: 3 Events: 1 (33.333%) Packets: 2 (66.667%) Unknown: 0 (0.000%) Suppressed: 0 (0.000%) on the eth0 interface, it is snort_eth0.pid... Barnyard2 recommended? SELECT q1.sig_gid,q1.sig_sid,q1.a FROM (SELECT sig_gid,sig_sid,count(*) AS a FROM signature WHERE sig_priority='0' GROUP BY sig_gid,sig_sid) AS q1 WHERE q1.a > 1; DB1 +---------+---------+-----+ | sig_gid | sig_sid | a | +---------+---------+-----+ |

Please keep mailing list traffic on the list unless private contact is specifically requested and granted. I'm compelled to delete every row in sig_reference table before executing Barnyard2.