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/webalizer-set-time-zone.sh /var/www/vhosts/10/100291/webspace/conf/webalizer.conf failed with code 127 saying: STDOUT: '' STDERR '/bin/sh: /etc/webalizer-set-time-zone.sh: No such file or directory
Webspace directory is not created.
In OA 5.5 path for webalizer script webalizer-set-time-zone.sh 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.