• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Upgrade to Plesk 11.5

Tozz

Regular Pleskian
I've just upgraded a machine to Plesk 11.5 running Debian 6 (Squeeze). The installer reported:

Code:
WARNING!
Some problems are found during fail
Cannot upgrade vhost directories for domains. Please run /opt/psa/bin/repair --update-vhosts-structure manually.(see log file: /tmp/plesk_11.5.30_installation.log)

Continue...

So that is what I did

Code:
2013-08-07T13:41:12+02:00 ERR (3)  [util_exec]: proc_close() failed
Error: mkdir: cannot create directory `./example.nl/logs': File exists
ERROR: Cannot relink logs. Target directory '/var/www/vhosts/example.nl/logs' is in invalid state.

I tried to delete example.nl/logs/, but this doesnt help. The script re-created the directory and then returns the same error message. The message repeats about 20 times.

Any ideas?
 
Knowing the version you upgraded from would probably help. After you get the error what type of file is /var/www/vhosts/example.nl/logs and its permissions?

The error messages you posted just indicates that some users (probably) won't be able to access up-to-date logs for their domains via shell or ftp. However they should still be able to do that via Panel.
 
I ran the latest Plesk 11.0 release (we have auto-installation of microupdates enabled). He permissions look alright, and are equal to other vhosts:

drwx------ 2 onthejob687 root 4096 Aug 7 13:40 logs

We have upgraded multiple Plesk machines to 11.5, but this is the first time I encounted this error. I still cant figure out why, as the permissions look to be the same as other vhosts I've checked.

eg, another domain:

drwx------ 2 pgt root 4096 Aug 7 15:06 logs
 
Yes, permissions are OK. You can try removing logs/ directories from problematic domains and rerunning repair utility.
 
@Tozz did you fixed this issue already? Facing the same problem and deleting the /logs directory ain't helping....
 
Back
Top