queue_log problem?

[guin]

actually i have playing around with queuemetrics since yesterday ...
i have installed queuemetrics and asterisk in different machine ... and i have connected  few phone with the asterisk machine. it goes well at first.. but after i made around 12 calls, queuemetrics did not show progress anymore. even i log in the agent, queuemetrics did not show anything.... its that something wrong with my queue_log file? how can i check where's the problem ?

[QueueMetrics]

How do you connect the two machines in order to send data over to the QM box? are you using qloaderd?

Anyway,
1. check that the new data gets appended to the queue_log file
2. if you are using qloaderd, check that the new data actually gets written in the queue_log table of the Qm database

If the two tests above pass,
3. check that your queue definition is correct, that is you are running reports for existing queues

[guin]

nop.. i wasnt using queueloader. at my asterisk server i mount nfs file to queuemetrics machine. i checked the queue_log file several times, it remain the same->65 lines, even i made new calls.

previously it when i using the queue , it run without problem. i have checked the queue definition, it is ok...

is there any other option to solve the problem?

[QueueMetrics]

You mena the file is not written to by the Asterisk process? this sounds really weird... are you sure your calls are hitting the queue() command at all?
If you instead do not see the updated lines on the oether side of the NFS share, there is likely some caching/buffering being made at the mount point; thry and have a look at the various share and mount options.

[guin]

i am using console port connect to my asterisk machine, it shows the process and record of the calls. it runs smoothly.therefore, i believe that the asterisk machine do record the calls.

as i have mounted the queue_log file at QM machine.i did experiment on it. i tried to remove the queue_log file, and test it again.(means the queue_log file starts with nothing) the result is the when the queue_log file reached 65(3.8kb) or 69(4.0kb) lines, the contents wont be updated anymore... is this because of the file size is restricted by QM?

[QueueMetrics]

We have a number of customers who use a NFS share - QM is read-only on it, so there is no reason why the share does not get updated.

Anyway, if you want to avoid wasting time on it, why don't you try implementing the Qloaderd approach to send data from the Asterisk to the QM database? you can find the latest qloaderd and its docs in QM under WEB-INF/mysql-utils.

[guin]

but my asterisk machine do not support perl.
i have been wonder, is there any limitation for mounting file?

[QueueMetrics]

No, but Qm does not know anything about the fact the file is shared, so it treats it as if it were a regular file on the filesystem.

My idea is that somehow some caching mechanism kicks in, so that QM ends up not seeing the latest version of the file, so:

- Find some mount option that will make the file readable correctly on the QM machine. I would start by playing with rsize and wsize and nfsvers and noac - see http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-nfs-client-config.html - also  see man nfs on your Linux box.

- Use some other file-sharing mechanism, like SMB

Please keep us posted on how it goes.