Open fails logged in /var/log/nginx/error.log

[TimReeves]

I've noticed that on most of my servers, /var/log/nginx/error.log accumulates error messages like this:

2015/06/01 04:13:45 [emerg] 28449#0: open() "/var/www/vhosts/system/DOMAIN/logs/proxy_access_log" failed (13: Permission denied)

This happens in the early hours of the morning, for most servers where the Nginx module is installed, once for each domain, and whether PHP-FPM package is installed or not. More specifically:

• At 2 Servers on Ubuntu 12.04.5 LTS / Plesk 12.0.18 Update #48 / Nginx + PHP-FPM
• At 1 Server on Ubuntu 14.04.2 LTS / Plesk 12.0.18 Update #48 / Nginx (no PHP-FPM)

The ownerships are

• /var/www/vhosts/system/DOMAIN/logs = drwx------ psaadm root
• /var/www/vhosts/system/DOMAIN/logs/proxy_* = rw-r--r-- nginx root

BUT it does NOT happen on another Server, otherwise identical to the first 2 noted, the difference there is that the proxy_* log files belong to root:root (not nginx:root).

Something is a bit weird somewhere, howcome otherwise more or less identical servers have different log owners? Which is correct?

I rather suspect that the messages may stop if I added all "psa" groups to the nginx group in /etc/group, or made root the log owner. But I don't feel comfortable with the latter, and anyway the problem should be solved, not worked around.

Any help would be much appreciated!

Cheers, Tim

 

[IgorG]

Try to reset all default vhosts structure permissions with

# plesk bin repair --restore-vhosts-permissions

 

[TimReeves]

Thanks Igor, have tried that, but I can't see any change in the relevant directory and file ownership/permissions.

The log files are HARD-LINKED from two places:

1 /var/www/vhosts/system/(SUB)DOMAIN/logs drwx------ 2 psaadm root

2a /var/www/vhosts/system/DOMAIN/logs drwx------ 3 {webspace-ftp-user} root
2b /var/www/vhosts/system/DOMAIN/SUB/logs drwx------ 3 {webspace-ftp-user} root (SUB same rights as "logs")

These permissions are set correctly as noted here.
I can't find any place saying what the ownership/permissions of the log files themselves should be.
Perhaps that is the inherent problem - no one ever decided or documented that aspect...

AHA - this is a long-known and still-unfixed problem in Plesk!

Igor, could you escalate that a teeny-weeny bit more forcefully to the developers please?
I have a script monitoring a lot of the logs for any non-zero size, so that I can react to any problems.
And these spurious entries (or not spurious, depending on what is actually happening there) cause mails to be sent to me every night...

Thanks!

 

[TimReeves]

Hi all,

any chance of a reply on this one? After all, it really does seem like a bug in Plesk, and it is filling up lots of logs unneccessarily...

Alternatively, is there another place where I can register bugs directly to the developers?

Cheers,

Tim

 

[IgorG]

Hi all,

any chance of a reply on this one? After all, it really does seem like a bug in Plesk, and it is filling up lots of logs unneccessarily...

Alternatively, is there another place where I can register bugs directly to the developers?

Cheers,

Tim

You can submit your bugreport here http://www.odin.com/support/plesk/bugreport/
Also I can recommend to create a request to support team to do in-depth investigation to find the reason and to fix it. Please create a ticket to support at https://www.odin.com/support/request/ .
You may have free support, please check what kind of Plesk license you use for available support options at http://kb.odin.com/en/121580 .
If there’s no free support in your case, you can order Plesk per-incident support at http://www.odin.com/support/buy-support/ Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.
If it is found that your problem was caused by product bug w/o available solution or workaround from Parallels, then your purchase will be re-funded.

 

[TimReeves]

I have now submitted a bug report on this at http://www.odin.com/support/plesk/bugreport/