3CX Disk Usage

[Michael Hogeling]

Hello,

I have a 3CX hosted on a linux ovh instance, the server has 16GB Ram, 100GB SSD and 6 vcores.

The business runs 9am - 5pm and the phones are not used out of hours, I logged the disk space at 86.2GB free last night and by morning it has dropped to 71.8GB free. What could be causing this? We upgraded the instances disk space and the consumption has only increased, I find my self often deleted the daemon file to make space. All call recording are remotely backed up at 6pm so I know this is not using space.

Regards in advance.

 

[Alphabetic]

What mode is your logging set to?

 

[Michael Hogeling]

What mode is your logging set to?

The logging is disabled, I only turn this on when it is required. We also use 3CX Monitor by voiptools for most diagnostics

 

[JohnS_3CX]

Hi Michael,

Some of the space could be used by voicemail, recordings, firmware, captures, CDRs and backups. Also by system logs (including debug logs that have to manually be enabled outside of the management console) and log backups.

You need to familiarize yourself a little more with Debian in this case, and run some shell commands to see which files/folders have what size so you can determine where most of the space is used. A quick google search can provide you with a couple of ways to list and sort the files.

Once you do, you can decide how to manage the growth of the files accordingly.

 

[Michael Hogeling]

I have already stated that I am regularly deleting the daemon log and system log. Those files combined were at 60GB yesterday, I had to delete and restart the pbx. Because of the disk being 100% we lost two hours of call recordings. Again the recordings are backed up at 6pm to a remote location, the logs are disabled and the two files using up the most space are as below

20GB used in /var/log
10.2GB on daemon log
4.1GB on syslog
5.7GB on syslog.1

 

[JohnS_3CX]

These are both linux logs. You really need to look inside and see what is generating all the traffic.

The only recommendation I can make at the moment is to disable any 3rd party software you use on this system (anything that didn't come with our ISO) and reboot to see if the problem stops when it runs for a few hours.