[OpenSER-Devel] [ openser-Bugs-1783705 ] SIPTRACE: date column contains invalid data

SourceForge.net noreply at sourceforge.net
Wed Aug 29 14:24:40 CEST 2007


Bugs item #1783705, was opened at 2007-08-29 03:22
Message generated for change (Comment added) made by miconda
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1783705&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver devel
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Daniel-Constantin Mierla (miconda)
Summary: SIPTRACE: date column contains invalid data

Initial Comment:
This is an intermittent problem.

The resulting date column contains "0000-00-00 00:00:00" when the invalid data is attempted to be inserted.

Turning on the MySQL logging facility (/etc/mysql/my.cnf)
produced the following:

29 Query insert into sip_trace (...,date,...) values (...,'1493958-10-30 11:27:37',...)

The problem appears to be isolated to records with an 'in' direction.

Below is an 'out' direction record.

28 Query insert into sip_trace (...,date,...) values
 (...,'2007-08-28 20:08:25',...)

----------------------------------------------------------------------

>Comment By: Daniel-Constantin Mierla (miconda)
Date: 2007-08-29 15:24

Message:
Logged In: YES 
user_id=1246013
Originator: NO

Please paste the backtrace as well.

----------------------------------------------------------------------

Comment By: Norm Brandinger (norm_brandinger)
Date: 2007-08-29 15:12

Message:
Logged In: YES 
user_id=1786021
Originator: NO

Changing to debug=9 causes a core from siptrace very quickly (not the
first call to siptrace).

openser[18109]: sl:run_sl_callbacks: callback id 0 entered 
openser[18109]: parse_headers: flags=40 
openser[18109]: siptrace:trace_sl_onreply_out: dest
[udp:209.102.227.253:5060] 
openser[18109]: trace_sl_onreply_out: storing info... 
openser[18106]: core:handle_sigs: child process 18112 exited by a signal
11 
openser[18106]: core:handle_sigs: core was generated 
openser[18106]: core:handle_sigs: child process 18113 exited by a signal
11 
openser[18106]: core:handle_sigs: core was generated 
openser[18106]: core:handle_sigs: terminating due to SIGCHLD 
openser[18115]: core:sig_usr: signal 15 received 
openser[18128]: core:sig_usr: signal 15 received 
openser[18126]: core:sig_usr: signal 15 received

----------------------------------------------------------------------

Comment By: Norm Brandinger (norm_brandinger)
Date: 2007-08-29 14:58

Message:
Logged In: YES 
user_id=1786021
Originator: NO

Testing this morning shows the failure happening for both 'in' and 'out'
trace entries.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1783705&group_id=139143



More information about the Devel mailing list