Article ID: 129540, created on Sep 29, 2016, last review on Oct 2, 2016

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0
  • Operations Automation 5.5


Note: issue only affects installations where NG Webcluster was deployed before OA 5.5. Standalone NG installations are not affected.

Provider migrated NG cluster from CloudLinux 5 to CloudLinux 6. After that all new provisioning tasks fail with the following output:

 Internal error: /bin/sh /bin/sh /etc/ /var/www/vhosts/10/100291/webspace/conf/webalizer.conf failed with code 127 saying: STDOUT: '' STDERR '/bin/sh: /etc/ No such file or directory

Webspace directory is not created.


In OA 5.5 path for webalizer script was changed, but that was not reflected in OA database. After migration and addition of new CloudLinux 6 nodes to cluster, settings propagated from database and instructed new servers to start script from non-existing location.


This issue was reported to the Engineering team with ID POA-104736 and will be fixed in future product releases. Please, contact your technical manager or representative of Odin technical advisors to clarify status of the issue.

Workaround for the issue is available, but requires direct OA database manipulation. Please, contact Odin technical support for further information.

Search Words

provisioning failed after migration

NG provisioning failed

/etc/ No such file or directory

migration to cloudlinux 6

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF