Sagan Git Update

5 views
Skip to first unread message

Champ Clark III

unread,
Mar 30, 2012, 9:25:51 PM3/30/12
to saga...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Crash recovery for SQL (MySQL/PostgreSQL/etc) for when Sagan is doing
direct database writes.

When Sagan "crashes", it may not be able to properly write out the
"last_cid" information.

The update checks the event tables MAX(cid) to the sensor tables
last_cid. If there is a mismatch, the last_cid is rolled forward and
the mismatch is corrected.

This is a step to hopefully clear up duplicate INSERT records when an
event is triggered and the last_cid is incorrect.


- --
- - Champ Clark III (ccl...@quadrantsec.com)
Quadrant Information Security (http://quadrantsec.com)
Key Fingerprint: 2E56 C2EB 1B25 C517 D5BA 2DCF 5E70 B2F8 0381 878A
GPG Key ID: 0381878A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPdl0fAAoJENnmXt7Lmc3KoEIH/jhKjixDIDcqYMVQpYrHRXg7
Rip0gzHIjsAEl55WaWB9a2F2yqd0dtoYx3fsGeim6XtunpvdnoQCPmvn6Lt56hA0
9u9+5ERnM7Iax2lngjCVcf7Uelx7HjLNI6DHvQN0XOfK+8Q8qFYEV4cxVlzWfJXS
k5Emyn2OzWC9P7rEkpK7VSJdZd1l71wbK/Jsx7nXpDMKibiW6yGy5bscIWCTfc3x
yI3wjX4k9tagMjggkg0vk+KzfZwn44SsTA44n6AiNXO8LAYdxxvcOpv2D3vU5Gay
4FKGmmiQo9uwGjNnDoQ5G93MdVhRQ38h0bXtfabTGXK3EDOLaG3AxNFRYQQlQtA=
=TCel
-----END PGP SIGNATURE-----

Reply all
Reply to author
Forward
0 new messages