Odd Behaviour with traffic quota system
I see there are some feature requests for making a more robust quota system, notably: http://bugtracker.ispconfig.org/index.php?do=details&task_id=2059 - this is a good thing.
I have recently had two issues with a client going over their traffic quota and their sites-enabled symlink being removed on the daily quota check cronjob.
In the most recent incident the following happened:
- The site went over quota and the sites-enabled symlink was removed for that domain
- I upped the quota to over their traffic limit
- The config symlink was not recreated by ISPC (I think it's reinstated every 24h ?) .. so I manually added the config symlink back in place and reloaded Nginx, site came back
- The domain was still marked as "active = n and traffic_quota_lock = y" - so on the next ISPC cron run. when a domain was updated, this (I think) triggered ISPC to remove the manually added symlink causing the domain to not respond (and client queries) - the symlink just disappeared.
- I manually added the symlink again as at #2 (closed) and then marked active = y and traffic_quota_lock = n manually. Since then the domain has remained available.
What should happen instead:
If the allowed quota is increased at #2 (closed), the vhost config symlink should be reinstated if it has been removed AND if the new value is higher than the most recent traffic count, rather than wait for the daily cron job to run.
This would avoid having to manually tweak settings and create symlinks to get the site back online.
Running ISPC latest, Nginx latest using PHP-FPM.
Thanks.