21 Aug
2006
21 Aug
'06
7:20 p.m.
We recently upgraded from version 1.0.0 to 1.1.0 from CVS of a few days ago.
After a couple of days of uptime, some SQL errors began to appear. First
there was this one:
Aug 21 10:07:07 eowyn OpenSER[19895]: ERROR: warning_builder: buffer
size exceeded
Aug 21 10:07:07 eowyn OpenSER[19895]: WARNING: warning skipped -- too big
Aug 21 10:07:07 eowyn OpenSER[19895]: submit_query:
Aug 21 10:07:07 eowyn OpenSER[19895]: db_insert: Error while submitting
query
Aug 21 10:07:07 eowyn OpenSER[19895]: ERROR:acc:acc_db_request: Error
while inserting to database
Then, some errors like this:
Aug 21 15:41:28 eowyn OpenSER[19895]: submit_query:
Aug 21 15:41:28 eowyn OpenSER[19895]: db_insert: Error while submitting
query
Aug 21 15:41:28 eowyn OpenSER[19895]: ERROR:acc:acc_db_request: Error
while inserting to database
Or the following:
Aug 21 19:02:10 eowyn OpenSER[20604]: submit_query:
Aug 21 19:02:10 eowyn OpenSER[20604]: db_query: Error while submitting query
Aug 21 19:02:10 eowyn OpenSER[20604]: NM ERROR: nm_hash_load_domains():
error with dbf.query()
The nm_hash_load_domains() function is a module of mine, that make an
SQL query. No problem with version 1.0.0.
Is there any SQL known problem in the 1.1.0 CVS version?
Maybe the first error caused some memory garbage?
Thanks.
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
22 Aug
22 Aug
2:24 p.m.
Hi Federico,
please check if when you get this errors your openser process is still
connected to the mysql server.
the interesting part is that no error string is present into the log:
OpenSER[19895]: submit_query:
regards,
bogdan
Federico Giannici wrote:
We recently upgraded from version 1.0.0 to 1.1.0 from
CVS of a few
days ago.
After a couple of days of uptime, some SQL errors began to appear.
First there was this one:
Aug 21 10:07:07 eowyn OpenSER[19895]: ERROR: warning_builder: buffer
size exceeded
Aug 21 10:07:07 eowyn OpenSER[19895]: WARNING: warning skipped -- too big
Aug 21 10:07:07 eowyn OpenSER[19895]: submit_query:
Aug 21 10:07:07 eowyn OpenSER[19895]: db_insert: Error while
submitting query
Aug 21 10:07:07 eowyn OpenSER[19895]: ERROR:acc:acc_db_request: Error
while inserting to database
Then, some errors like this:
Aug 21 15:41:28 eowyn OpenSER[19895]: submit_query:
Aug 21 15:41:28 eowyn OpenSER[19895]: db_insert: Error while
submitting query
Aug 21 15:41:28 eowyn OpenSER[19895]: ERROR:acc:acc_db_request: Error
while inserting to database
Or the following:
Aug 21 19:02:10 eowyn OpenSER[20604]: submit_query:
Aug 21 19:02:10 eowyn OpenSER[20604]: db_query: Error while submitting
query
Aug 21 19:02:10 eowyn OpenSER[20604]: NM ERROR:
nm_hash_load_domains(): error with dbf.query()
The nm_hash_load_domains() function is a module of mine, that make an
SQL query. No problem with version 1.0.0.
Is there any SQL known problem in the 1.1.0 CVS version?
Maybe the first error caused some memory garbage?
Thanks.
3:12 p.m.
Your suspect was correct: I was able to reproduce exactly the same
errors simply by stopping a restarting the MySQL server (thus breaking
old connections).
OpenSER is using MySQL library version 5.0.18.
The MySQL server is version 4.0.27.
Bye.
Bogdan-Andrei Iancu wrote:
Hi Federico,
please check if when you get this errors your openser process is still
connected to the mysql server.
the interesting part is that no error string is present into the log:
OpenSER[19895]: submit_query:
regards,
bogdan
Federico Giannici wrote:
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
We recently upgraded from version 1.0.0 to 1.1.0
from CVS of a few
days ago.
After a couple of days of uptime, some SQL errors began to appear.
First there was this one:
Aug 21 10:07:07 eowyn OpenSER[19895]: ERROR: warning_builder: buffer
size exceeded
Aug 21 10:07:07 eowyn OpenSER[19895]: WARNING: warning skipped -- too big
Aug 21 10:07:07 eowyn OpenSER[19895]: submit_query:
Aug 21 10:07:07 eowyn OpenSER[19895]: db_insert: Error while
submitting query
Aug 21 10:07:07 eowyn OpenSER[19895]: ERROR:acc:acc_db_request: Error
while inserting to database
Then, some errors like this:
Aug 21 15:41:28 eowyn OpenSER[19895]: submit_query:
Aug 21 15:41:28 eowyn OpenSER[19895]: db_insert: Error while
submitting query
Aug 21 15:41:28 eowyn OpenSER[19895]: ERROR:acc:acc_db_request: Error
while inserting to database
Or the following:
Aug 21 19:02:10 eowyn OpenSER[20604]: submit_query:
Aug 21 19:02:10 eowyn OpenSER[20604]: db_query: Error while submitting
query
Aug 21 19:02:10 eowyn OpenSER[20604]: NM ERROR:
nm_hash_load_domains(): error with dbf.query()
The nm_hash_load_domains() function is a module of mine, that make an
SQL query. No problem with version 1.0.0.
Is there any SQL known problem in the 1.1.0 CVS version?
Maybe the first error caused some memory garbage?
Thanks.
3:39 p.m.
Federico Giannici wrote:
Your suspect was correct: I was able to reproduce
exactly the same
errors simply by stopping a restarting the MySQL server (thus breaking
old connections).
Shouldn't the mysql module reconnect?
regards
klaus
OpenSER is using MySQL library version 5.0.18.
The MySQL server is version 4.0.27.
Bye.
Bogdan-Andrei Iancu wrote:
Hi Federico,
please check if when you get this errors your openser process is still
connected to the mysql server.
the interesting part is that no error string is present into the log:
OpenSER[19895]: submit_query:
regards,
bogdan
Federico Giannici wrote:
We recently upgraded from version 1.0.0 to 1.1.0
from CVS of a few
days ago.
After a couple of days of uptime, some SQL errors began to appear.
First there was this one:
Aug 21 10:07:07 eowyn OpenSER[19895]: ERROR: warning_builder: buffer
size exceeded
Aug 21 10:07:07 eowyn OpenSER[19895]: WARNING: warning skipped -- too
big
Aug 21 10:07:07 eowyn OpenSER[19895]: submit_query:
Aug 21 10:07:07 eowyn OpenSER[19895]: db_insert: Error while
submitting query
Aug 21 10:07:07 eowyn OpenSER[19895]: ERROR:acc:acc_db_request: Error
while inserting to database
Then, some errors like this:
Aug 21 15:41:28 eowyn OpenSER[19895]: submit_query:
Aug 21 15:41:28 eowyn OpenSER[19895]: db_insert: Error while
submitting query
Aug 21 15:41:28 eowyn OpenSER[19895]: ERROR:acc:acc_db_request: Error
while inserting to database
Or the following:
Aug 21 19:02:10 eowyn OpenSER[20604]: submit_query:
Aug 21 19:02:10 eowyn OpenSER[20604]: db_query: Error while
submitting query
Aug 21 19:02:10 eowyn OpenSER[20604]: NM ERROR:
nm_hash_load_domains(): error with dbf.query()
The nm_hash_load_domains() function is a module of mine, that make an
SQL query. No problem with version 1.0.0.
Is there any SQL known problem in the 1.1.0 CVS version?
Maybe the first error caused some memory garbage?
Thanks.
3:45 p.m.
Klaus Darilion wrote:
Federico Giannici wrote:
yes, it should.. the option is turned on by default...
http://openser.org/docs/modules/1.1.x/mysql.html#AEN68
Federico please apply the attached patch and send me the output.
regards,
bogdan
? modules/mysql/.dbase.c.swp
Index: modules/mysql/dbase.c
===================================================================
RCS file: /cvsroot/openser/sip-server/modules/mysql/dbase.c,v
retrieving revision 1.5
diff -u -r1.5 dbase.c
--- modules/mysql/dbase.c 14 Jul 2006 14:12:59 -0000 1.5
+++ modules/mysql/dbase.c 22 Aug 2006 13:44:38 -0000
@@ -87,6 +87,7 @@
return 0;
}
code = mysql_errno(CON_CONNECTION(_h));
+ LOG(L_ERR, "submit_query: errno code is %d\n", code);
if (code != CR_SERVER_GONE_ERROR && code != CR_SERVER_LOST) {
break;
}
Your suspect was correct: I was able to reproduce
exactly the same
errors simply by stopping a restarting the MySQL server (thus
breaking old connections).
Shouldn't the mysql module reconnect?
3:51 p.m.
Bogdan-Andrei Iancu wrote:
Federico please apply the attached patch and send me
the output.
OK, here it is:
Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query: errno code is 2013
Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query: errno code is 0
Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query:
Aug 22 15:50:34 eowyn OpenSER[16778]: db_query: Error while submitting query
Bye.
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
4:28 p.m.
Federico Giannici wrote:
Bogdan-Andrei Iancu wrote:
this is CR_SERVER_LOST
Federico please apply the attached patch and send
me the output.
OK, here it is:
Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query: errno code is 2013
Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query: errno code is 0
this means no error :-/
Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query:
Aug 22 15:50:34 eowyn OpenSER[16778]: db_query: Error while submitting
query
can you check on the mysql server if the query was performed or not?
because the strange part is that submit_query returns a non zero value
but the mysql_error reports no error...
regards,
bogdan
5:18 p.m.
Bogdan-Andrei Iancu wrote:
Federico Giannici wrote:
After the SQL server is restarted then every time a query is done by
OpenSER a new connection is opened (and then closed) ma the query is NOT
executed.
Here it is an example:
26 Connect ser(a)eowyn.neomedia.it on ser
26 Query SET NAMES latin1
26 Quit
Bye.
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
Aug 22 15:50:34 eowyn OpenSER[16778]:
submit_query:
Aug 22 15:50:34 eowyn OpenSER[16778]: db_query: Error while submitting
query
can you check on the mysql server if the query was performed or not?
because the strange part is that submit_query returns a non zero value
but the mysql_error reports no error...
23 Aug
23 Aug
6:27 p.m.
Any news on this problem?
Today I found that the problem occurs even when MySQL is NOT restarted.
Here it is example of a query that seems to fail but without an error
code (no previous error 2013):
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query: errno code is 0
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query:
Aug 23 16:36:58 eowyn OpenSER[28950]: db_query: Error while submitting query
As said before, a new connection is done to the MySQL server, but no
query is executed and the connection is immediately closed (instead of
keeping it open).
Bye.
Federico Giannici wrote:
Bogdan-Andrei Iancu wrote:
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
Federico Giannici wrote:
After the SQL server is restarted then every time a query is done by
OpenSER a new connection is opened (and then closed) ma the query is NOT
executed.
Here it is an example:
26 Connect ser(a)eowyn.neomedia.it on ser
26 Query SET NAMES latin1
26 Quit
Bye.
Aug 22 15:50:34 eowyn OpenSER[16778]:
submit_query:
Aug 22 15:50:34 eowyn OpenSER[16778]: db_query: Error while
submitting query
can you check on the mysql server if the query was performed or not?
because the strange part is that submit_query returns a non zero
value but the mysql_error reports no error...
26 Aug
26 Aug
6:10 p.m.
I have found that now the correct way to set the reconnection in MySQL
is to use the mysql_options() function. Here it is the description of
the MYSQL_OPT_RECONNECT option: "Enable or disable automatic
reconnection to the server if the connection is found to have been lost.
Reconnect has been off by default since MySQL 5.0.3; this option is new
in 5.0.13 and provides a way to set reconnection behavior explicitly.".
So I replaced the "ptr->con->reconnect = 1;" instruction in
"mysql/my_con.c" with the following lines BEFORE the call to
mysql_real_connect():
my_bool reconnect;
reconnect=1;
mysql_options(ptr->con,MYSQL_OPT_RECONNECT,(char*)&reconnect);
Well, it continues to DON'T work, but the behavior changed: it no longer
fails with error 0 (?). Now it fails with error 2013 and then 2006:
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2013
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2006
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2006
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: MySQL server has
gone away
Aug 26 17:38:53 eowyn OpenSER[10042]: db_insert: Error while submitting
query
Aug 26 17:38:53 eowyn OpenSER[10042]: db_insert_ucontact(): Error while
inserting contact
Aug 26 17:38:53 eowyn OpenSER[10042]: ERROR:usrloc:insert_ucontact:
failed to insert in database
Moreover, this time NO connection to the MySQL is actually done
(previously a connection was done, but without any query).
In conclusion, it appears to me that the reconnections under MySQL are a
great mess, and they probably depend on the actual version of client and
server used.
So, I suggest to don't depend on them. On the submit_query() function,
after the 3 attempts, if the error is still CR_SERVER_GONE_ERROR or
CR_SERVER_LOST, we should close the connection and try to reopen it.
What do you think?
Bye.
Federico Giannici wrote:
Any news on this problem?
Today I found that the problem occurs even when MySQL is NOT restarted.
Here it is example of a query that seems to fail but without an error
code (no previous error 2013):
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query: errno code is 0
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query:
Aug 23 16:36:58 eowyn OpenSER[28950]: db_query: Error while submitting
query
As said before, a new connection is done to the MySQL server, but no
query is executed and the connection is immediately closed (instead of
keeping it open).
Bye.
Federico Giannici wrote:
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
Bogdan-Andrei Iancu wrote:
Federico Giannici wrote:
After the SQL server is restarted then every time a query is done by
OpenSER a new connection is opened (and then closed) ma the query is
NOT executed.
Here it is an example:
26 Connect ser(a)eowyn.neomedia.it on ser
26 Query SET NAMES latin1
26 Quit
Bye.
Aug 22 15:50:34 eowyn OpenSER[16778]:
submit_query:
Aug 22 15:50:34 eowyn OpenSER[16778]: db_query: Error while
submitting query
can you check on the mysql server if the query was performed or not?
because the strange part is that submit_query returns a non zero
value but the mysql_error reports no error...
7:45 p.m.
Further reading the MySQL documentation, I found that:
"Prior to MySQL 5.0.19 [or 5.1.8], even if the reconnect flag in the
MYSQL structure is equal to 1, MySQL does not automatically reconnect
and re-issue the query as it doesn't know if the server did get the
original query or not."
And I was using just version 5.0.18!
Now I upgraded to version 5.0.22 and the problem now seems to be resolved.
Bye.
Federico Giannici wrote:
I have found that now the correct way to set the
reconnection in MySQL
is to use the mysql_options() function. Here it is the description of
the MYSQL_OPT_RECONNECT option: "Enable or disable automatic
reconnection to the server if the connection is found to have been lost.
Reconnect has been off by default since MySQL 5.0.3; this option is new
in 5.0.13 and provides a way to set reconnection behavior explicitly.".
So I replaced the "ptr->con->reconnect = 1;" instruction in
"mysql/my_con.c" with the following lines BEFORE the call to
mysql_real_connect():
my_bool reconnect;
reconnect=1;
mysql_options(ptr->con,MYSQL_OPT_RECONNECT,(char*)&reconnect);
Well, it continues to DON'T work, but the behavior changed: it no longer
fails with error 0 (?). Now it fails with error 2013 and then 2006:
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2013
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2006
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2006
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: MySQL server has
gone away
Aug 26 17:38:53 eowyn OpenSER[10042]: db_insert: Error while submitting
query
Aug 26 17:38:53 eowyn OpenSER[10042]: db_insert_ucontact(): Error while
inserting contact
Aug 26 17:38:53 eowyn OpenSER[10042]: ERROR:usrloc:insert_ucontact:
failed to insert in database
Moreover, this time NO connection to the MySQL is actually done
(previously a connection was done, but without any query).
In conclusion, it appears to me that the reconnections under MySQL are a
great mess, and they probably depend on the actual version of client and
server used.
So, I suggest to don't depend on them. On the submit_query() function,
after the 3 attempts, if the error is still CR_SERVER_GONE_ERROR or
CR_SERVER_LOST, we should close the connection and try to reopen it.
What do you think?
Bye.
Federico Giannici wrote:
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
Any news on this problem?
Today I found that the problem occurs even when MySQL is NOT
restarted. Here it is example of a query that seems to fail but
without an error code (no previous error 2013):
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query: errno code is 0
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query:
Aug 23 16:36:58 eowyn OpenSER[28950]: db_query: Error while submitting
query
As said before, a new connection is done to the MySQL server, but no
query is executed and the connection is immediately closed (instead of
keeping it open).
Bye.
Federico Giannici wrote:
Bogdan-Andrei Iancu wrote:
Federico Giannici wrote:
> Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query:
> Aug 22 15:50:34 eowyn OpenSER[16778]: db_query: Error while
> submitting query
can you check on the mysql server if the query was performed or not?
because the strange part is that submit_query returns a non zero
value but the mysql_error reports no error...
After the SQL server is restarted then every time a query is done by
OpenSER a new connection is opened (and then closed) ma the query is
NOT executed.
Here it is an example:
26 Connect ser(a)eowyn.neomedia.it on ser
26 Query SET NAMES latin1
26 Quit
Bye.
28 Aug
28 Aug
11:12 a.m.
Hi Federico!
Can you please make a patch and submit it at the bug tracker on sourceforge?
thanks
klaus
Federico Giannici wrote:
I have found that now the correct way to set the
reconnection in MySQL
is to use the mysql_options() function. Here it is the description of
the MYSQL_OPT_RECONNECT option: "Enable or disable automatic
reconnection to the server if the connection is found to have been lost.
Reconnect has been off by default since MySQL 5.0.3; this option is new
in 5.0.13 and provides a way to set reconnection behavior explicitly.".
So I replaced the "ptr->con->reconnect = 1;" instruction in
"mysql/my_con.c" with the following lines BEFORE the call to
mysql_real_connect():
my_bool reconnect;
reconnect=1;
mysql_options(ptr->con,MYSQL_OPT_RECONNECT,(char*)&reconnect);
Well, it continues to DON'T work, but the behavior changed: it no longer
fails with error 0 (?). Now it fails with error 2013 and then 2006:
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2013
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2006
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2006
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: MySQL server has
gone away
Aug 26 17:38:53 eowyn OpenSER[10042]: db_insert: Error while submitting
query
Aug 26 17:38:53 eowyn OpenSER[10042]: db_insert_ucontact(): Error while
inserting contact
Aug 26 17:38:53 eowyn OpenSER[10042]: ERROR:usrloc:insert_ucontact:
failed to insert in database
Moreover, this time NO connection to the MySQL is actually done
(previously a connection was done, but without any query).
In conclusion, it appears to me that the reconnections under MySQL are a
great mess, and they probably depend on the actual version of client and
server used.
So, I suggest to don't depend on them. On the submit_query() function,
after the 3 attempts, if the error is still CR_SERVER_GONE_ERROR or
CR_SERVER_LOST, we should close the connection and try to reopen it.
What do you think?
Bye.
Federico Giannici wrote:
Any news on this problem?
Today I found that the problem occurs even when MySQL is NOT
restarted. Here it is example of a query that seems to fail but
without an error code (no previous error 2013):
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query: errno code is 0
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query:
Aug 23 16:36:58 eowyn OpenSER[28950]: db_query: Error while submitting
query
As said before, a new connection is done to the MySQL server, but no
query is executed and the connection is immediately closed (instead of
keeping it open).
Bye.
Federico Giannici wrote:
Bogdan-Andrei Iancu wrote:
Federico Giannici wrote:
> Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query:
> Aug 22 15:50:34 eowyn OpenSER[16778]: db_query: Error while
> submitting query
can you check on the mysql server if the query was performed or not?
because the strange part is that submit_query returns a non zero
value but the mysql_error reports no error...
After the SQL server is restarted then every time a query is done by
OpenSER a new connection is opened (and then closed) ma the query is
NOT executed.
Here it is an example:
26 Connect ser(a)eowyn.neomedia.it on ser
26 Query SET NAMES latin1
26 Quit
Bye.
12:34 p.m.
Klaus Darilion wrote:
Hi Federico!
Can you please make a patch and submit it at the bug tracker on
sourceforge?
I don't know enough of the internals of the OpenSER sql connections
handling to implement it.
Moreover, as I said earlier, I solved the problem upgranding the MySQL
client library to a newer version.
Maybe, it could be useful to write somewhere that automatic
reconnections under MySQL work only with version >= 5.0.19 or 5.1.8.
Bye.
Federico Giannici wrote:
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
I have found that now the correct way to set the
reconnection in MySQL
is to use the mysql_options() function. Here it is the description of
the MYSQL_OPT_RECONNECT option: "Enable or disable automatic
reconnection to the server if the connection is found to have been
lost. Reconnect has been off by default since MySQL 5.0.3; this option
is new in 5.0.13 and provides a way to set reconnection behavior
explicitly.".
So I replaced the "ptr->con->reconnect = 1;" instruction in
"mysql/my_con.c" with the following lines BEFORE the call to
mysql_real_connect():
my_bool reconnect;
reconnect=1;
mysql_options(ptr->con,MYSQL_OPT_RECONNECT,(char*)&reconnect);
Well, it continues to DON'T work, but the behavior changed: it no
longer fails with error 0 (?). Now it fails with error 2013 and then
2006:
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2013
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2006
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: errno code is 2006
Aug 26 17:38:53 eowyn OpenSER[10042]: submit_query: MySQL server has
gone away
Aug 26 17:38:53 eowyn OpenSER[10042]: db_insert: Error while
submitting query
Aug 26 17:38:53 eowyn OpenSER[10042]: db_insert_ucontact(): Error
while inserting contact
Aug 26 17:38:53 eowyn OpenSER[10042]: ERROR:usrloc:insert_ucontact:
failed to insert in database
Moreover, this time NO connection to the MySQL is actually done
(previously a connection was done, but without any query).
In conclusion, it appears to me that the reconnections under MySQL are
a great mess, and they probably depend on the actual version of client
and server used.
So, I suggest to don't depend on them. On the submit_query() function,
after the 3 attempts, if the error is still CR_SERVER_GONE_ERROR or
CR_SERVER_LOST, we should close the connection and try to reopen it.
What do you think?
Bye.
Federico Giannici wrote:
Any news on this problem?
Today I found that the problem occurs even when MySQL is NOT
restarted. Here it is example of a query that seems to fail but
without an error code (no previous error 2013):
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query: errno code is 0
Aug 23 16:36:58 eowyn OpenSER[28950]: submit_query:
Aug 23 16:36:58 eowyn OpenSER[28950]: db_query: Error while
submitting query
As said before, a new connection is done to the MySQL server, but no
query is executed and the connection is immediately closed (instead
of keeping it open).
Bye.
Federico Giannici wrote:
Bogdan-Andrei Iancu wrote:
> Federico Giannici wrote:
>
>> Aug 22 15:50:34 eowyn OpenSER[16778]: submit_query:
>> Aug 22 15:50:34 eowyn OpenSER[16778]: db_query: Error while
>> submitting query
>
> can you check on the mysql server if the query was performed or
> not? because the strange part is that submit_query returns a non
> zero value but the mysql_error reports no error...
After the SQL server is restarted then every time a query is done by
OpenSER a new connection is opened (and then closed) ma the query is
NOT executed.
Here it is an example:
26 Connect ser(a)eowyn.neomedia.it on ser
26 Query SET NAMES latin1
26 Quit
Bye.
6737
days inactive
6744
days old
12 comments
3 participants
participants (3)
-
Bogdan-Andrei Iancu -
Federico Giannici -
Klaus Darilion