Current logrotate configuration is not valid

Hi!

I seen few posts about it with solutions but my case it a bit complicated.

I have "error: stat of /var/log/virtualmin/.mydomain.com_access_log failed: No such file or directory"....

The problem is that i have around 50 virtual servers using domains like "server1.mydomain.com , server2.mydomain.com , server3.mydomain.com ... etc"

Without more clues, it's impossible for me to know which virtual server log file is causing that problem.

Do you have an idea about how to find the right file?

Status: 
Closed (fixed)

Comments

Howdy -- it looks like the problem is specific to "mydomain.com", not one of the sub-domains.

Where is it that you're seeing the above error though?

I see it when i re-check virtualmin configuration

Actually, it's showing a "." in front of the domain name, which wouldn't normally be there for the primary "mydomain.com" domain.

That makes me wonder if something else is going on, such as an Apache VirtualHost pointing to the wrong log file.

If you go into Limits and Validation -> Validate Virtual Servers -> Validate Now, and have it perform a validation on all your domains, does it generate any errors or warnings for any them? I'm wondering if that may be able to determine where the issue is here.

I'm getting just one error:

Administration user : Encrypted password for Unix user xxxxxxx does not match virtual server.

Do you think it can come from this?

Also, while we were making tests with the API, i created a domain .mydomain.com to test if it will work for fun and the domain has been created but that also created some errors that i dont really remember about.

Ok. Finally, the problem was coming from the domain created with the API .mydomain.com

There was a line .gestionminute.com.... in /etc/logrotate.d

I just removed that line and everything went fine.

Thanks for your support!

Great, I'm glad it's working for you now!

We'll look into whether Virtualmin should allow a domain beginning with a "." to be added, as it sounds like that was the source of the trouble you were seeing.

Automatically closed -- issue fixed for 2 weeks with no activity.

Automatically closed -- issue fixed for 2 weeks with no activity.