pping is unable to post boxUp/boxDown events

[Morten Brekkevold]

It appears the fix for bug 1403365 has caused a regression that stops the pping from being able to post events, essentially breaking one of the most important features of NAV.

Unfortunately, this made it into the 4.2.4 release, which we have now retracted.

These symptomatic errors can be seen in pping.log:

[2015-03-20 11:47:52] db.py:execute:167 [Critical] Throwing away update...
[2015-03-20 11:47:52] db.py:execute:165 [Critical] insert or update on table "eventqvar" violates foreign key constraint "eventqvar_eventqid_fkey"
DETAIL: Key (eventqid)=(1287006) is not present in table "eventq".

[2015-03-20 11:47:52] db.py:execute:167 [Critical] Throwing away update...
[2015-03-20 11:47:52] db.py:execute:165 [Critical] null value in column "subid" violates not-null constraint

[Morten Brekkevold (mbrekkevold)]

There may be more components than pping that post events with explicit subid=NULL values, so the best option for a quick fix may be to add a database trigger that translates NULL values in the subid field to empty strings.

[Morten Brekkevold (mbrekkevold)]

fix here: https://nav.uninett.no/hg/stable/rev/f9a76d7352c6