Article ID: 129687, created on Oct 25, 2016, last review on Oct 25, 2016

  • Applies to:
  • Operations Automation

Symptoms

CPU autoscale does not work for a VE, its History is flooded with events:

Autoscale failed

The VE was recently created or migrated to another node.

The following error can be found repetitively in /var/log/parallels.log on the node:

GetDiskAvailableSpace(/var/parallels) failed : 0x80000324 PRL_ERR_INCORRECT_PATH

/var/parallels is configured as a link to a non-existent location:

[root@vz01 ~]# ls -alh /var/parallels
lrwxrwxrwx 1 root root 27 May 25 21:37 /var/parallels -> /pstorage/cluster01/vmprivate
[root@vz01 ~]# ls /pstorage/cluster01/vmprivate
ls: cannot access /pstorage/cluster01/vmprivate: No such file or directory

Cause

Misconfigured symbolic link for /var/parallels directory prevents the collection of available disk space statistics by OACI, which breaks autoscaling.

Resolution

Correct the symbolic link to point to the actual VM storage location:

[root@vz01 ~]# unlink /var/parallels
[root@vz01 ~]# ln -s /pcs/vmprivate /var/parallels
[root@vz01 ~]# ls -alh /var/parallels
lrwxrwxrwx 1 root root 14 Oct 25 23:59 /var/parallels -> /pcs/vmprivate

Search Words

PRL_ERR_INCORRECT_PATH

Autoscale failed

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF