[OpenSER-Users] OpenSER failure when MySQL redundant database fails

[Arturo Díaz Almagro]

Hi all,

I am going to try to backport the changes in the trunk version of the db
management to openser 1.2 branch. I have performed a diff and found new
files and significant changes in some others. My main concern is related
with the problem exposed so I only would like to modify the part of the code
that fixes the problem.

I would be please if anyone could help me to locate that part of the code.
After testing and confirmation from the people who mantains this portion of
OpenSER I will share the changes.

Kind regards.

2008/2/25, Henning Westerholt <henning.westerholt at 1und1.de>:
>
> On Monday 25 February 2008, Arturo Díaz Almagro wrote:
> > Please, see my comments below.
>
> > > [..]
>
> > > For recent mysql driver versions this is not needed anymore, i've
> > > committed in revision 3606 a improvement to the trunk version of
> openser
> > > that uses the recently introduced extensions in the mysql lib. This
> could
> > > be easily backported to your version, take a look into the mysql
> > > documentation if this different timeouts are supported on your driver
> > > version.
> >
> > Does that mean that I could compile the mysql module in the trunk
> version
> > and replace  the old mysql.so module by the new generated one from the
> > trunk? Is it fully backward compatible?
> >
> > Kind regards.
>
>
> Hi Arturo Díaz Almagro,
>
> (lets continue this discussion on the user list)
>
> No, but this will not work at all. Even replacing the code and recompile
> will
> not work, the changes were to extensive. You need to backport the changes
> from the mentioned revision to the driver you use internally in your
> company.
> You could get the changes with 'svn diff' or search on the devel list for
> the
> commit message.
>
> Cheers,
>
>
> Henning
>



-- 
Arturo Díaz

Contact me on
FWD: 870436
Skype: arturo.diaz.almagro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20080226/0d4a9ca5/attachment.htm>