Submitted by newvolition on Sat, 07/14/2018 - 00:59
Debian 9
I try to enable log file rotation on a virtual server and get this message:
Log file rotation failed! : .. the log file /var/log/virtualmin/dkjonesandco.net_access_log is already being rotated at /usr/share/webmin/web-lib-funcs.pl line 1479.
It's fine if it's already enabled but virtualmin should pick this up and show the box as checked.
Thanks
Status:
Closed (cannot reproduce)
Comments
Submitted by JamieCameron on Sat, 07/14/2018 - 23:30 Comment #1
That's an unusual situation - how was rotation for that log setup if not via Virtualmin?
Submitted by newvolition on Sun, 07/15/2018 - 01:07 Comment #2
It wasn’t. This is a new domain on the system I just added. It’s worth mentioning that I first added it without the Apache web site, for email only. Then when I realized Apache site would be required for my webmail setup, autodiscover etc I added it, now this message shows when I try to enable log file rotation.
Submitted by JamieCameron on Sun, 07/15/2018 - 13:45 Comment #3
Was this domain perhaps deleted and then re-created at any point? I'm trying to figure out how this obsolete logrotate entry was still there.
Submitted by newvolition on Sun, 07/15/2018 - 18:31 Comment #4
It was moved to the subserver of another.
Submitted by newvolition on Tue, 07/24/2018 - 03:01 Comment #5
This happened again tonight. I disable Apache web site on a domain so Virtualmin would rewrite the apache directives, and upon re-enabling the domain I get this error:
Log file rotation failed! : .. the log file /var/log/virtualmin/mckenziemonuments.com_access_log is already being rotated at /usr/share/webmin/web-lib-funcs.pl line 1479.
Submitted by newvolition on Mon, 02/11/2019 - 22:56 Comment #6
I noticed that most of the time the Log File Rotation checkbox is not available when editing a server, however when I moved some domains from my old server, a few times I saw the box and checked it, then received this message. This may be because Debian already rotates them. I'm going to close this issue until it comes up under normal circumstances again.
Submitted by newvolition on Mon, 02/11/2019 - 22:56 Comment #7