Did this cause your DB to fail again? Restarting BY should fix it.


On Wed, Jul 2, 2014 at 8:16 PM, James Lay <jlay@slave-tothe-box.net> wrote:
On Wed, 2014-07-02 at 12:47 -0400, Bamm Visscher wrote:
Hi James,

This does look like there is a TZ issue at play. I'll dig deeper when I get a chance this evening. One way to get back up would be to temporarily disable the autocat rule that is triggering the update.


And again...moments ago:

Jul  2 18:01:59 x.x.x.x barnyard2[15859]: FATAL ERROR: sguil: Expected Confirm 904 and got: Failed to insert 904: mysqlexec/db server: Duplicate entry 4-904 for key PRIMARY#012.  I'm officially at a loss at one to do now besides roll back to 0.8.0.


Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
Sguil-users mailing list

sguil - The Analyst Console for NSM