vicidial.org

Hi

New Install
ViciBox_v9.x86_64-9.0.2.iso
VERSION: 2.14-753a
BUILD: 200518-0828
Single Server

I have created a manual dial campaign and loaded in leads, 24 hours calling time, dial statuses selected but on Real Time dialable leads 0 and leads in hopper 0 yet the agents are still able to dial.

How can this be fixed?

hopper debug

Code: Select all


vicibox9:~ # /usr/share/astguiclient/AST_VDhopper.pl --debugX

----- DEBUG -----


----- SUPER DEBUG -----

TIME DEBUG: -5.00|-5.00|0|   GMT: 20:51
SELECT list_id FROM vicidial_lists where ( (active='N') or ( (active='Y') and (expiration_date < "2020-05-27") ) );Inactive Lists:  3
Inactive and Expired List Leads Deleted:  0E0 |DELETE from vicidial_hopper where list_id IN('999','998','1000') ;|
CALLBACK HOLD: 0|SELECT count(*) FROM vicidial_callbacks where callback_time <= '2020-05-27 15:51:49' and status='ACTIVE' ;|
     hopper DNC count:   0
     |SELECT count(*) from vicidial_hopper where status='DNC';|
---------------Auto Trim Hopper Enabled For Matrix---------------------
Leads in Hopper for this Campaign = 0
Hopper Level for this Campaign = 1000

CAMPAIGNS TO PROCESSES HOPPER FOR:  1|0
Campaign Matrix set to no-hopper-dialing: Y
NO HOPPER COUNT: 0|SELECT count(*) FROM vicidial_hopper where campaign_id='Matrix' and status NOT IN('QUEUE','HOLD');|
DONE. Script execution time in seconds: 0
vicibox9:~ #


try this:

vim /etc/my.cnf
Look for sql_mode and change it to sql_mode=""

This is the output:

There is no sql_mode that i could find

Code: Select all

vicibox9:~ # vim /etc/my.cnf
#      are actually attached to the chipset instead. A single modern NVMe
#      drive can max out the connection between the CPU and the chipset,
#      let alone two NVMe drives. You also have induced latency from the
#      CPU to Chipset transport as well.
#
#  - If you feel the need to tune this config file, you need to tune for
#      a 50/50 read to write workload or if anything a higher write
#      workload. Googling MariaDB performance tuning that uses something
#      like WordPress or Drupal or PHPBB as the target audience is not
#      really comprable to a ViciDial workload. The correct search terms
#      would be 'write intensive' or 'balanced' workload.
#
#  - There are no magic tuning or settings that can fix inadequate
#      hardware. Run 'iostat -dkx 1' and see how utilized your non-NVMe
#      drives are. If it's above 90%, there is no fix for that. NVMe's
#      do not report utilization correctly in iostat so you'll need to
#      go by feel on those. Always used an SSD for /srv/mysql/data in a
#      RAID-1 whenever possible. Go cheap on the dialers/web, not the DB!!!
#



[client]
# password   = your_password
# port       = 3306
# socket     = /run/mysql/mysql.sock


# The MariaDB server
[mysqld]
#bind-address = 127.0.0.1 # Uncomment for local/socket access only, will brick network access
#port = 3306 # Do not uncomment unless you know what you are doing, can brick your database connectivity
#socket = /run/mysql/mysql.sock # Same note as above

# Stuff to tune for your hardware
max_connections=512 # If you have a dedicated database that meets the above HW reqs, change this to 2000
key_buffer_size = 4G # Increase to be approximately 60% of system RAM when you have more then 8GB in the system


# In general most of the below settings don't need tuning
log-error = /var/log/mysql/mysqld.log
long_query_time=3
slow_query_log = 1
slow_query_log_file = /var/log/mysql/mysqld-slow.log
log-slow-verbosity = query_plan,explain
secure_file_priv = /var/lib/mysql-files # Only allow LOAD DATA INFILE from this directory as a security feature
log_bin = /var/lib/mysql/mysql-bin
binlog_format = mixed
binlog_direct_non_transactional_updates=1 # By default, all slave replications are treated as transactions, even though MyISAM doesn't support it, so disable that behavior cause it makes slave replicationg REALLLLLLLLLY slow
relay_log = /var/lib/mysql/mysql-relay-bin
datadir = /srv/mysql/data
server-id = 1 # Master should be 1, and all slaves should have a unique ID number
slave-skip-errors = 1032,1690,1062 # ViciDial doesn't always do clean inserts, so prevent duplicate inserts from bombing the replication basically
slave_parallel_threads = 4 # Might need to increase this if slave replicating is slow, up to 40 or even 60 threads is not unheard of
slave-parallel-mode = optimistic
slave-parallel-max-queued = 2M
skip-external-locking
skip-name-resolve

there is more to that file....

Code: Select all

