Page 1 of 1

Paused agents not showing in realtime screen

PostPosted: Fri Jul 06, 2007 11:20 pm
by ekaftan
I had a server crash today (electrical problem). After the crash paused agents dont get shown on the realtime screen. Everything else seems to work ok.

I reindexed mysql tabled and emptied vicidial_live_calls and rebooted and still nothing.

Any ideas?

This is an agents record while paused (and not showing on the realtime screen)

live_agent_id user server_ip conf_exten extension status lead_id campaign_id uniqueid callerid channel random_id last_call_time last_update_time last_call_finish closer_campaigns call_server_ip user_level comments
2 4198 200.9.185.45 8600051 Local/4198@default PAUSED 0 WCFCPRE1 0.0000000 16751324 2007-07-06 23:33:11 2007-07-07 00:07:55 2007-07-06 23:33:11 NULL 1

PostPosted: Mon Jul 09, 2007 11:18 pm
by mflorell
Did you run the AST_reset_mysql_vars.pl script after your crash?

This will clear out the session records in the database.

Also, do you have more than one server? are they ntp time synced?

PostPosted: Tue Jul 10, 2007 7:44 pm
by ekaftan
mflorell wrote:Did you run the AST_reset_mysql_vars.pl script after your crash?

This will clear out the session records in the database.

Also, do you have more than one server? are they ntp time synced?


No I did not run it... should I put it on rc.local?

Its a single server. The same one I had the problem with the calls not transferring, that fixed itself upgrading to 2.0.3

I have it running. Paused agents still dont appear on the realtime interface. All the rest works...

I will run the reset script. thanks.

PostPosted: Wed Jul 11, 2007 7:08 pm
by aster1
If you have a power problem .. i will highly recommend to run AST_reset_mysql_vars.pl in rc.local ( it doesnt harm even if no power problem ) along with some script to repair all tables in vicidial database on every start ( check http://www.adspeed.org/2007/01/mysql-sh ... e-all.html )

run this script with --optimize as well as --repair in rc.local and also the AST_reset_mysql_vars.PL

If you have this in startup .. most of random problems that arise are solved on restart but mysql cant repair tables completely everytime so you might have to fix few manually