All installation and configuration problems and questions
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
by dj mondo » Thu Oct 13, 2011 8:33 pm
If i wanted to maintain hard drive space, what files or folders, would i need to look at, that would be the biggest files. Logs, recordings, which ones would be the ones i would like to maintain and make sure the drive space is maintainable?
Thank you
Armando
VERSION: 2.4-309a | BUILD: 110430-1642 | Asterisk Version: 1.4.38-vici | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation l Built By Vici Group.
-
dj mondo
-
- Posts: 327
- Joined: Mon Feb 21, 2011 9:19 am
by mflorell » Fri Oct 14, 2011 12:34 pm
/var/log/astguiclient/
/var/log/asterisk/
/var/spool/asterisk/monitorDONE/
-
mflorell
- Site Admin
-
- Posts: 18384
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
-
by boybawang » Tue Oct 18, 2011 4:39 am
you can delete the /var/spool/asterisk/monitorDONE/ORIG/* folder contents since they take much of your diskspace because they are raw and unprocessed audio WAV files
you also have to check out /var/log/apache2 or /var/log/httpd the files grow when un noticed
you can check disk space in mb by doing the following :
df -m
to check disk usage:
du -m /var/
shows the sizes on each folder under /var/
-
boybawang
-
- Posts: 989
- Joined: Sat Nov 14, 2009 1:18 pm
- Location: Dumaguete City, Negros Oriental, Philippines
-
by ramizuabhalim » Thu Jan 09, 2020 11:21 am
Hi,
Once I'm monitor the Vicidial.. Probably the hard disk quite fast going full because of the database which is /var/lib/mqsl/asterisk.. how to maintain from the hdd full without any impact the reporting or else.
-
ramizuabhalim
-
- Posts: 97
- Joined: Sat Dec 07, 2019 11:14 am
by covarrubiasgg » Fri Jan 10, 2020 3:31 pm
what hard drives are you using, the database should not be a problem to maintain unless you are using ridiculously low capacity drives.
-
covarrubiasgg
-
- Posts: 420
- Joined: Thu Jun 10, 2010 10:20 am
- Location: Tijuana, Mexico
-
by williamconley » Fri Jan 10, 2020 3:59 pm
There are many log tables, some of which serve no purpose. There is a log archiving routine in crontab that is commented out. For Necessary log data it can archive (instead of delete) which doesn't save any room ... but: There are options for that script which can empty many of the unused tables. For instance, carrier logging is not used in any reports and is really only needed under very special circumstances. Carrier logs can be HUGE.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
-
williamconley
-
- Posts: 20258
- Joined: Wed Oct 31, 2007 4:17 pm
- Location: Davenport, FL (By Disney!)
-
by mflorell » Fri Jan 10, 2020 5:08 pm
I can't think of any log tables that serve no purpose at all, although there are several that are really only there to help with debugging.
As for managing them, we have added several 'trim' options to the "ADMIN_archive_log_tables.pl" script that we have set up for several clients that will wipe out old logs in some of the larger log tables.
- Code: Select all
# /usr/share/astguiclient/ADMIN_archive_log_tables.pl --help
allowed run time options:
[--daily] = only archives call_log, vicidial_log_extended, vicidial_dial_log and vicidial_drop_log tables, only last 24 hours kept
[--carrier-daily] = will also archive the vicidial_carrier_log table when --daily is run
[--vlog-daily] = will also archive the vicidial_log table when --daily is run
[--days=XX] = number of days to archive past, default is 732(2 years)
[--months=XX] = number of months to archive past, default is 24(2 years) If 'days' used then 'months' ignored
[--queue-log] = archive QM queue_log records
[--only-trim-archive-level-one] = will not perform normal archive process, instead this will only delete records
that are older than XX months from least important log archive tables:
call_log_archive, vicidial_log_extended_archive, vicidial_dial_log_archive, vicidial_drop_log
[--only-trim-archive-level-two] = same as --only-trim-archive-level-one, except includes tables:
vicidial_carrier_log_archive, vicidial_api_log_archive, vicidial_rt_monitor_log_archive
[--only-trim-archive-level-three] = same as --only-trim-archive-level-two, except includes tables:
vicidial_log_archive, vicidial_agent_log_archive, vicidial_closer_log_archive, vicidial_xfer_log_archive
[--recording-log-days=XX] = OPTIONAL, number of days to archive recording_log table only past
[--did-log-days=XX] = OPTIONAL, number of days to archive vicidial_did_log table only past
[--cpd-log-purge-days=XX] = OPTIONAL, number of days to purge vicidial_cpd_log table only past
[--wipe-closer-log] = OPTIONAL, deletes all records from vicidial_closer_log after archiving
[--wipe-all-being-archived] = OPTIONAL, deletes all records from most tables after archiving
[--quiet] = quiet
[--calc-test] = date calculation test only
[--test] = test
-
mflorell
- Site Admin
-
- Posts: 18384
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
-
Return to Support
Who is online
Users browsing this forum: No registered users and 136 guests