:/etc # cat my.cnf
#
# ViciBox v.9.0 MariaDB 10.2.X config for OpenSuSE Leap 15.1
#
# Recommended hardware for this config file :
#  - 8-Core CPU 2.0Ghz or up (Real cores!!! not threads)
#  - 16GB of RAM for 250 or less agents, 32GB or up for more agents
#  - At least 512GB of SSD configured in a RAID1 (Hardware or Linux MD)
#
#
#
# Tips, Tricks, and Cheats :
#  - ALL DISCRETIONARY BUDGET SHOULD GO TOWARDS FAST DATABASE DRIVES,
#      FOLLOWED BY RAM, FOLLOWED BY CPU. That's the order of importance
#      for your standard ViciDial database before custom stuff gets
#      thrown into the mix. More info below.
#
#  - 256GB SSD/NVMe can be used if mounted under /srv/mysql/data while
#      using regular SATA 7200-rpm (or up) enterprise drives for the OS.
#      Please be careful that you don't do this AFTER you have set-up
#      ViciDial otherwise you will need to move the database files or
#      create a back-up then re-import the whole database. Doing this
#      wrong will wipe out all your data. You've been warned!
#
#  - If given a choice, more GHz is better then more CPU within the same
#      generation of CPU. For example a CPU with 8-cores at 2.1GHz gives
#      you a performance metric of 16.8 (Cores x GHz). A 6-core CPU at
#      3.0GHz gives you a performance metric of 18. So for MariaDB the
#      6-Core CPU at 3.0GHz would be faster then the 8-core CPU at 2.1GHz.
#      Your average 300-agent call center is quite happy with an 8-core
#      CPU until the custom report developers and management gets in
#      there and starts data mining. Use a slave for that!!!
#
#  - There's not much of a reason to go above 128GB RAM as this config
#      and ViciDial in general doesn't really take advantage of it with
#      the generated workload. Sure it won't hurt, but it won't really
#      help either. Better of spending that additional money on SSDs or
#      NVMe where you can afford it.
#
#  - NVMe drives are best used in a Linux MD RAID-1 attached directly
#      to the CPU through either a PCIe 3.0 add-in card or a M.2 to
#      PCIe 3.0 adapter card. Best performance is obtained when not
#      using a 'PLX' or PCIe switch chip. An example of some NVMe to
#      PCIe adapter cards are the SuperMicro AOC-SLG3-2M2, the ASRock
#      Ultra Quad M.2, or using multiple StarTech PEX4M2E1 adapters.
#      The dual or quad M.2 cards require "PCIe Bifurcation" support
#      in the motherboards BIOS. Please check the motherboard block
#      diagram in the manual to identify which PCIe ports are directly
#      attached to the CPU. You can use Dual and Quad NVMe cards with a
#      PLX or PCIe switcher built in but they will bottleneck with a
#      modern NVMe. An example of these type of 'switching' adapters
#      would be the SuperMicro AOC-SHG3-4M2P or Synology M2D18. In
#      reality most call centers won't need the speed of NVMe until
#      around 300 agents or so, but it's nice to have on tap.
#
#  - Most onboard M.2 NVMe ports are not directly attached to the CPU, but
#      are actually attached to the chipset instead. A single modern NVMe
#      drive can max out the connection between the CPU and the chipset,
#      let alone two NVMe drives. You also have induced latency from the
#      CPU to Chipset transport as well.
#
#  - If you feel the need to tune this config file, you need to tune for
#      a 50/50 read to write workload or if anything a higher write
#      workload. Googling MariaDB performance tuning that uses something
#      like WordPress or Drupal or PHPBB as the target audience is not
#      really comprable to a ViciDial workload. The correct search terms
#      would be 'write intensive' or 'balanced' workload.
#
#  - There are no magic tuning or settings that can fix inadequate
#      hardware. Run 'iostat -dkx 1' and see how utilized your non-NVMe
#      drives are. If it's above 90%, there is no fix for that. NVMe's
#      do not report utilization correctly in iostat so you'll need to
#      go by feel on those. Always used an SSD for /srv/mysql/data in a
#      RAID-1 whenever possible. Go cheap on the dialers/web, not the DB!!!
#



[client]
# password   = your_password
# port       = 3306
# socket     = /run/mysql/mysql.sock


# The MariaDB server
[mysqld]
#bind-address = 127.0.0.1 # Uncomment for local/socket access only, will brick network access
#port = 3306 # Do not uncomment unless you know what you are doing, can brick your database connectivity
#socket = /run/mysql/mysql.sock # Same note as above

# Stuff to tune for your hardware
max_connections=512 # If you have a dedicated database that meets the above HW reqs, change this to 2000
key_buffer_size = 4G # Increase to be approximately 60% of system RAM when you have more then 8GB in the system


