Around 4 months ago I changed VPS providers, so had to re-install ISP Config on the new system. I noticed today during maintenance that my /var/logs directory was much larger than it should be. After digging around a bit I noticed that the logs are not getting compressed and removed after a period of time as they should be (my old installation on the old server had no problem with log rotation). Is there anything I can do to fix this problem?
Which logs do you mean? The directory contains logs that are managed by the Linux os and others that are managed by ispconfig, so it is important to know which exact log file is having issues.
The files in /var/log/ispconfig/httpd were the ones I noticed. From what I know these get rotated by the daily php script. I've tried running the php script manually as well and it does not perform the log rotation. I have logs dating back to April 19th when the new VPS was initially set up. Cron has no problem working, as I have about a dozen other jobs. I could always set up the log rotation myself, but I'm curious why ISP Config is not handling it.
I set the server up as a new installation and then migrated my user files / website data back from S3. So, I did not copy anything from my original installation's fstab file. I will investigate the fstab file shortly. Thanks!
The fstab file has an entry for each domain hosted on this system. They are all similar to the following: /var/log/ispconfig/httpd/zontaottawa.ca /var/www/clients/client0/web3/log none bind,nobootwait,_netdev 0 0 However, upon checking the /var/www/clients/client0/web3/log directory, it appears empty. If I check the /var/log/ispconfig/httpd/zontaottawa.ca directory it has months worth of logs though. What could be the reasoning for this behaviour?
Probably the vm is not obeying the fstab file. Run: mount -a and check the log directories of the sites again, the log files should show up then.
You are correct. That was the problem. I'll add the command to my startup scripts. Thanks a lot for the advice!
