Master.csv file cant be open

[yasserin]

Hi I post this on the support forum but since Im using VicidialNow 1.1 I will post it here, Im using Asterisk 1.2.27, vicidial 2.0.4.1 rc4, sometime I get this error:

ERROR[4599]: cdr_csv.c:237 csv_log: Unable to re-open master file /var/log/asterisk//cdr-csv//Master.csv : Read-only file system

Im still getting this error, and Im not even recordings the calls, I dont know why this file get huge or it get lock up sometimes. when this error happen, I cannot even reboot my server (which is the only way to temporaly solve this issue) because many coomands do not respond. All my calls precedes the AGI(agi://127.0.0.1:4577/call_log), so these calls couldnt go through.

I had to say that these problem presents doesnt present every day, but I had to reboot my server like ten times for this problem.

Can you help me with these log problem,

[gardo]

When does your system go to read-only mode? Do you have sufficient disk space?

[yasserin]

I dont know, it suddenly happens, and I have to restart the system


Here is the result df -h

Filesystem Size Used Avail Use% Mounted on
/dev/hdd1 145G 24G 114G 18% /
/dev/hda1 99M 12M 83M 12% /boot
tmpfs 1.5G 0 1.5G 0% /var/spool/asterisk/monitor

[yasserin]

here's du /var/log/asterisk//cdr-csv//Master.csv

652 /var/log/asterisk//cdr-csv//Master.csv

One question, what do you believe that could me the problem.... this problem is happening very often, I dont think is a disk space problem, beacuse as you can see I had many space available.

here are the files that asterisk create on this dir

Master.csv Master.csv.2008-09-06---70458
Master.csv.2008-08-19---123919 Master.csv.2008-09-08---143331
Master.csv.2008-08-19---160214 Master.csv.2008-09-08---70638
Master.csv.2008-08-20---71010 Master.csv.2008-09-09---70854
Master.csv.2008-08-23---70555 Master.csv.2008-09-10---70112
Master.csv.2008-08-23---91813 Master.csv.2008-09-11---70348
Master.csv.2008-08-24---65105 Master.csv.2008-09-11---92451
Master.csv.2008-08-26---160649 Master.csv.2008-09-12---70605
Master.csv.2008-08-27---71207 Master.csv.2008-09-13---70155
Master.csv.2008-08-28---70522 Master.csv.2008-09-14---70509
Master.csv.2008-08-29---70733 Master.csv.2008-09-17---130231
Master.csv.2008-08-30---134855 Master.csv.2008-09-17---182607
Master.csv.2008-08-30---71817 Master.csv.2008-09-17---70117
Master.csv.2008-09-01---145128 Master.csv.2008-09-18---71331
Master.csv.2008-09-01---70104 Master.csv.2008-09-19---143411
Master.csv.2008-09-02---100315 Master.csv.2008-09-19---70229
Master.csv.2008-09-02---71150 Master.csv.2008-09-19---95915
Master.csv.2008-09-03---131943 Master.csv.2008-09-20---70822
Master.csv.2008-09-03---70802 Master.csv.2008-09-21---73117
Master.csv.2008-09-04---184120 Master.csv.2008-09-22---114613
Master.csv.2008-09-04---192911 Master.csv.2008-09-22---70701
Master.csv.2008-09-04---70914 Master.csv.2008-09-22---80913

today we had to restart two time the server, its there a way to stop asterisk from creating this file???

[yasserin]

In some forum says that maybe I exceed the numbre of open files but as you can see Im not even on the half capacity what this distro has.
here's the /proc/sys/fs/file-nr


1472 0 309545

[gardo]

I'm not really sure what's happenning. I haven't experienced this before. Can you check the system logs particularly /var/log/messages for any clues? Master.csv is the main cdr of asterisk. This is where it keeps all its transactions/activities.

[yasserin]

This is the error that gives me when asterisk stops

Sep 25 19:08:01 WARNING[3276]: res_agi.c:210 launch_netscript: Connect to 'agi://127.0.0.1:4577/call_log' failed: Connection refused
== Spawn extension (default, 447511202, 1) exited non-zero on 'SIP/3047-b78541f0'
Sep 25 19:08:01 ERROR[3276]: cdr_csv.c:237 csv_log: Unable to re-open master file /var/log/asterisk//cdr-csv//Master.csv : Read-only file system
Sep 25 19:08:01 ERROR[3276]: cdr_custom.c:129 custom_log: Unable to re-open master file /var/log/asterisk/cdr-custom/Master.csv : Read-only file system


as for the linux log, it doesnt gives me much information, only when I reboot, and the after reboot kernels logs