Hi Andrei,
A new crash happend today !
It was impossible to restart SER. During this time I could collect logs from syslog by activating ser debug (ie. facility local0, etc.).
The solution have consisted in flushing Location table to be able to restart SER...
I attach the gdb output and syslog trace to this email. Do you see that the problem is same as the previous one ?
Regards,
Adrien
Le jeudi 10 septembre 2009 à 18:36 +0200, inge a écrit :
Hi Andrei,
Thank you for this detailed answer.
Indeed, update to 0.9.7 will be more easier than SER 2.0. Our priority is to avoid a lot of bugs.
We are not able to reproduce the crash...so we'll see. Probably we will do an update to 0.9.7.
Regards,
Adrien
Le mercredi 09 septembre 2009 à 13:11 +0200, Andrei Pelinescu-Onciul a écrit :
On Sep 04, 2009 at 18:06, inge inge@legos.fr wrote:
Hello Andrei,
I wonder what is involved in migration to SER 2.0 versus 0.9.5. I read that UID is used now to identify the users instead of username for example, so we can anticipate impacts on internal processes and SERWeb.
Yes, uid and did (for domains) are now used internally. There is a script which might help in migrating a database: http://www.iptel.org/ser/migrate_db
Can I find a detailed list which these changelog ?
Try http://www.iptel.org/basic_changes_in_configuration_file_0 http://git.sip-router.org/cgi-bin/gitweb.cgi?p=ser;a=blob;f=ser/NEWS;h=02543... http://git.sip-router.org/cgi-bin/gitweb.cgi?p=ser;a=blob;f=ser/ChangeLog;h=...
I don't remember exactly, hopefully there is a more complete migration guide somewhere (maybe somebody else can help if I missed anything).
Is it not more reasonnable to migrate in 0.9.7? Mainly to solve our initial bug with Seg Fault and optionnaly to have new features.
Yes, in your case migration to 0.9.7 should be painless (there are no config or db changes, only bugfixes, so you wouldn't need to change anything).
Andrei
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev