vicidial.org

Greetings and Happy New year!

We are using:
ViciBox V.10.0.0 210901
VICIDial version: 2.14b0.5
Asterisk #: 13.38.2
SVN: 3793
On physical computer Dell precision T1650 Intel i5, 16G RAM, 1 TB HDD

For some reason our vicidial_log table stopped populating anything, now I have checked vicidial_list table ( from what I found vicidial_log fetches information from this table) to see if it has any recent records and it does have. plus campaigns are not working anymore. I don't even know where to start troubleshooting?

FYI I have already changed values for uniqueID to varchar(30) and recently updated our SVN version.

Any help would be much appreciated!

You need to check if database tables are crashed or not.
Please check mysql log. it will give more information if database issue is there.

Thanks for your reply… we did ran quick repair on Database yesterday without any luck. Let me see if I can figure ou something with mysqllog

matt,

any ideas what could cause this? I had a look at the system but everything looks right. It seems they restored a backup and since that date the vicidial_log isnt being filled nor vicidial_list. I couldnt figure it out

maybe the auto increment value

alo wrote:maybe the auto increment value

Where can I find that setting and what needs to be in there?

You can check in mysql regarding that table's description, and you will get the autoincrement type of fields there.

alo wrote:maybe the auto increment value

kashyapking wrote:You can check in mysql regarding that table's description, and you will get the autoincrement type of fields there.

Ran mysql query to find if there is any Auto Increment value for the table by running "select AUTO_INCREMENT FROM information_schema.`TABLES` where TABLE_SCHEMA = " asterisk" AND TABLE_NAME = " vicidial_log"" command and the result I got is:
AUTO_INCREMENT
-------------------------
(N/A)

Does that table normally have Auto Increment for UNIQUEID or any other field_type?

Weird enough it automatically fixed it.. I am guessing we had bunch of BAD UNIQUE_ID values and as soon as it ran out of those values list started populating.