Vicidial 6.0 crashing database

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Vicidial 6.0 crashing database

Postby vijaydxb » Mon Sep 29, 2014 2:45 pm

We have recently upgraded the Vicidial 5.0.3 server to version 6.0.2 . after the upgrade all the big reports (including one month Inbound DID report) are not working. after reaching 85 agents system crashing (it happened thrice) . Please find the details below

VERSION: 2.10-448a
BUILD: 140706-0927
VER 2153

DB server
PowerEdge R715 32GB,
2x AMD Opteron 6320 (2.8GHz, 8C, 8M L2/16M L3 Cache, Turbo CORE, 115W TDP), DDR3-1600MHz
4 X 300GB, SAS 6Gbps, 2.5-in, 15K RPM Hard Drive (Hot-plug) - RAID 10
1 PERC H700 Integrated RAID Controller, 1GB NV Cache

2 Web server , 4 Telephony server


my.cnf
Code: Select all
port            = 3306
socket          = /var/run/mysql/mysql.sock
datadir = /var/lib/mysql
skip-external-locking
key_buffer_size = 1024M
max_allowed_packet = 2M
table_open_cache = 8192
sort_buffer_size = 4M
net_buffer_length = 8K
read_buffer_size = 4M
read_rnd_buffer_size = 16M
myisam_sort_buffer_size = 128M
#thread_cache_size = 50
query_cache_size = 0
query_cache_size = 256
thread_concurrency=32
skip-name-resolve
connect_timeout=60
long_query_time=3
slow-query-log
#log_slow_queries
max_connections=512
open_files_limit=24576
max_heap_table_size=64M
expire_logs_days=3
default-storage-engine=MyISAM
table_definition_cache=8192
table_cache=8192
myisam_recover
myisam_repair_threads=1
tmpdir          = /tmp/


From mysqld.log
Code: Select all
140929 15:08:08 [Warning] Checking table:   './asterisk/vicidial_xfer_log'
140929 15:08:28 [ERROR] mysqld: Table './asterisk/vicidial_api_log' is marked as crashed and should be repaired
140929 15:08:28 [Warning] Checking table:   './asterisk/vicidial_api_log'
140929 15:08:55 [ERROR] mysqld: Table './asterisk/user_call_log' is marked as crashed and should be repaired
140929 15:08:55 [Warning] Checking table:   './asterisk/user_call_log'
140929 15:16:47 [ERROR] mysqld: Table './asterisk/vicidial_admin_log' is marked as crashed and should be repaired
140929 15:16:47 [Warning] Checking table:   './asterisk/vicidial_admin_log'
140929 15:36:16 [ERROR] mysqld: Table './asterisk/vicidial_xfer_stats' is marked as crashed and should be repaired
140929 15:36:16 [Warning] Checking table:   './asterisk/vicidial_xfer_stats'
140929 16:06:56 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,

something is definitely wrong and this may fail.


Kindly help me to fix tis problem.
Regards..
Vijay.
vijaydxb
 
Posts: 15
Joined: Tue Aug 30, 2011 4:30 pm

Re: Vicidial 6.0 crashing database

Postby geoff3dmg » Tue Sep 30, 2014 3:05 am

Well you can run a repair on the mysql tables with the following command:

Code: Select all
mysqlcheck --auto-repair --check --optimize --all-databases


Do you know why your system crashed?
Vicibox 5.03 from .iso | VERSION: 2.10-451a BUILD: 140902-0816 | Asterisk 1.8.28.2-vici | Multi-Server | Amfeltec H/W Timing Cards | No Extra Software After Installation | Dell PowerEdge 1850 | Pentium 4 'Prescott' Xenon Quad @ 3.40GHz
geoff3dmg
 
Posts: 403
Joined: Tue Jan 29, 2013 4:35 am
Location: Lancashire, UK


Return to Support

Who is online

Users browsing this forum: Google [Bot] and 116 guests