Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
Not what I was talking about. It's also possible to block viewing specific campaigns and user groups from some managers. Which means you may only be able to run reports for specific groups of people and that may not include those whose calls you're attempting to see. Just being able to run the report doesn't mean the data in the report is available to you.all reports viewable
I have no idea what that meant.Only few report have it
Your Vicidial Version may be a bit old. but if you have it: There will be a checkbox in some (most? all?) reports for "Search archived data". This changes the data source from whatever log file(s) that report uses to "XXX_archive". So if it was pulling from "vicidial_log" it will now pull from "vicidial_log_archive" instead, accessing the archived data. If you check your mysql tables for record counts (phpMyAdmin makes this very easy, you can sort by record-count), you'll see if the archive tables are populated and if the associated NON-archive tables are tiny by comparison.wehre do I find this archive box
Leckbush wrote:1. But Im the highest user here. Im the top admin, the user admin is at level 9.
Leckbush wrote:All permission is allowed even in user group. There is just no report output. Im the one who managed the dialer unless there is a system user that is set to prevent me to see report even an admin user?
Leckbush wrote:2. I check the sql via workbench. I try to pull out the the table for "vicidial_agent_log_archive % vicidial_agent_log" But returned no data, just NULL. So I guess its not writing any data on the table
Leckbush wrote:3. I already did try pulling report with search archive data, But doesnt work.
Leckbush wrote: When I open Workbench I have this query report automatically appear when I login to it [Error Code: 144 Table './asterisk/vicidial_carrier_log' is marked as crashed and last (automatic?) repair failed] Do you think thats problem?
mysqlcheck --auto-repair -p asterisk vicidial_carrier_log
Leckbush wrote:Wow thank you william. I hope repairing this solve the issue on report including some metric that doesnt work on realtime report of some campaign. I'll give you an update of whats the result is.
Can I run the repair command while under calls operations?
mysql asterisk -p -e "show table status where comment like '%crashed%'"
mysqlcheck --all-databases --auto-repair -p
Users browsing this forum: Bing [Bot], Google [Bot] and 66 guests