I’ve searched the forum and not been able to find a match to a solution or explanation for this situation (doesn’t mean it isn’t there, of course).
When running the “Validate Virtual Servers,” I am presented with output for 6 out of 10 of them indicating: domainname.com
All features are good
and for the remaining 4 of them: domainname.com
Log file rotation : No logrotate configuration found for file /home/username/logs/php_log
Unlike other forum users reports on this issue, in the backup email I receive after my nightly backups for all sites, I get this for all sites:
Copying Logrotate configuration …
… done
Could it be a false indication?
Can anyone help me understand why the server validations indicate this, what it means, or better yet, how to I make it go away?
if there is a php_log file in /home/username/logs/php_log
then add it to the form under Webmin > System > Log File Rotation in the same section as the ones that havn’t complained.
if there is no php_log file in /home/username/logs/php_log create the file and
then add it to the form under Webmin > System > Log File Rotation
I had to do that with several of my virtual servers. I had been making them consistent with with PHP Options FPM. I don’t know exactly what caused it but that fixed it.
Mine were missing the file and the error indicated that.
I think on my system this had to do with changing virtual servers between being aliases and sub-servers of the main virtual server and vice-versa. I was working with one main domain with 14 other domains resolving to it as well and resolving them on the main virtual server as opposed to using a registrar forward.
One thing I noticed (I will try to explain it adequately here) is I think AWStats doesn’t work for the subdomains, which is important if one wants to know whether a particular domain is being used. And with all the switching back and forth I was doing (between aliases and sub-servers of the main virtual server and vice-versa), I did notice that sometimes the settings seemed to get bunged up. They ended up not being the way they would be if one were to set a virtual server (or an alias) up a particular way from scratch (fresh). One thing in particular I noticed was a pull-down labeled “Server configuration template” ending up in a state where I could choose either “Default Settings” or “Settings For Sub-Servers” - after changing between sub-server or alias states. Fresh creation of an alias or a sub-server doesn’t allow a choice between the two.
