无法发布到另一台计算机上的服务结构本地群集 [英] Cant publish to service fabric local cluster on another machine
问题描述
我今天在我的开发机器上安装了本地集群以进行游戏.但是，上传某些来宾exe时，结构崩溃.我什至只加载了简单的旧notepad.exe，但是同样崩溃了. 作为进一步的测试，我将notepad.exe推送到公共团体中，并且运行良好. 这篇文章给出了类似的错误，根据评论，我怀疑这是Windows 7问题.
I installed a local cluster to my development machine today to have a play. However when uploading some guest exe's the fabric crashes. I even tested just loading simple old notepad.exe, but alas the same crash. As a further test I pushed the notepad.exe to the public party cluster and it ran just fine. This post gives a similar error, and as per the comments I suspect it is a Windows 7 issue.
因此，下一个想法是在新的Windows服务器VM上安装本地群集，然后尝试发布到该本地群集.但是我在那里也碰到了另一堵墙.我可以连接到远程"群集的Web管理界面，并且可以看到所有Fabric进程在端口19000上运行和侦听，但是VS 2015在发布期间拒绝连接. 我禁用了防火墙，认为这是问题所在，并"ping"了各个端口以进行验证.一些响应(例如19080)但没有响应.
So next idea was to install a local cluster on a new Windows server VM, and attempt to publish to that. But I've hit another wall there too. I can connect to the "remote" cluster's web management interface, and I can see all of the Fabric processes running and listening on port 19000, but VS 2015 refuses to connect during a publish. I disabled the firewall thinking that was the issue, and have "pinged" various ports to verify. Some respond (such as 19080) but not 19000.
想法?
更新:在远程计算机上运行powershell connect命令有效.
Update: Running powershell connect command on the remote machine works.
Update2::我已经将本地群集"安装到了其他3台计算机上，并且它们都做完全相同的事情
Update2: I've installed the "local cluster" onto 3 other machines and all do exactly the same thing
Update3:使用netsh命令在远程计算机上创建转发端口，以将其从18090路由到19000.现在，我可以通过powershell从本地计算机连接到远程计算机的本地群集. (我还注意到，如果远程计算机上的用户名/密码不在同一域中，则用户名/密码必须相同) Visual Studio现在也可以连接，但是powershell脚本会在中间出现错误，这是输出.
Update3: Created a port forward on the remote machine using the netsh command to route from 18090 to 19000. Now I can connect via powershell from my local machine to the remote machine's local cluster. (I also noticed that the username/password on the remote machine needs to be the same if they are not on the same domain) Visual Studio can also now connect, but the powershell script Errors mid way, here is the output.
*>正在将应用程序复制到图像存储中...
复制应用程序包成功
正在注册应用程序类型...
Register-ServiceFabricApplicationType:应用程序清单文件
在商店中找不到"FabricApp2Type \ ApplicationManifest.xml".
在C:\ Program Files \ Microsoft SDKs \ Service Fabric \ Tools \ PSModule \ ServiceFabricS
DK \ Publish-NewServiceFabricApplication.ps1:244 char:9
+ Register-ServiceFabricApplicationType -ApplicationPathInImageStore
$ appl ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+ CategoryInfo:ResourceUnavailable:(Microsoft.Servi ... usterCon
nection:ClusterConnection)[Register-ServiceFabricApplicationType]，FileNo
tFoundException
+ FullyQualifiedErrorId:RegisterApplicationTypeErrorId，Microsoft.Service
Fabric.Powershell.RegisterApplicationType
*>Copying application to image store...
Copy application package succeeded
Registering application type...
Register-ServiceFabricApplicationType : The Application Manifest file
'FabricApp2Type\ApplicationManifest.xml' is not found in the store.
At C:\Program Files\Microsoft SDKs\Service Fabric\Tools\PSModule\ServiceFabricS
DK\Publish-NewServiceFabricApplication.ps1:244 char:9
+ Register-ServiceFabricApplicationType -ApplicationPathInImageStore
$appl ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+ CategoryInfo : ResourceUnavailable: (Microsoft.Servi...usterCon
nection:ClusterConnection) [Register-ServiceFabricApplicationType], FileNo
tFoundException
+ FullyQualifiedErrorId : RegisterApplicationTypeErrorId,Microsoft.Service
Fabric.Powershell.RegisterApplicationType
完成执行脚本'Deploy-FabricApplication.ps1'.*
Finished executing script 'Deploy-FabricApplication.ps1'.*
由于Windows 7机器无法使用，因此我现在不得不在远程计算机上安装Visual Studio的本地副本，并使用该副本来运行测试.
I've now resorted to installing a local copy of visual studio on the remote machine and using that to run my tests since my Windows 7 machine wont.
尽管我现在的工作是解决Win 7错误，但我可以看到在其他计算机上具有本地群集"进行开发和调试的好处.这比在Azure中建立开发集群要容易得多，并且比推送到公共Party集群要安全得多.我希望SF团队中已经有人在允许VS进行远程部署和调试.
Whilst my efforts to now are to get around the Win 7 bug, I can see benefit in having "local clusters" on other machines for development and debugging. Is a lot easier than having to stand up a dev cluster in Azure, and more secure than pushing to the public Party cluster. I hope someone in the SF team is already working on allowing VS to remotely deploy and debug.
如果到目前为止，有人对如何解决这些问题有建议，请发表.我也很高兴测试想法.
If anyone has suggestions as to how to remedy the issues so far, please post. I'm happy test ideas too.
推荐答案
我在DevTest实验室中托管了几个小型的一机开发集群，它们运行良好.
I have several small one machine development clusters hosted in DevTest labs, and they work well.
我认为主要区别在于，我使用的是Service Fabric Standalone安装程序，而不是SDK.我试图使SDK版本正常工作，并获得与您发现的结果相同的结果.
I think the key difference is that I am using the Service Fabric Standalone installer as opposed to the SDK. I tried to get the SDK version to work, with the same results you found.
这些是我在内部分发的说明，用于在DevTest实验室中创建一台计算机微型集群".
These are the instructions I distribute internally to create a one machine 'micro cluster' in DevTest lab.
- 从Azure站点下载Service Fabric独立程序包
然后解压缩 https://azure. microsoft.com/en-us/documentation/articles/service-fabric-cluster-creation-for-windows-server/ - 编辑文件ClusterConfig.Unsecure.DevCluster
- 使用本地计算机的IP地址或主机名ex-"iPAddress":"10.0.0.5"更新3个ip地址条目
- 使用PowerShell命令创建群集(使用管理员).\ CreateServiceFabricCluster.ps1 -ClusterConfigFilePath
.\ ClusterConfig.Unsecure.DevCluster.json -AcceptEULA - 通过打开浏览器来验证集群创建是否完成-
- 打开本地计算机上的发布端口(如果使用普通的ARM计算机而不是dev-test，则打开端点防火墙)
- Download the Service Fabric standalone package from the Azure site
and Unzip https://azure.microsoft.com/en-us/documentation/articles/service-fabric-cluster-creation-for-windows-server/ - Edit File ClusterConfig.Unsecure.DevCluster
- Update the 3 ip address entries with the IP address or host name of the local machine ex - "iPAddress": "10.0.0.5"
- Create the Cluster with PowerShell Command (use admin) .\CreateServiceFabricCluster.ps1 -ClusterConfigFilePath
.\ClusterConfig.Unsecure.DevCluster.json -AcceptEULA - Verify Cluster creation complete by opening browser - http://hostname:19080
- Open Publish port on local machine (and endpoint firewall if using normal ARM machine instead of dev-test)
这篇关于无法发布到另一台计算机上的服务结构本地群集的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
