Page 1 of 1

Real time report -Agent stat not updated

PostPosted: Mon Mar 25, 2013 6:28 am
by lvish
Hi

We are observing a peculiar problem in real time display, agent status is not being updated when screen refreshes.
ie. if an agent has moved from pause mode to call waiting mode real time display still shows in pause mode even after multiple refreshes. After couple of minutes it works fine . This is happening randomly for all agents.

Server load is not greater than 15%.

Any inputs is highly appreciated.

thanks in advance.

lvish
--------------------------------------------------------------------------------------------
DB ,Web ,Asterisks-- Dell R720 -Hexa core 32GB, -- 60 Agents --64Bit version
Asterisks ,Web -- ML110 , 1 X Quad core 8GB RAM -- 25 Agents --- 4 PRis 32 bit
Asterisks ,Web -- ML110 , 1 X Quad core 8GB RAM -- 25 Agents -- 2 Pri's 32bit

VERSION: 2.6-375a
BUILD: 120831-1523

Dahdi 2.6 -PRI trunks X 6 no.s
Vicibox 4.0.1,
Balance dialing -- Yes in all servers.
--------------------------------------------------------------------------------------------

Re: Real time report -Agent stat not updated

PostPosted: Tue Mar 26, 2013 8:53 am
by williamconley
during the next occurrence, enter "uptime" on each server and get the real server load. this will be in the form of how many processors are busy. so if you have a 4 processor system, it could be anywhere from 0.1 to 4.0. in a vicidial server, 50% or below is good. so 2.0 or below for a 4 processor server or 4.0 for an 8 processor server.

Re: Real time report -Agent stat not updated

PostPosted: Mon Apr 01, 2013 1:59 am
by lvish
thanks Williamconley for reply,

I have not seen CPU usage going above 20% , ofcourse uptime of the server is greater than 60 days.

I will execute the commands provided by you and revert .

thank you once again.


regds

Re: Real time report -Agent stat not updated

PostPosted: Mon Apr 01, 2013 6:00 pm
by williamconley
cpu usage of 20% or below would imply "0.4" on a 2 processor system, is that what you meant? Or did you see "20.0"? LOL Or are you still using something other than "uptime" to get the cpu usage?

what do you have the end of shift set to for the campaign?

have you created a new campaign to see if the problem persists?

have you checked for crashed tables?

Re: Real time report -Agent stat not updated

PostPosted: Wed Apr 03, 2013 7:19 am
by lvish
hi
uptime output 24 proc system
13:36pm up 69 days 21:31, 2 users, load average: 0.33, 0.66, 0.58.

We use top command to monitor cpu usage.

end of shift -- Latest server time --23;59
Local call time -- 24Hrs

We have test campaign created since the date of installation. Not faced any problem in that campaign. Problem looks like not specific to a campaign. Appears randomly .

Will check for crashed tables and revert.

thanks

Re: Real time report -Agent stat not updated

PostPosted: Wed Apr 03, 2013 7:19 pm
by williamconley
is there actually a semi-colon in the latest server time?

Re: Real time report -Agent stat not updated

PostPosted: Wed Apr 03, 2013 9:30 pm
by lvish
sorry its a typo, its just 23:59.

Re: Real time report -Agent stat not updated

PostPosted: Wed Apr 03, 2013 9:52 pm
by williamconley
up 69 days? try rebooting nightly, see if that helps. also: was the load average taken at the time of a "problem" or at a random moment not during a problem time?

Re: Real time report -Agent stat not updated

PostPosted: Sun Apr 07, 2013 9:34 pm
by lvish
thanks , Have rebooted now.will observe and revert post todays production.
CPU utilization is taken during peak traffic hours. But that time problem was not reported.

Re: Real time report -Agent stat not updated

PostPosted: Mon Apr 08, 2013 2:28 pm
by williamconley
you may want to get the load average during the time of failure, this is often educational ... no matter what the problem is, have a look at your load average. if the load average is something you are familiar with during all scenarios, you'll be the first to recognize a problem when it changes.

Re: Real time report -Agent stat not updated

PostPosted: Wed Apr 17, 2013 10:23 pm
by lvish
hi

looks like it got fixed after restart. till now no one has complained. Thanks for the support