vicidial.org

Anyone ever experience this error? I saw one post about it with no resolution. Basically it is happening across all dialers. I came across it trying to figure out the LRERR issue. However I am starting to wonder if it is a database issue that is somehow causing the system to report LRERR. The other possibility is a bug that causes LRERR to double post.

2016-03-18 07:04:23|agi-VDAD_ALL_outbound.agi|01103||1062|Duplicate entry '1458309845.313' for key 'PRIMARY'|INSERT INTO vicidial_log (uniqueid,lead_id,campaign_id,call_date,start_epoch,status,phone_code,phone_number,user,processed,alt_dial,list_id,called_count) values('1458309845.313','56400345','OUTBNDDL','2016-03-18 07:04:23','1458309863','LRERR','1','8885556585','VDAD','N','NONE','4212','5')|V3180703460056400345|56400345|
2016-03-18 07:04:23|agi-VDAD_ALL_outbound.agi|01104||1062|Duplicate entry '1458309845.313' for key 'PRIMARY'|INSERT INTO vicidial_log_extended set uniqueid='1458309845.313',server_ip='192.168.0.10',call_date='2016-03-18 07:04:23',lead_id = '56400345',caller_code='V3180703460056400345',custom_call_id='';|V3180703460056400345|56400345|

You can safely ignore it. If I recall, It stems from the fact that the Unique ID is not actually unique ... it's just unique "per server" and there are multiple servers in play. However, it occurs in log tables that do not require logging in most cases as they are only used for troubleshooting purposes. So occasional skipped records from timing collisions are not worth resolving (thus the lack of resolution to date).

Awesome. Thank you. With that being said, any ideas on how to find out more detail about the LRERR? Nothing is jumping out unfortunately.

There are also multiple processes that will try to insert that record depending on what kind of call and what even is happening. It's much less likely that there is an actual duplicate than it's just another process has already inserted it for that call.

As for LRERR, that's almost always related to a call that is hung up before any audio is passed on the call. There can be multiple causes for that.

I stand corrected. Bad memory. And no audio (resulting in LRERR) is usually a firewall issue. Especially if it happens more than once in a blue moon. If you have a multi-server vicidial cluster OR a multi-location agent scenario, then you will likely have some fun chasing down the firewall issue but it can still be done.