|Summary:||ASTERISK-16940: Error when storing queue_log data in RT - "column 'time' cannot be type 'int(10) unsigned'"|
|Reporter:||Tom Rymes (trymes)||Labels:|
|Date Opened:||2010-11-10 10:33:06.000-0600||Date Closed:||2011-06-07 14:05:01|
|Description:||I have followed the instructions available here: https://issues.asterisk.org/view.php?id=11625 to setup my queue_log to write to the realtime database on an elastix 2.0/Centos 5 system. |
Upon reloading asterisk, I receive this error:
WARNING res_config_mysql.c: Realtime table general@queue_log: column 'time' cannot be type 'int(10) unsigned' (need char)
I have not found anything in the bug tracker or elsewhere to indicate that the structure of the table has changed and that the original instructions linked above are now invalid. Having said that, I did find this: https://issues.asterisk.org/view.php?id=17082 , which indicates that modifications have been made to realtime queue_log behavior for Asterisk 1.8, though I have not found any reason to believe that those changes should be affecting the table structure for my 18.104.22.168 version of Asterisk.
****** ADDITIONAL INFORMATION ******
I set "Product Version" to "22.214.171.124", as I presume that is the correct version of app_queue for Asterisk v126.96.36.199.
|Comments:||By: Tilghman Lesher (tilghman) 2010-11-10 12:22:16.000-0600|
The documented format is actually in contrib/realtime/mysql/queue_log.sql. The issue report is not considered documentation, as the format can and will change during the process where features are added.
By: Tom Rymes (trymes) 2010-11-10 15:06:47.000-0600
My apologies. I do understand that the issue report is not documentation, but information about this is thin on the ground, other than sites that reference the issue report. More specifically, I have downloaded the 188.8.131.52 source tarball and I cannot find the queue_log.sql file you mention.
[root@vox mysql]# pwd
[root@vox mysql]# ls
iaxfriends.sql meetme.sql musiconhold.sql sipfriends.sql voicemail.sql
By: Leif Madsen (lmadsen) 2010-11-18 15:30:24.000-0600
Have you tried the format of time or date? (or whatever is valid)
By: Leif Madsen (lmadsen) 2010-11-18 15:31:12.000-0600
I'm closing this as a support issue. It would be appreciated if documentation were submitted so this can be avoided in the future, but the appropriate place for this is the asterisk-users mailing list or #asterisk on the Freenode IRC network.