QueueMetrics > Running QueueMetrics

QM not showing status on box 2, when HD on asterisk box one became full

(1/1)

cuban_cigar:
A setup had been working for about a year with asterisk on box 1, and queuemetrics on box 2.


The asterisk box (1) suffered a full harddrive and now queuemetrics is effectively dead on server (2), not showing live readout.


why / how to fix ?

QueueMetrics:
What do you mean by "dead"? you see no results, or cannot access it?
Try and restart it anyway....

cuban_cigar:
Queuemetrics loads without errors generated on the web page portion.

Login is allowed,

Liscence info shows current info of a valid QM install.

No current status shows up, that is all agents and queues are shown, but it says calls:0.


Box2

tomcat restart procedure ( several steps )
service queuemetrics restart
service httpd  restart
service mysqld  restart

then finally a reboot


Box1

tomcat restart procedure ( several steps )
service queuemetrics restart
service httpd  restart
service asterisk restart  (and manual restart of asterisk with cli )
service qloaderd restart
service mysqld  restart

The technician who set it up was on it yesterday and presumable this morning, but the client emailed again asking about it.

Could the qloader have started with a blank partition somehow when the HD got full and mysql database was repaired?

How to check if qloader is drawing the data correctly from the messages log?  Not certain but it could be that qloader is not sending data to box 2.

QueueMetrics:
It could well be that if MySQL crashed as well,  the table is not writable until repaired. So basically Qloaderd would stall because it keeps getting errors back from the DB. Anyway, do check /var/log/asterisk/qloaderd.log - if that is the issue it should be written in the logs.

Navigation

[0] Message Index