QueueMetrics > Running QueueMetrics

Rotated Logs Per SIGXFSZ (exceeded files limit)

(1/3) > >>

wilsonchua:
I got this error message on my asterisk :
" Asterisk queue logger restarted".
"Rotated Logs Per SIGXFSZ (exceeded files limit)"

Then from that time on, I couldnt get any stats on the queuemetrics.
Has anyone come across this yet? Any ideas on how to resolve this?

wilsonchua:
further INfo:
I went into my /var/log/asterisk and saw a lot of empty sized event_log.xxxxx
Could these be related?

What could be causing it? And how is it affecting queuemetrics?

wilsonchua:
I read this:
http://www.mail-archive.com/asterisk-users@lists.digium.com/msg188549.html

Basically, the logrotate is also triggered when a large file exceed 2gb in size. This causes the the SIGXFSZ to be triggered, which in turn triggers the log rotation...

So i used this command to look for large files :
find / -type f -size +50000k -exec ls -lh {} \;| awk '{print $9": " $5}'

And found this:
/var/log/asterisk/cdr-csv/Master.csv: 2.0G

I will back this file up to Master.csv.bak and then rm the Master.csv and see if this resolves the situation.

wilsonchua:
It did! Apparently, the Master.csv was never rotated, so its file size just kept on increasing.
AFter a while, it hit the 2gb limit and that triggered the SIGXFSZ (exceeded files limit), in turn , this triggered the log files to rotate.
This results in a LOT of event_log.* and Full.x.* files being made of zero size file.

I restarted qloader with /etc/init.d/qloader restart

I can now see data in the 'today' , real time monitoring.

I need your advise if i am to do anything about the past 2 days where no data is still showing in the queuemetrics.
Should i just wait for the qloader to process everything>? Or should i manually run some script?

marcos:
Hi,

It depends.
If the problem was related to asterisk, it probably was not able to update the queue_log file.
If you're able to identify events for the past days, on that file, they probably were already update to your database by the qloader.
If you're able to identify events that are present in the queue_log file but not in the queue_log table (i.e. the qloader already updated more recent events) your qloader daemon will not be able to update past events automatically.
In order to fill the hole you would like to use the queuePartialUpdater tool as explained here: http://queuemetrics.com/manuals/QLoader-chunked/ar01s03.html

Thank you and regards,
Marco Signorini.

Navigation

[0] Message Index

[#] Next page