I am trying to deploy a console application to service fabric. I was able to successfully deploy and run the application in local service fabric cluster. But when I am trying with public service fabric cluster, I am seeing below warning in service fabric explorer and the application is not running.
Unhealthy event: SourceId='System.Hosting',
Property='CodePackageActivation:C:EntryPoint', HealthState='Warning',
ConsiderWarningAsError=false.There was an error during CodePackage
activation.The service host terminated with exit code: 3762504530
The most common explanation for code the runs locally but not in Azure is that you're targeting a .NET framework version that is not present on the VMs provisioned in a Service Fabric cluster. They currently provide .NET 4.5.1 out of the box, with .NET 4.5.2 getting added some time this month. Try retargeting your app to 4.5.1.
Update: as of February 2016, VMs provisioned for Service Fabric clusters come with .NET 4.5.2 by default.
Related
I am trying to deploy service fabric application from powershell. I am able to deploy with service fabric SDK. is it possible to deploy service fabric application from powershell using powershell scripts without having service fabric sdk installed?(Scenario: in a standalone service fabric cluster)
I haven't worked with standalone clusters, but based on my experience just working with a local dev cluster, yes, you need the SDK because it installs both the runtime (without a runtime, what cluster will the scripts connect to?) and the Service Fabric PowerShell module you'll be using (per the docs for the cmdlets).
I installed service fabric locally and set up five cluster node. I followed this tutorial and downloaded source code from here. It worked fine. Now I created one .net core application (docker enabled) API with visual studio 2019. I published image on docker hub (I ran image locally to confirm it is working fine.). Then I create service fabric project through visual studio and add container to it. I published on local cluster of five nodes. First one is already running. It is build and published successfully. But on service fabric explorer, it is showing me this error.
Unable to connect to service fabric cluster through visual studio for remote debugging
I have a service fabric cluster deployed using ARM template. I am using the same cluster certificate and client certificate to connect to cluster(for development purpose only). I am able to connect to the cluster using powershell. However, when I try to connect to the cluster using visual studio cloud explorer for remote debugging, I get below error in the output window in visual studio:
Cloud Explorer could not connect to cluster 'xxxxxxxx':
An authentication token could not be obtained. Refresh the node to sign in again.
I have tried to refresh the cloud explorer but it has no effect. Additionally, I tried to deploy the service fabric application and then try, however, it has the same error before and after deployment of service fabric application.
I'm trying to determine if it's possible to install a previous version of a Service Fabric application using the online Service Fabric Explorer as opposed to having to use a PowerShell script? In our case, the previous version of the application exists in the cluster and is visible in the list of application versions in the Explorer.
I appreciate any input.
This topic has been raised a few times around SO, short answer is no.
This answer give more details: Service fabric rollback to previous version from visual stuido or service fabric explorer
edit: I have updated this question with more detail
I'm trying to deploy an Docker compose to Service Fabric. This cluster is a custom setup using three vm's (Windows Server 2016 Datacenter with Containers) on Azure running the latest version (CodeVersion 6.0.219.9494).
I'm using VSTS with the 'Deploy docker-compose application to a Service Fabric cluster' task to deploy the docker compose file. VSTS uses a custom build server (Server 2016) on which Service Fabric SDK 2.7 is installed. I couldn't install 2.8 because the task in VSTS is not compatible, see https://github.com/Microsoft/vsts-tasks/issues/5505.
So far, so good. But when Service Fabric deploys the container I receive the following error (In Service Fabric Explorer): There was an error during download. Failed to download container image erwinstaal/dockerdemo. This image has been pushed to a public repo on Docker Hub. However, when I use the Docker images command on one of the nodes the image has been downloaded. Does anyone have a clue on what could be going on?