Why I can’t see “Log file rotation enabled?” option in “Enabled features” for couple of domains? How can I enable this?
I have only this:
Mail for domain enabled? DNS domain enabled?
Apache website enabled? Webalizer reporting enabled?
SSL website enabled? MySQL login enabled?
PostgreSQL login enabled? IP-based virtual FTP enabled?
Spam filtering enabled? Virus filtering enabled?
Webmin login enabled? Enable DAV logins?
Enable AWstats reporting? Allow Mailman mailing lists?
I ran into the same problem. As soon as I select the “Log file rotation enabled?” feature for a domain and click “Save Virtual Server” the option is gone.
Is this a feature or a bug? Because I like to be able to switch it off again in a later stage.
I’d like to add to this my own findings.
I also discovered that, even though the “log file rotation” plugin is installed and enabled, and the appropriate “Allowed feature” is set in the Default Plan, I do not get the option to turn rotation on or off when I “Create Virtual Server” or edit an existing one (logged in as root).
In the “Delete server” list though the logfile rotation appears as one of the things that will get deleted.
How to solve this?
Obviously, new servers are created with the Logfile Rotation feature automatically turned on (if the Feature is enabled and the Plan allows it). There is no checkbox to turn it off in the web interface then.
Using the command line API it is possible though to turn it off after creation: “virtualmin disable-feature --logrotate --domain mydomain.com”
Afterwards, the “Logfile Rotation” feature does show up (turned off) in the “Edit Virtual Server” web interface function! When I (successfully) turn it on again there, it disappears once more from the list.
This is clearly a bug that should be fixed. Could a responsible coder here maybe give some feedback about this issue?
To finish off this issue, after posting a “bug report” I got the information that the option to turn off log rotation is deliberately missing from the GUI, so that inexperienced users don’t turn it off by accident and end up with overflowing hard drives. A valid point there. And disabling via API does, as I pointed out, work correctly.