Create OS layer version fails when offload compositing is enabled

Create OS layer version fails when offload compositing is enabled

book

Article ID: CTX666103

calendar_today

Updated On:

Description

Issue : Creation of OS layer version fails, when 'Use Offload Compositing' option is enabled.


Error : "The Compositing Engine failed to initialize after '00:20:00'"
image.png
image.png
  • Console shows 'Waiting for the Compositing Engine machine to be ready', followed by 20 minute time out.  
  • ELM logs show 'CompositingEngineRegisterWithElmTimeout' timeout being reached.
ERROR [84243] AsyncWorkItemManag: WorkItem with id 51773445 finished with an exception: Uni.Core.Handlers.Exceptions.GlobalizedErrorException`1[Uni.Core.Contract.Results.TimeoutErrorCategory]: MessageId=CompositingEngineRegisterWithElmTimeout, DefaultTitle=, CategoryData={[TimeoutErrorCategory { Timeout = 00:20:00 }]}

Resolution

  • Allow required (bi-directional) ports between the ELM and Composite Engine machine on the XenCenter Hypervisor.
Compositing Engine machine>> ELM  | Allow Port 443 
ELM >> Compositing Engine | Allow Port 443 

Next got Error :  “The Connection failed” 

  • Compositing Engine machines must be able to contact the ELM on port 443 and port 3260 (Layer disk access via iSCSI).  All of the layer data flows between the ELM and  Compositing Engine machines over iSCSI.
  • Compositing Engine >> ELM  Allow '3260' ISCSI port to successfully create the packaging machine. 

Problem Cause

  • Network Connectivity issue between Compositing Engine machine and the ELM. On Compositing Engine machine, startup tasks show error “no endpoint listening at https://10.x.x.6x/unidesk.web/API.asmx".
image.png
  • Confirm the Compositing Engine machine is getting an IP . It is listening on port 80/ 443.
image.png
     
    Powered by Wolken Software