# In general most of the below settings don't need tuning
log-error = /var/log/mysql/mysqld.log
long_query_time=3
slow_query_log = 1
slow_query_log_file = /var/log/mysql/mysqld-slow.log
log-slow-verbosity = query_plan,explain
secure_file_priv = /var/lib/mysql-files # Only allow LOAD DATA INFILE from this directory as a security feature
log_bin = /var/lib/mysql/mysql-bin
binlog_format = mixed
binlog_direct_non_transactional_updates=1 # By default, all slave replications are treated as transactions, even though MyISAM doesn't support it, so disable that behavior cause it makes slave replicationg REALLLLLLLLLY slow
relay_log = /var/lib/mysql/mysql-relay-bin
datadir = /srv/mysql/data
server-id = 1 # Master should be 1, and all slaves should have a unique ID number
slave-skip-errors = 1032,1690,1062 # ViciDial doesn't always do clean inserts, so prevent duplicate inserts from bombing the replication basically
slave_parallel_threads = 4 # Might need to increase this if slave replicating is slow, up to 40 or even 60 threads is not unheard of
slave-parallel-mode = optimistic
slave-parallel-max-queued = 2M
skip-external-locking
skip-name-resolve
connect_timeout = 60
max_allowed_packet = 16M
table_open_cache = 4096
table_definition_cache = 16384
sort_buffer_size = 4M
net_buffer_length = 8K
read_buffer_size = 4M
read_rnd_buffer_size = 16M
myisam_sort_buffer_size = 128M
query_cache_size = 0 # Yes, this will bottleneck your system if you have more then a few thousand QPS, so leave disabled! You've been warned :)
expire_logs_days = 3 # Disabling or setting this to 0 will fill up your hard-drive eventually, 3 days is a good compromise for slaves with connectivity issues
concurrent_insert = 2
myisam_repair_threads = 4
myisam_recover_option = DEFAULT
tmpdir = /tmp/
thread_cache_size = 100
join_buffer_size = 1M
myisam_use_mmap = 1
open_files_limit = 24576
max_heap_table_size=512M
tmp_table_size=32M
key_cache_segments=64
sql_mode=""


### By default only replicate the 'asterisk' database for ViciDial, comment out to replicate everything
### Make sure you do a full database dump if not just replicating asterisk database
#replicate_do_db=asterisk

### Comment out the tables below here if you really need them replicated to the slave, these are PERFORMANCE HOGS!
### Most of these tables are MEMORY tables which aren't persistent or used solely as tables for tracking the progress
### of things temporarily before doing real things like log inserts or lead updates
#replicate-ignore-table=asterisk.vicidial_live_agents
#replicate-ignore-table=asterisk.live_sip_channels
#replicate-ignore-table=asterisk.live_channels
#replicate-ignore-table=asterisk.vicidial_auto_calls
#replicate-ignore-table=asterisk.server_updater
#replicate-ignore-table=asterisk.web_client_sessions
#replicate-ignore-table=asterisk.vicidial_hopper
#replicate-ignore-table=asterisk.vicidial_campaign_server_status
#replicate-ignore-table=asterisk.parked_channels
#replicate-ignore-table=asterisk.vicidial_manager
#replicate-ignore-table=asterisk.cid_channels_recent
#replicate-wild-ignore-table=asterisk.cid_channels_recent_%


### Yes, we need this for system tables, so no need to tune anything here for ViciDial settings, these are just for the mysql tables and internal stuff
innodb_buffer_pool_size = 128M
innodb_file_format = Barracuda # Deprecated in future releases as this is the only supported format, eventually
innodb_file_per_table = ON
innodb_flush_method=O_DIRECT
innodb_flush_log_at_trx_commit=2
innodb_log_buffer_size=8M


### Configure the MariaDB server to use SSL, for the experts among us, nothing in ViciDial uses this natively, and might brick your DB
#ssl-ca=/etc/mysql/ssl/ca-cert.pem
#ssl-cert=/etc/mysql/ssl/server-cert.pem
#ssl-key=/etc/mysql/ssl/server-key.pem




[mysqld_multi]
mysqld     = /usr/bin/mysqld_safe
mysqladmin = /usr/bin/mysqladmin
log        = /var/log/mysqld_multi.log

# If you want to use mysqld_multi uncomment 1 or more mysqld sections
# below or add your own ones.

# WARNING
# --------
# If you uncomment mysqld1 than make absolutely sure, that database mysql,
# configured above, is not started.  This may result in corrupted data!
#
# [mysqld1]
# port       = 3306
# datadir    = /var/lib/mysql
# pid-file   = /var/lib/mysql/mysqld.pid
# socket     = /var/lib/mysql/mysql.sock
# user       = mysql

# [mysqld2]
# port       = 3307
# datadir    = /var/lib/mysql-databases/mysqld2
# pid-file   = /var/lib/mysql-databases/mysqld2/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld2/mysql.sock
# user       = mysql

# [mysqld3]
# port       = 3308
# datadir    = /var/lib/mysql-databases/mysqld3
# pid-file   = /var/lib/mysql-databases/mysqld3/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld3/mysql.sock
# user       = mysql

# [mysqld6]
# port       = 3309
# datadir    = /var/lib/mysql-databases/mysqld6
# pid-file   = /var/lib/mysql-databases/mysqld6/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld6/mysql.sock
# user       = mysql

!includedir /etc/my.cnf.d


vicidial_campaign_stats entry missing. create a new table and a new entry will be created. then copy that entry with the campaign ID of the original campaign. You likely deleted the entries in that table when cleaning the system or modified a campaign ID directly in sql rather than copying/creating one in the interface.