Everything,
It seems I cannot deploy an application that works fine on my local cluster to a cluster in Azure.
The strange thing is that I was able to deploy this application in the past, but it seems to be unable now. After deploying the application, it seems that my stateless services are first deployed without any problems, but my full-state services and subjects do not seem to be able to find suitable nodes for replicas, as I seem to receive the following warning (through the service explorer fabrics, when choosing an application):
Unhealthy event: SourceId='System.PLB', Property='ServiceReplicaUnplacedHealth_Primary_8f41b6fb-3c6f-4916-9f85-27da0171ae6d', HealthState='Warning', ConsiderWarningAsError=false. The Load Balancer was unable to find a placement for one or more of the Service Replicas: fabric:/Namespace/ActorService Primary Partition 8f41b6fb-3c6f-4916-9f85-27da0171ae6d could not be placed, possibly, due to the following constraints and properties: Placement Constraint: N/A Depended Service: N/A Constraint Elimination Sequence: NodeBlockList eliminated 5 possible node(s) for placement
In further research, I also encountered the following error:
Error event: SourceId='System.Hosting', Property='CodePackageActivation:Code:EntryPoint'. ServiceManifestName='ActorPkg', NodeName='_nt1vm_4',AggregatedHealthState='Error'.
When checking all the log files in the blob repository, as well as on the trace, I also found the following log instructions:
2016-5-12 12:54:15.176,Warning,1516,2528,Hosting.ProcessActivationManager,Application service 66933b89-78e9-4590-8971-d0cad139d956 with processId 3240 for parent process 310a2a579b75d9847ba5a43d6b365d7c terminated with exit code 2148734720 2016-5-12 12:54:15.176,Warning,1516,2528, Hosting._Nodes_ProcessUnexpectedTermination@310a2a579b75d9847ba5 a43d6b365d7c,ServiceHostProcess: Process.exe for ApplicationId 66933b89-78e9-4590-8971-d0cad139d956 terminated unexpectedly with exit code 2148734720 on node id 310a2a579b75d9847ba5a43d6b365d7c 2016-5-12 12:54:15.176,Informational,1516,2528,Hosting.ProcessActivationManager,Sending ApplicationService host down notification for apphost 66933b89-78e9-4590-8971-d0cad139d956, node 310a2a579b75d9847ba5a43d6b365d7c 2016-5-12 12:54:15.176,Warning,2888,2556, Hosting.ApplicationHostManager@310a2a579b75d9847ba5a43d6b365d7c :131075269508464788,Processing termination of activated Application Host: HostId=66933b89-78e9-4590-8971-d0cad139d956, ExitCode=2148734720 2016-5-12 12:54:15.176,Warning,2888,2556,IPC.ServerFailedToRemoveClient,527e532390 client 66933b89-78e9-4590-8971-d0cad139d956 not found 2016-5-12 12:54:15.176,Informational,2888,2556, Hosting.ApplicationHostManager@310a2a579b75d9847ba5a43d6b365d7c :131075269508464788,RemoveActivationTableEntry: ErrorCode=S_OK, HostId=66933b89-78e9-4590-8971-d0cad139d956 2016-5-12 12:54:15.176,Informational,1516,2528,Transport.Enqueue,adb77036b0 enqueue ef74d99d-1a29-4c34-b6d1-1f59542a42d8:1926 False 319B @ qsize 0/0B 2016-5-12 12:54:15.176,Informational,2864,2556, RA.HostingProcessClosedEvent_Hosting@310a2a579b75d9847ba5a43d6b3 65d7c:131075269508464788,RA on node 310a2a579b75d9847ba5a43d6b365d7c:131075269508464788 performing AppHost down processing for apphost: 66933b89-78e9-4590-8971-d0cad139d956/ 2016-5-12 12:54:15.176,Informational,2864,2556, RA.MultipleFTWorkBegin_MultipleFT@310a2a579b75d9847ba5a43d6b365d 7c:131075269508464788,Multiple FT Work Begin [Activity: AppHostClosed 66933b89-78e9-4590-8971-d0cad139d956]. FTs 36 2016-5-12 12:54:15.176,Informational,2888,2556, Hosting.HostingHealthManager@310a2a579b75d9847ba5a43d6b365d7c :131075269508464788,ServicePackage ReportHealth: HealthReport(fabric:/Namespace+ActorPkg+310a2a579b75d9847ba5a43d6b365d7c instance=131075312250519674 System.Hosting CodePackageActivation:Code:EntryPoint Error ttl=Infinite sn=131075312551846737 There was an error during CodePackage activation.The service host terminated with exit code:2148734720 removeWhenExpired=false 2016-05-12 12:54:15.184 priority NotAssigned)
If anyone has any ideas or suggestions as to why my application can no longer be deployed in the cloud, that would be very helpful!
Yours faithfully