I was able to get ser (0.9.6) running with mysql 4.1.16, but upon upgrading to mysql 5.0.21, I am having problems again. MySQL loads fine, as does SER, but when my UA attempts to register with the database, I see these errors throughout my mysql log:
[Warning] Aborted connection 109 to db: 'nv_proxy' user: 'nvproxy' host: 'localhost' (Got an error reading communication packets)
If I try to make a call, I get a 407 Proxy Authentication Required failure, which I expect. There are no errors in /var/log/messages that indicate what exactly the problem is with my database access, so ser seems to think things are okay.
Has anyone seen this before or have any idea what I might have missed in my upgrade from 4.1.16 to 5.0.21 MySQL?
Thanks in advance, Steve
Maybe you upgraded your mysql libraries too.
Try compiling SER again with new libraries
Stephen Helfen wrote:
I was able to get ser (0.9.6) running with mysql 4.1.16, but upon upgrading to mysql 5.0.21, I am having problems again. MySQL loads fine, as does SER, but when my UA attempts to register with the database, I see these errors throughout my mysql log:
[Warning] Aborted connection 109 to db: 'nv_proxy' user: 'nvproxy' host: 'localhost' (Got an error reading communication packets)
If I try to make a call, I get a 407 Proxy Authentication Required failure, which I expect. There are no errors in /var/log/messages that indicate what exactly the problem is with my database access, so ser seems to think things are okay.
Has anyone seen this before or have any idea what I might have missed in my upgrade from 4.1.16 to 5.0.21 MySQL?
Thanks in advance, Steve
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I did do that...no joy. Any other suggestions?
From: Rodrigo Gonzalez rjgonzale@gmail.com To: Stephen Helfen steve_helfen@hotmail.com CC: serusers@lists.iptel.org Subject: Re: [Serusers] New MySQL results in aborted connections from SER Date: Wed, 17 May 2006 18:00:04 -0300
Maybe you upgraded your mysql libraries too.
Try compiling SER again with new libraries
Stephen Helfen wrote:
I was able to get ser (0.9.6) running with mysql 4.1.16, but upon upgrading to mysql 5.0.21, I am having problems again. MySQL loads fine, as does SER, but when my UA attempts to register with the database, I see these errors throughout my mysql log:
[Warning] Aborted connection 109 to db: 'nv_proxy' user: 'nvproxy' host: 'localhost' (Got an error reading communication packets)
If I try to make a call, I get a 407 Proxy Authentication Required failure, which I expect. There are no errors in /var/log/messages that indicate what exactly the problem is with my database access, so ser seems to think things are okay.
Has anyone seen this before or have any idea what I might have missed in my upgrade from 4.1.16 to 5.0.21 MySQL?
Thanks in advance, Steve
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
how about creating a symbolic link to the libmysqlclient.so.15 (not sure .what). Just find this file (in my system it's under /usr/local/lib/mysql/ directory, i dont know about yours) and make a symbolic link
ln -s libmysqlclient.so.15 libmysqlclient.so.10
hope that helps.
On 5/18/06, Stephen Helfen steve_helfen@hotmail.com wrote:
I did do that...no joy. Any other suggestions?
From: Rodrigo Gonzalez rjgonzale@gmail.com To: Stephen Helfen steve_helfen@hotmail.com CC: serusers@lists.iptel.org Subject: Re: [Serusers] New MySQL results in aborted connections from SER Date: Wed, 17 May 2006 18:00:04 -0300
Maybe you upgraded your mysql libraries too.
Try compiling SER again with new libraries
Stephen Helfen wrote:
I was able to get ser (0.9.6) running with mysql 4.1.16, but upon upgrading to mysql 5.0.21, I am having problems again. MySQL loads fine, as does SER, but when my UA attempts to register with the database, I see these errors throughout my mysql log:
[Warning] Aborted connection 109 to db: 'nv_proxy' user: 'nvproxy' host: 'localhost' (Got an error reading communication packets)
If I try to make a call, I get a 407 Proxy Authentication Required failure, which I expect. There are no errors in /var/log/messages that indicate what exactly the problem is with my database access, so ser seems to think things are okay.
Has anyone seen this before or have any idea what I might have missed in my upgrade from 4.1.16 to 5.0.21 MySQL?
Thanks in advance, Steve
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
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Andrey Kouprianov -
Rodrigo Gonzalez -
Stephen Helfen