Issues After Upgrading Vicidial
Posted:
Sun Apr 01, 2018 9:48 pm
by elyc1990
I performed an upgrade to my database, webserver, and asterisk to the latest svn on Friday as per instruction here
http://www.vicidial.org/VICIDIALforum/v ... hp?t=16326. We ran upgrade_2.14.sql
My current version:
VERSION: 2.14-665a
BUILD: 180316-0751
Version under System Settings:
Version: 2.14b0.5
SVN Version: 2953
DB Schema Version: 1540
DB Schema Update Date: 2018-03-30 20:23:00
Before upgrade, everything works normally. However after upgrade here are some issues that I'm facing:
1. "Export Calls Report" - wrong data in wrong column e.g. call date shown as 23151-60, status show "No answer autodial" instead of NA, user - recording link, campaign id - date of call, etc. Some data eg phone number dialed, phone code, phone number are missing. The lead information shows normally under vicidial admin web portal lead entry.
2. Under the "CALLED COUNTS WITHIN THIS LIST:" of the individual list summary, it does not show call count for all status, instead it shows one row wi something like this:
CALLED COUNTS WITHIN THIS LIST:
STATUS STATUS NAME 0 1 2 3 4 5 6 SUBTOTAL
1 904
TOTAL 1981 7408 670 114 22 7 2 10204
3. All the old and new call backs in agent screen show 727551212 in the phone number with full name as "Matt lead05" and status as either "L" or "A".
Can anyone please enlighten me what could have gone wrong?
Re: Issues After Upgrading Vicidial
Posted:
Sun Apr 01, 2018 9:56 pm
by williamconley
Verify that all servers now have the same SVN revision level.
Verify that all servers successfully completed the perl install.pl script all the way to the end with no errors.
Verify that the sql script ran all the way to the end without you overriding it in any way (no errors). The last line of the sql file contains an update to the db_schema record. Verify that this update line matches the value in admin->system settings.
Re: Issues After Upgrading Vicidial
Posted:
Sun Apr 01, 2018 11:29 pm
by elyc1990
Thanks William for your reply,
All servers have the same SVN revision level and all the install.pl scripts were completed with no errors.
I suspect it's the database issue, will run the sql upgrade script again. If it's database schema upgrade issue, is there any way to repair it?
Re: Issues After Upgrading Vicidial
Posted:
Mon Apr 02, 2018 12:26 am
by elyc1990
Hi
I just ran \. /usr/src/astguiclient/trunk/extras/upgrade_2.14.sql again, here are some errors. Are the issues due to the database upgrade error? How can I solve it?
mysql> \. /usr/src/astguiclient/trunk/extras/upgrade_2.14.sql
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 1 row affected (0.00 sec)
Records: 1 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'parked_channels_recent' already exists
ERROR 1060 (42S21): Duplicate column name 'internal_chat_type'
ERROR 1060 (42S21): Duplicate column name 'internal_chat_type'
ERROR 1060 (42S21): Duplicate column name 'message_id'
ERROR 1060 (42S21): Duplicate column name 'message_id'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'agent_chat_screen_colors'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'conf_qualify'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'populate_lead_province'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'api_only_user'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_api_urls' already exists
ERROR 1050 (42S01): Table 'vicidial_api_urls_archive' already exists
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'dead_to_dispo'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'external_lead_id'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'areacode_filter'
ERROR 1060 (42S21): Duplicate column name 'areacode_filter_seconds'
ERROR 1060 (42S21): Duplicate column name 'areacode_filter_action'
ERROR 1060 (42S21): Duplicate column name 'areacode_filter_action_value'
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_areacode_filters' already exists
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'enable_auto_reports'
ERROR 1060 (42S21): Duplicate column name 'modify_auto_reports'
ERROR 1050 (42S01): Table 'vicidial_automated_reports' already exists
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'agent_xfer_validation'
ERROR 1060 (42S21): Duplicate column name 'populate_state_areacode'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'conf_qualify'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'enable_pause_code_limits'
ERROR 1060 (42S21): Duplicate column name 'time_limit'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'enable_drop_lists'
ERROR 1050 (42S01): Table 'vicidial_drop_lists' already exists
ERROR 1050 (42S01): Table 'vicidial_drop_log' already exists
ERROR 1050 (42S01): Table 'vicidial_drop_log_archive' already exists
ERROR 1091 (42000): Can't DROP 'drop_date'; check that column/key exists
ERROR 1061 (42000): Duplicate key name 'vicidial_drop_log_archive_key'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'allow_ip_lists'
ERROR 1060 (42S21): Duplicate column name 'system_ip_blacklist'
ERROR 1060 (42S21): Duplicate column name 'modify_ip_lists'
ERROR 1060 (42S21): Duplicate column name 'ignore_ip_list'
ERROR 1060 (42S21): Duplicate column name 'admin_ip_list'
ERROR 1060 (42S21): Duplicate column name 'agent_ip_list'
ERROR 1060 (42S21): Duplicate column name 'api_ip_list'
ERROR 1050 (42S01): Table 'vicidial_ip_lists' already exists
ERROR 1050 (42S01): Table 'vicidial_ip_list_entries' already exists
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'dl_minutes'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'ready_max_logout'
ERROR 1060 (42S21): Duplicate column name 'ready_max_logout'
ERROR 1060 (42S21): Duplicate column name 'routing_prefix'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'cid_channels_recent' already exists
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'callback_display_days'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'three_way_record_stop'
ERROR 1060 (42S21): Duplicate column name 'hangup_xfer_record_start'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_rt_monitor_log' already exists
ERROR 1050 (42S01): Table 'vicidial_rt_monitor_log_archive' already exists
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'agent_push_events'
ERROR 1060 (42S21): Duplicate column name 'agent_push_url'
Query OK, 0 rows affected (0.01 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'hide_inactive_lists'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'xfer_hungup'
ERROR 1060 (42S21): Duplicate column name 'xfer_hungup_datetime'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_campaign_hour_counts' already exists
ERROR 1050 (42S01): Table 'vicidial_campaign_hour_counts_archive' already exists
ERROR 1050 (42S01): Table 'vicidial_carrier_hour_counts' already exists
ERROR 1050 (42S01): Table 'vicidial_carrier_hour_counts_archive' already exists
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'user_call_log_archive' already exists
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_inbound_survey_log' already exists
ERROR 1050 (42S01): Table 'vicidial_inbound_survey_log_archive' already exists
ERROR 1061 (42000): Duplicate key name 'visla_key'
ERROR 1060 (42S21): Duplicate column name 'inbound_survey'
ERROR 1060 (42S21): Duplicate column name 'inbound_survey_filename'
ERROR 1060 (42S21): Duplicate column name 'inbound_survey_accept_digit'
ERROR 1060 (42S21): Duplicate column name 'inbound_survey_question_filename'
ERROR 1060 (42S21): Duplicate column name 'inbound_survey_callmenu'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'allow_manage_active_lists'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'filename_override'
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1061 (42000): Duplicate key name 'vle_lead_id'
ERROR 1060 (42S21): Duplicate column name 'front_uniqueid'
ERROR 1060 (42S21): Duplicate column name 'close_uniqueid'
ERROR 1050 (42S01): Table 'vicidial_xfer_log_archive' already exists
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'expired_lists_inactive'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'did_system_filter'
ERROR 1050 (42S01): Table 'vicidial_dnccom_scrub_log' already exists
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'flag_projdnc'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'custom_variables'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'disk_reads'
ERROR 1060 (42S21): Duplicate column name 'disk_writes'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'inbound_list_script_override'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'webphone_layout'
ERROR 1060 (42S21): Duplicate column name 'webphone_layout'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'scheduled_callbacks_email_alert'
ERROR 1060 (42S21): Duplicate column name 'email_alert'
ERROR 1060 (42S21): Duplicate column name 'email_result'
ERROR 1060 (42S21): Duplicate column name 'email_alert'
ERROR 1060 (42S21): Duplicate column name 'email_result'
ERROR 1062 (23000): Duplicate entry 'AGENT_CALLBACK_EMAIL ' for key 'PRIMARY'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'field_duplicate'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'max_inbound_calls_outcome'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'manual_auto_next_options'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'agent_screen_time_display'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_ingroup_hour_counts' already exists
ERROR 1050 (42S01): Table 'vicidial_ingroup_hour_counts_archive' already exists
ERROR 1060 (42S21): Duplicate column name 'default_xfer_group'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'next_dial_my_callbacks'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'anyone_callback_inactive_lists'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_process_log' already exists
Query OK, 0 rows affected (0.00 sec)
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'inbound_no_agents_no_dial_container'
ERROR 1060 (42S21): Duplicate column name 'inbound_no_agents_no_dial_threshold'
Query OK, 1 row affected (0.01 sec)
Records: 1 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_inbound_callback_queue' already exists
ERROR 1050 (42S01): Table 'vicidial_inbound_callback_queue_archive' already exists
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'icbq_expiration_hours'
ERROR 1060 (42S21): Duplicate column name 'closing_time_action'
ERROR 1060 (42S21): Duplicate column name 'closing_time_now_trigger'
ERROR 1060 (42S21): Duplicate column name 'closing_time_filename'
ERROR 1060 (42S21): Duplicate column name 'closing_time_end_filename'
ERROR 1060 (42S21): Duplicate column name 'closing_time_lead_reset'
ERROR 1060 (42S21): Duplicate column name 'closing_time_option_exten'
ERROR 1060 (42S21): Duplicate column name 'closing_time_option_callmenu'
ERROR 1060 (42S21): Duplicate column name 'closing_time_option_voicemail'
ERROR 1060 (42S21): Duplicate column name 'closing_time_option_xfer_group'
ERROR 1060 (42S21): Duplicate column name 'closing_time_option_callback_list_id'
ERROR 1060 (42S21): Duplicate column name 'add_lead_timezone'
ERROR 1060 (42S21): Duplicate column name 'icbq_call_time_id'
ERROR 1060 (42S21): Duplicate column name 'icbq_dial_filter'
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'enable_gdpr_download_deletion'
ERROR 1060 (42S21): Duplicate column name 'export_gdpr_leads'
ERROR 1050 (42S01): Table 'recording_log_deletion_queue' already exists
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1050 (42S01): Table 'vicidial_cid_groups' already exists
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'cid_group_id'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'pause_max_dispo'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'script_top_dispo'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
ERROR 1060 (42S21): Duplicate column name 'source_id_display'
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0
Re: Issues After Upgrading Vicidial
Posted:
Mon Apr 02, 2018 12:49 am
by elyc1990
Issue solved, I rolled back my webserver to the one before I upgrade, install the upgrade and everything is back to normal. The only difference between this webserver and the one which gave issue is the different version of PHP. Current version of PHP is 5.3 while the one that had issue is 7.2 (coincidentally someone else upgraded the php version before the vicidial upgrade on Friday).
It didnt' occur to me that it is php issue because the automated report that I ran from asterisk server (Run Server) had some fields missing as well. After the web server was rolled back, the automated report become normal. It is weird that php version in webserver will affect automated report content that's generated from asterisk server...
Re: Issues After Upgrading Vicidial
Posted:
Mon Apr 02, 2018 4:53 am
by mflorell
Would you have happened to have grabbed the error_log output from apache before you rolled the webserver back?
We have tested VICIdial with PHP 7 before, and have a couple of clients running it in production and not seen any issues, so I'm curious to see what the errors look like in your case.
Re: Issues After Upgrading Vicidial
Posted:
Mon Apr 02, 2018 8:25 am
by elyc1990
Hi Matt, sure thing, I have sent you the error log via email through the forum.
Re: Issues After Upgrading Vicidial
Posted:
Mon Apr 02, 2018 9:18 am
by mflorell
I don't seem to have received anything. Please try sending it directly to
support@vicidial.com