- When I go to “Reports” tab is shows the below. Why? How do I fix?
SELECT substring(calldate,1,10) AS day, sum(duration) AS calltime, count(*) as nbcall FROM cdr WHERE UNIX_TIMESTAMP(calldate) >= UNIX_TIMESTAMP(‘2009-12-01’) GROUP BY substring(calldate,1,10) [nativecode=1146 ** Table ‘asteriskcdrdb.cdr’ doesn’t exist]
-
When I go to “Recording” tab, log-in and then click on the the “call monitor” link it says, DB Error: no such table
Why is this is the case? hod do I fix? -
Why would, “Flash Operator Panel” show a BOLD ‘s’ one extension. What does this mean?
So here is my story what happened. All the above started to occur by itself. It started with the entire UI not working.
FreePBX System Status
FreePBX Notices
*
Error There are 1 bad destinations
Ignore this
DEST STATUS: EMPTY
Ringroup: Michael Wayne Fail Over (601)
Added 1 week, 2 days, 23 hours, 46 minutes ago
(retrieve_conf.BADDEST)
show all
FATAL ERROR
SELECT extension,name,voicemail FROM users ORDER BY extension [nativecode=1146 ** Table ‘asterisk.users’ doesn’t exist]SQL - SELECT extension,name,voicemail FROM users ORDER BY extension
After awhile now we get this
FATAL ERROR
DELETE FROM notifications WHERE module = ‘core’ AND id = ‘AMPDBPASS’ [nativecode=1146 ** Table ‘asterisk.notifications’ doesn’t exist]SQL - DELETE FROM notifications WHERE module = ‘core’ AND id = ‘AMPDBPASS’
So we logged into the backend to check the databases, and it seems that our asterisk databases are gone. I don’t know if it’s coincidental to what appears to be an openfire jabber server installation or not. Openfire Jabber was installed for many weeks and never caused a problem. It appears that the DB files still exist, but are in what appears to be a temporary format, like something was working on them in the backend and the system was rebooted during the process.
So we found at the end of each file was symbol ~.
The next we removed it.
cd /var/lib/mysql/asterisk
list=ls
for i in $list; do echo $i; newi=${i/~/}; echo $newi; mv $i $newi; echo; done
… but we still have the problems above. Also not sure how we can avoid this or what caused this issue.