Microsoft Service Fabric Stateful Service will not start

4
votes

All of a sudden my local Service Fabric is unable to start Stateful services. I've tried to uninstall the SDK's, but with no luck. The same service run fine on the Azure cluster.

Even the quickstart service in visual studio won't start

Service Status: fabric:/testapp/Stateful1 is not ready, 1 partitions remaining.

Service Status: fabric:/testapp/Stateful1 is not ready, 1 partitions remaining.

Something is taking too long, the application is still not ready. Finished executing script 'Get-ServiceFabricApplicationStatus'. Time elapsed: 00:01:41.7659838

Error from Service Fabric Explorer: Error event: SourceId='System.FM', Property='State'. Partition is below target replica or instance count.

2
c#.netazureazure-service-fabricservice-fabric-stateful
What does your local publish profile and parameters look like? Depending on your routing you need to be careful about having a greater than 1 instance count and services on the same port. – jimpaine
<Parameters> <Parameter Name="Stateful1_PartitionCount" Value="1" /> <Parameter Name="Stateful1_MinReplicaSetSize" Value="1" /> <Parameter Name="Stateful1_TargetReplicaSetSize" Value="1" /> </Parameters> – Thomas B
Do you have any other apps in the cluster or non service fabric applications running in IIS on your machine on the same ports? It might also be worth resetting the cluster via the tray icon, this can sometimes help with inconsistences. – jimpaine
No other apps in the cluster or in iis. But I noticed that fabric:/System/FaultAnalysisService is in Error state – Thomas B

2 Answers

5
votes

If you are receiving errors about cluster itself and fabric:/System/FaultAnalysisService, please look at this thread, your issue might be related to lack of disk space.

Assuming you have local cluster setup with default values you can use PowerShell as well to get information about cluster health:

# connect to cluster
Connect-ServiceFabricCluster -ConnectionEndpoint "localhost:19000"
# import commandlets
Import-Module "$ENV:ProgramFiles\Microsoft SDKs\Service Fabric\Tools\PSModule\ServiceFabricSDK\ServiceFabricSDK.psm1"
# get cluster status 
Get-ServiceFabricClusterHealth

I'd recommend using PowerShell to interact with cluster.

-1
votes

Try to disable the symbol server for remote debuging in visual studio.

Options > Debugging > Symbols > Disable Microsoft Symbol servers

Had the same issue, it turned out that the symbol server returned a 404 when visual studio tried to get the symbols. That slowed down the whole application, so the script thought it failed.

ScreenShot