4
votes

I broke my service fabric cluster some how, now all it says is "Status: Upgrade service unreachable".

How do I find out what's wrong? My VMs are up but I can't access the SF Explorer, and the SF blade in the Azure portal contains no nodes!

I believe this has something to do with setting up the reverse proxy. I have downloaded and modified the default 5VM template and added in the reverseProxyEndpointPort property, upon deploying the VM's I get this message

Starting deployment...
New-AzureRmResourceGroupDeployment : 10:53:09 - Resource Microsoft.Compute/virtualMachineScaleSets 'Default' failed with message '{
  "status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "VMExtensionHandlerNonTransientError",
        "message": "Handler 'Microsoft.Azure.ServiceFabric.ServiceFabricNode' has reported failure for VM Extension
'Default_ServiceFabricNode' with terminal error code '1009' and error message: 'Enable failed for plugin (name:
Microsoft.Azure.ServiceFabric.ServiceFabricNode, version 1.0.0.33) with exception Command
C:\\Packages\\Plugins\\Microsoft.Azure.ServiceFabric.ServiceFabricNode\\1.0.0.33\\ServiceFabricExtensionHandler.exe of
Microsoft.Azure.ServiceFabric.ServiceFabricNode has exited with Exit code: -532462766'"
      }
    ]
  }
}'
At C:\Users\User\Downloads\template\deploy.ps1:104 char:5
+     New-AzureRmResourceGroupDeployment -ResourceGroupName $resourceGr ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [NewAzureRmResourceGroupDeployment], Exception
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet
1
I also got stuck with same upgrade service unreachable state. De-allocating and restarting the VM resolved my issue. see here stackoverflow.com/questions/44257426/…Mahbubur Rahman

1 Answers

3
votes

edit:

Make sure that you deploy your template using VM size D2 or better. You can scale down after it succeeds.

original:

Use RDP to connect to one of the nodes. Check the event viewer for more information. There's a SF section there.

Try restarting the SF service and/or machines.

(What did you do to get it into this state?)