28 Sep
2009
28 Sep
'09
5:02 a.m.
Hello Andrei,
We need to wait for 0.9.9 ?
Or should we just patch the current 0.9.8 to avoid the bug ?
Otherwise, do you have an idea of the value we should set for
"PKG_MEM_POOL_SIZE" and avoid a truncate of location to restart SER ?
Regards,
Adrien.
Le jeudi 24 septembre 2009 à 23:09 +0200, Andrei Pelinescu-Onciul a
écrit :
On Sep 24, 2009 at 15:49, inge <inge(a)legos.fr>
wrote:
Hi Andrei,
Thanks for the 0.9.8 release.
We upgraded our proxy yesterday with sucess.
But we had another crash of SER in this morning.
The cause seem to be defferent than the previous one.
Attached is a backtrace from the coredump.
Is there a bug related to that in the last 0.9.x version ?
No, this is a new one.
It was introduced in 0.9.7. A very safe looking optimization was
backported from unstable (at that time). Unfortunately the optimization
had a bug and although it was quickly fixed in unstable, the fix was not
backported to 0.9.7.
Try the attached patch (patch -p2 < auth_db_empty_usernames_fix.patch ).
It seems I'll have to release 0.9.9 :-(
Andrei