[asterisk-dev] Channel Event Logging and newcdr svn branch

[Matthew Nicholson]

On Thu, 2009-06-04 at 18:30 +0400, Alexander Krylowsky wrote:

> 1. with CEL logging enabled ("enable=yes" in cel.conf general section)
> a lot of astobj2.c warnings on every cel event appears on console:
> 
> ERROR[9355]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3b5 for 0xb78f3a70
> ERROR[9355]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3b5 for 0xb78f3a70
> ERROR[9355]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3b5 for 0xb78f3a70
> ERROR[9355]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3b5 for 0xb78f3a70
> .........
> 
> Looks like it doesn't affect normal asterisk operation. This bug is similar to #14974.

I was not able to reproduce this.  Please give me some more information
about your setup.

> 2. Unescaped data (eventtime) in cel_pgsql query: on every cel event on console appears:
> 
> [Jun  4 18:23:59] ERROR[9781]: cel_pgsql.c:338 pgsql_log: Connection may have been lost... attempting to reconnect.
> [Jun  4 18:23:59] ERROR[9781]: cel_pgsql.c:341 pgsql_log: Connection reestablished.
> [Jun  4 18:23:59] ERROR[9781]: cel_pgsql.c:347 pgsql_log: HARD ERROR!  Attempted reconnection failed.  DROPPING CALL RECORD!
> [Jun  4 18:23:59] ERROR[9781]: cel_pgsql.c:348 pgsql_log: Reason: ERROR: syntax error near "18"
> LINE 1: ...rfield","peer") VALUES ('CEL_CHAN_END',2009-06-04 18:23:59,'...

This should be fixed in r199218
-- 
Matthew Nicholson
Digium, Inc. | Software Developer