6 Mar
2015
6 Mar
'15
9:09 p.m.
Hello,
I’m not sure if this is the correct forum for this question but here goes…
I’m facing an issue setting up a sipcapture server. I’m seeing several db errors in the
logs:
Mar 6 10:45:13 sipcapture /usr/local/sbin/kamailio[37872]: ERROR: db_mysql
[km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Data too long for column
'correlation_id' at row 1
I did a packet capture of the sql query and it appears that the value for the
correlation_id is omitted. Interestingly its not all packets but maybe 60%. Do I have
something misconfigured?
Thanks,
Spencer
A sanitized version of the query is below:
insert into sip_capture
(date,micro_ts,method,reply_reason,ruri,ruri_user,from_user,from_tag,to_user,to_tag,pid_user,contact_user,auth_user,callid,callid_aleg,via_1,via_1_branch,cseq,reason,content_type,auth,user_agent,source_ip,source_port,destination_ip,destination_port,contact_ip,contact_port,originator_ip,originator_port,proto,family,rtp_stat,type,node,correlation_id,msg
) values ('2015-03-06
10:50:22',1425667824109829,'180','Ringing','','','+12052222222','gK007b315d','+12051111111','3Sr0m4vyjy2UK','','+12051111111','','2080378443_116641441@1.1.1.1','','SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7','z9hG4bK00B5617ed64f1ebf7d7','1888238783
INVITE','','','','','3.3.3.3',5060,'1.1.1.1',5060,'2.2.2.2',6038,'',0,1,2,'',2,'node1:2001','SIP/2.0
180 Ringing\r\nVia: SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route:
<sip:3.3.3.3;lr;ftag=gK007b315d>\r\nFrom:
<sip:+12052222222@1.1.1.1>;tag=gK007b315d\r\nTo:
<sip:+12051111111@3.3.3.3>;tag=3Sr0m4vyjy2UK\r\nCall-ID:
2080378443_116641441(a)1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact:
<sip:+12051111111@2.2.2.2:6038;transport=udp>\r\nAccept: application/sdp\r\nAllow:
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE\r\nSupported:
path\r\nContent-Length: 0\r\n\r\n','SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route:
<sip:3.3.3.3;lr;ftag=gK007b315d>\r\nFrom:
<sip:+12052222222@1.1.1.1>;tag=gK007b315d\r\nTo:
<sip:+12051111111@3.3.3.3>;tag=3Sr0m4vyjy2UK\r\nCall-ID:
2080378443_116641441(a)1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact:
<sip:+12051111111@2.2.2.2:6038;transport=udp>\r\nAccept: application/sdp\r\nAllow:
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE\r\nSupported:
path\r\nContent-Length: 0\r\n\r\n')
10 Mar
10 Mar
3:08 p.m.
Hello,
maybe the values are too big for the defined column size. You can try
altering the table and increase the size for correlation_id column.
I cc-ed Alexandr, who wrote the module and can eventually comment more
on the issue.
Cheers,
Daniel
On 06/03/15 20:09, Spencer Thomason wrote:
Hello,
I’m not sure if this is the correct forum for this question but here goes…
I’m facing an issue setting up a sipcapture server. I’m seeing several db errors in the
logs:
Mar 6 10:45:13 sipcapture /usr/local/sbin/kamailio[37872]: ERROR: db_mysql
[km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Data too long for column
'correlation_id' at row 1
I did a packet capture of the sql query and it appears that the value for the
correlation_id is omitted. Interestingly its not all packets but maybe 60%. Do I have
something misconfigured?
Thanks,
Spencer
A sanitized version of the query is below:
insert into sip_capture
(date,micro_ts,method,reply_reason,ruri,ruri_user,from_user,from_tag,to_user,to_tag,pid_user,contact_user,auth_user,callid,callid_aleg,via_1,via_1_branch,cseq,reason,content_type,auth,user_agent,source_ip,source_port,destination_ip,destination_port,contact_ip,contact_port,originator_ip,originator_port,proto,family,rtp_stat,type,node,correlation_id,msg
) values ('2015-03-06
10:50:22',1425667824109829,'180','Ringing','','','+12052222222','gK007b315d','+12051111111','3Sr0m4vyjy2UK','','+12051111111','','2080378443_116641441@1.1.1.1','','SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7','z9hG4bK00B5617ed64f1ebf7d7','1888238783
INVITE','','','','','3.3.3.3',5060,'1.1.1.1',5060,'2.2.2.2',6038,'',0,1,2,'',2,'node1:2001','SIP/2.0
180 Ringing\r\nVia: SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route:
<sip:3.3.3.3;lr;ftag=gK007b315d>\r\nFrom:
<sip:+12052222222@1.1.1.1>;tag=gK007b315d\r\nTo:
<sip:+12051111111@3.3.3.3>;tag=3Sr0m4vyjy2UK\r\nCall-ID:
2080378443_116641441(a)1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact:
<sip:+12051111111@2.2.2.2:6038;transport=udp>\r\nAccept: application/sdp\r\nAllow:
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE\r\nSupported:
path\r\nContent-Length: 0\r\n\r\n','SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route:
<sip:3.3.3.3;lr;ftag=gK007b315d>\r\nFrom:
<sip:+12052222222@1.1.1.1>;tag=gK007b315d\r\nTo:
<sip:+12051111111@3.3.3.3>;tag=3Sr0m4vyjy2UK\r\nCall-ID:
2080378443_116641441(a)1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact:
<sip:+12051111111@2.2.2.2:6038;transport=udp>\r\nAccept: application/sdp\r\nAllow:
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE\r\nSupported:
path\r\nContent-Length: 0\r\n\r\n')
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com
7:47 p.m.
Thanks Daniel and Alexandr,
I’m not sure if any of this is pertinent but this is a FreeBSD 10.1 system using clang. I
just did a rebuild from master to rule out any build skew and everything seems ok for a
short period of time (about 5 minutes) and then the value for correlation_id seems to have
the same value as the msg column in many queries.
Thanks,
Spencer
On Mar 10, 2015, at 6:08 AM, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:
Hello,
maybe the values are too big for the defined column size. You can try
altering the table and increase the size for correlation_id column.
I cc-ed Alexandr, who wrote the module and can eventually comment more
on the issue.
Cheers,
Daniel
On 06/03/15 20:09, Spencer Thomason wrote:
Hello,
I’m not sure if this is the correct forum for this question but here goes…
I’m facing an issue setting up a sipcapture server. I’m seeing several db errors in the
logs:
Mar 6 10:45:13 sipcapture /usr/local/sbin/kamailio[37872]: ERROR: db_mysql
[km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Data too long for column
'correlation_id' at row 1
I did a packet capture of the sql query and it appears that the value for the
correlation_id is omitted. Interestingly its not all packets but maybe 60%. Do I have
something misconfigured?
Thanks,
Spencer
A sanitized version of the query is below:
insert into sip_capture
(date,micro_ts,method,reply_reason,ruri,ruri_user,from_user,from_tag,to_user,to_tag,pid_user,contact_user,auth_user,callid,callid_aleg,via_1,via_1_branch,cseq,reason,content_type,auth,user_agent,source_ip,source_port,destination_ip,destination_port,contact_ip,contact_port,originator_ip,originator_port,proto,family,rtp_stat,type,node,correlation_id,msg
) values ('2015-03-06
10:50:22',1425667824109829,'180','Ringing','','','+12052222222','gK007b315d','+12051111111','3Sr0m4vyjy2UK','','+12051111111','','2080378443_116641441@1.1.1.1','','SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7','z9hG4bK00B5617ed64f1ebf7d7','1888238783
INVITE','','','','','3.3.3.3',5060,'1.1.1.1',5060,'2.2.2.2',6038,'',0,1,2,'',2,'node1:2001','SIP/2.0
180 Ringing\r\nVia: SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route:
<sip:3.3.3.3;lr;ftag=gK007b315d>\r\nFrom:
<sip:+12052222222@1.1.1.1>;tag=gK007b315d\r\nTo:
<sip:+12051111111@3.3.3.3>;tag=3Sr0m4vyjy2UK\r\nCall-ID:
2080378443_116641441(a)1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact:
<sip:+12051111111@2.2.2.2:6038;transport=udp>\r\nAccept: application/sdp\r\nAllow:
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE\r\nSupported:
path\r\nContent-Length: 0\r\n\r\n','SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP
1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route:
<sip:3.3.3.3;lr;ftag=gK007b315d>\r\nFrom:
<sip:+12052222222@1.1.1.1>;tag=gK007b315d\r\nTo:
<sip:+12051111111@3.3.3.3>;tag=3Sr0m4vyjy2UK\r\nCall-ID:
2080378443_116641441(a)1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact:
<sip:+12051111111@2.2.2.2:6038;transport=udp>\r\nAccept: application/sdp\r\nAllow:
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE\r\nSupported:
path\r\nContent-Length: 0\r\n\r\n')
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
3546
days inactive
3550
days old
2 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Spencer Thomason