Search Engine: Elastic

Article ID: 129638, created on Oct 18, 2016, last review on Aug 10, 2017

  • Applies to:
  • Operations Automation 6.0


All Legacy VPS module related tasks fail with the message:

The remote server is temporarily down, details:
system exception, ID ''
OMG minor code (2), described as 'No usable profile in IOR.', completed = NO

VPSManager service controller generates a core dump every 5 minutes:

[root@osscore ~]# ls -Altrh  /usr/local/pem/var/cores/
-rw------- 1 pemuser pemgroup 224M Oct 18 16:56 core.31663
-rw------- 1 pemuser pemgroup 225M Oct 18 17:01 core.32647
-rw------- 1 pemuser pemgroup 225M Oct 18 17:06 core.3554
-rw------- 1 pemuser pemgroup 225M Oct 18 17:11 core.7709
-rw------- 1 pemuser pemgroup 225M Oct 18 17:16 core.8385

There is a "Plesk version update" task in rescheduled state.

The VPS the task belongs to contains a directory instead of a Plesk version file:

[root@vps-1010101 ~]# file /usr/local/psa/version
/usr/local/psa/version: directory

or it could be an empty file as well:

[root@vps-1010101 ~]# file /usr/local/psa/version
/usr/local/psa/version: empty


Inconsistency inside the VPS crashes OA VPSManager service controller. This issue has been submitted to Odin Engineering team as CCU-13609: "VPSManager SC crashes if /usr/local/psa/version is a directory inside VPS with Plesk".


Cancel the task temporarily to stop the crashes.

Workaround is to fix the file inside the VPS manually:

[root@vps-1010101 ~]# rm -rf /usr/local/psa/version
[root@vps-1010101 ~]# echo "12.5.30 CentOS 6 1205160608.10" >> /usr/local/psa/version
[root@vps-1010101 ~]# cat /usr/local/psa/version
12.5.30 CentOS 6 1205160608.10

Valid version of Plesk could be obtained from file /usr/local/psa/core.version.

Run the task again, once the file gets fixed.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF