Check the archives. I've answered this a couple of times already.

mysql 5.0.X has modified the default behaviour of how the socket timeout works. By default, it times out connections after a period of time. There was a patch after about 5.0.12 to allow people to modify this behaviour, but the patch didn't work until 5.0.19.

In order to get SER 0.9.X to work with 5.0.19 and above and reconnect after a timed out socket, you need to modify the my_con.c in $SER-SRC/modules/mysql and recompile the mysql module.

I've attached a modified my_con.c file that has the correct options to utilise the patched mysql code. It will fix the reconnect issues (allowing SER to reconnect once the socket has timed out).

N.

Andrey Kuprianov wrote:

Im also having this problem. I even upgraded SER to 0.9.7-pre8, but
still the same.
I tend to think, though, that this is a MySQL version problem. I
installed MySQL 5.0 from Ubuntu's packages. I think reinstalling MySQL
or just upgrading it (or maybe downgrading to 4.1), should do the
trick.

On 5/24/07, Nhadie <nhadie@tbgi.net.ph> wrote:

Hi All


How can i make sure that when mysql dies, ser will not allow calls anymore?
Because i had a problem, when mysql died, ser still continued to allow
calls and i was not able to account it.

How can i resolve this. Thank You in Advance.

Regards
Ronald




_______________________________________________
Serusers mailing list
Serusers@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers

_______________________________________________
Serusers mailing list
Serusers@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers