Messages

1

Running QueueMetrics / Re: Queuemetrics is not accessible through web after system reboot

« on: May 11, 2007, 10:47:03 »

I'm not exactly sure what you mean by './queuemetrics restart'. Is that a special script, or are you referring to using the tomcat manager interface to restart the QueueMetrics application?

Is that the entire error message? If not, then posting it would help diagnose the problem a little bit better. I can give you some things to check in the meantime though to help diagnose the problem

With Tomcat running (and QueueMetrics installed), point your browser (ON the QueueMetrics/Tomcat server) to http://127.0.0.1:8080/queuemetrics/dbtest . This may point you
in the right direction as to where the errors are comming from.

Also, make sure you have the correct version of the Java / MySQL  connector installed. From the online QueueMetrics manual, it says to use mysql-connector-java-3.0.10-stable-bin.jar, that can be
downloaded from  http://www.mysql.com/products/connector-j/index.html.

A list of some troubleshooting error codes and their explanations can also be found at http://www.queuemetrics.com/faq.jsp.

Hope this helps. 

2

MySQL storage and Qloaderd/Uniloader / Re: Error type: dr

« on: May 03, 2007, 13:10:24 »

The problem is that MySQL is not recognizing the username/password combination you are using. In MySQL, there is a difference between a user at 'localhost' and a user at '192.168.51.22', for example. When you create a user in MySQL, MySQL recognizes the user by username AND location. You also have to give the user database/table/usage privileges.

You could create a user in MySQL that is only used for QueueMetrics, let's call it 'queuemetrics'.

You need to go into the MySQL client to create a user. Usually the command (from a console) is simply 'mysql'. However, there are command line options. Try one of these:

Code: [Select]

mysql -u root -p
OR
mysql -u root
If you have set a password for the 'root' user, use the first MySQL command. If not, then use the second MySQL command.

Ok, so now you should be at a 'mysql>' prompt.
You now need to create a user and give that user privileges over your 'queuemetrics' database in MySQL.

The following command will create a user in MySQL named 'queuemetrics' who is only given access from 'localhost', grant all privileges to that user (except for GRANT), only give them access to the 'queuemetrics' database (and all of its tables), using the password 'password'.

Code: [Select]

mysql> GRANT ALL PRIVILEGES ON queuemetrics.*  TO 'queuemetrics'@'localhost' IDENTIFIED BY 'password';
To see what grants you have given the user, type:

Code: [Select]

mysql> SHOW GRANTS FOR 'queuemetrics'@'localhost';
To exit MySQL, simply type:

Code: [Select]

mysql>\q
Then, you need to change the MySQL username and password in the Qloader script to reflect the username and password you created in MySQL.

That should do it for you 

PS - MySQL has extensive documentation about how to use their DBMS. For more information on the GRANT command, check out http://dev.mysql.com/doc/refman/5.0/en/grant.html

3

General Asterisk configuration / Re: Agent-View problem

« on: April 30, 2007, 18:28:54 »

I'm not familiar with the mod, but I can suggest checking something...

In your queue_log data file/sql table, does the 'agent' field (4th field of each queue_log record) contain the same agent identifier throughout the events in a call (AGENTCALLBACKLOGIN/AGENTLOGIN, CONNECT, PAUSE, UNPAUSE, COMPLETECALLER, COMPLETEAGENT, etc.)?

The reason why I'm asking is because I believe the same value that was used for the AGENTCALLBACKLOGIN/AGENTLOGIN, must be the same when queue_log events such as CONNECT, etc. occur in order for QueueMetrics to be able to know which agent a particular call was answered by.

Hope it helps

4

Running QueueMetrics / Re: Queuemetrics is not accessible through web after system reboot

« on: April 30, 2007, 14:17:28 »

Are you exporting the tomcat server variables correctly? The startup.sh script calls catalina.sh. If you look at catalina.sh (the top portion of the file), you'll notice the available variables you can set. The main variables you should set to get tomcat running are JAVA_HOME, JRE_HOME, and CATALINA_HOME. You can set these variables in a startup script that can be run when you startup your computer or when you start up tomcat.

To see your system variables are set correctly, try typing at a console prompt:

Code: [Select]

echo $JAVA_HOME
echo $JRE_HOME
echo $CATALINA_HOME
If nothing returns, then you aren't setting this variable correctly. If the incorrect path is displayed, then you need to find out where it's being set incorrectly and change it.

You can set these variables in a script or even at a console prompt:

Code: [Select]

JAVA_HOME=/usr/local/queuemetrics/jdk1.5.0_06
JRE_HOME=/usr/local/queuemetrics/jdk1.5.0_06
CATALINA_HOME=/usr/local/queuemetrics/tomcat
export JAVA_HOME JRE_HOME CATALINA_HOME
Try setting those variables and then restarting tomcat. Make sure the program 'java' is accessible in the 'bin/' subdirectory of your JAVA_HOME (or JRE_HOME variable). If JRE_HOME is not defined, it should default to JAVA_HOME.

On our system, we're only using jre1.5.0_06 (not jdk1.5.0_06), which works fine. Our JAVA_HOME and JRE_HOME variables are both set to '/usr/java/jre1.5.0_06'.

You can see if tomcat is running by typing from a console:

Code: [Select]

ps aux | grep tomcat
If it returns something like:

Code: [Select]

root      3863  7.1  8.7 4617372 355684 pts/2 Sl  07:27   2:48 /usr/java/jre1.5.0_06/bin/java -server -Xms3072M -Xmx3072M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+CMSIncrementalPacing -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Djava.endorsed.dirs=/usr/share/tomcat/common/endorsed -classpath :/usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/commons-logging-api.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Djava.io.tmpdir=/usr/share/tomcat/temp org.apache.catalina.startup.Bootstrap start...then tomcat is running.

I hope this helps you 

5

QueueMetrics installation / Re: New Daylight Savings Time changes for the US

« on: March 15, 2007, 12:10:36 »

I believe if you have versions:
1.3.1_18
1.4.2_11
5.0_u6 (1.5.0_06)
6
... and higher you will be ok and no update is necessary.
The tzUpdater tool can also just be used to only check and validate the current time zone information. Just use the --verbose and --test options when you run from the command line like this:

Code: [Select]

java -jar tzupdater.jar --verbose --test
The readme for the tzUpdater tool can be found here: http://java.sun.com/javase/tzupdater_README.html

As a side note: make sure that you're not only changing the time on your linux machines by one hour. The entire time zone needs to be changed. For example, if you're living on the east coast USA, the time zone changed from -0500 to -0400. You can check this by running from a console prompt

Code: [Select]

date -R This will display the time and date including the GMT/UTC offset.

6

The tavern / Re: Welcome everyone

« on: March 07, 2007, 14:07:12 »

This interface seems to be nicer and more featureful than phpBB. I like it!