Azure / azure-iot-remote-monitoring

Azure IoT Remote Monitoring preconfigured solution
Other
249 stars 221 forks source link

hostname azurecloud is not available #421

Closed a-karnik closed 3 years ago

a-karnik commented 7 years ago

Hi,

azurecloud is not valid

I am using VS 2013. Trying to deploy the IoT solution to Azure Cloud. I ran below command

build.cmd cloud debug AzureCloud

It gives me below error.

hostname azurecloud is not available

I have attached screen shot. Can you please help?

Thanks

joyhui commented 7 years ago

It means the name "AzureCloud" is taken. You should give a unique string as your solution name, since it will be used as a DNS for your website. If the name is token by someone else, you have to give a different name.

Here is the command line: build.cmd cloud [debug | release] <deploymentname>

You can try: build.cmd cloud debug KarnikCloud

Guideline: https://github.com/xzsheng/azure-iot-remote-monitoring/blob/limliu/Docs/cloud-deployment.md

a-karnik commented 7 years ago

Thanks for the reply Hui. I will try that tonight.

Ashish Karnik

On Apr 26, 2017, at 1:36 AM, Hui Jiang notifications@github.com wrote:

It means the name "AzureCloud" is taken. You should give a unique string as your solution name, since it will be used as a DNS for your website. If the name is token by someone else, you have to give a different name.

Here is the command line: build.cmd cloud [debug | release]

You can try: build.cmd cloud debug KarnikCloud

Guideline: https://github.com/xzsheng/azure-iot-remote-monitoring/blob/limliu/Docs/cloud-deployment.md

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

a-karnik commented 7 years ago

Hui, I went ahead and now got this error...

unable to create unique name for resource karnikcloud for url azure-devices.net Error comes from line 293 in DeploymentLib.ps1.

Can you please help?

Thanks Ashish

zhang-hua commented 7 years ago

@a-karnik, the hostname 'karnikcloud.azure-devices.net' is used by the IoTHub resource karnikcloud. Looks like it has already been taken by someone else. Since these resources are globally unique, please add some random numbers (e.g f3a6) or dates (e.g. 427) after the name so that it has not possible conflicts.

a-karnik commented 7 years ago

Thanks Zhang-hua. I tried changing to KarnikCloud14141 and KarnikCloudReallyLongName but get same exception. I am sorry; I am new to Powershell and Azure world. Can you please help?

Thanks Ashish

a-karnik commented 7 years ago

Zhang-hua, FYI, When I log in my Azure Portal account, I see both under "All Resource". Does it mean that the deployment was successful?

Thanks Ashish

zhang-hua commented 7 years ago

@a-karnik , all of the Azure resources of remote monitoring solution will be deployed into one resource group with the same name. If you can see there are 11 resources in that resource group, then it means you have succeeded. And also you can get status of the deployment in the resource group overview page on Azure portal. And if you want to remove the deployed solution, just delete the resource group so that Azure Resource Manager will delete everything that you just deployed.

zhang-hua commented 7 years ago

@a-karnik , please also ping the DNS name locally on your machine to see if it is resolvable. Some ISP or your network service provider may reply the DNS name resolution request which misled the PowerShell script. you can verify DNS availability by PowerShell command

[Net.Dns]::GetHostEntry("KarnikCloud14141.azure-devices.net")

please also refer to another issue thread 406.

a-karnik commented 7 years ago

Thanks Zhang-Hua, please check the attached snap shot of results when I ran above command from PowerShell. Does this help?

Thanks Ashish

dnspowershell screenshot

zhang-hua commented 7 years ago

@a-karnik , I pushed a PR to fix this local DNS resolution issue at 422. It has passed in my tests. please try it and tell us your feedback. Thanks!

+@joyhui

a-karnik commented 7 years ago

Thanks Zhang-Hua, I did copy new files in my folder and re ran below command.

build.cmd cloud debug karnikClud2

I got attached exception - "The Term 'Resolve-DnsName' is not recognized as the name of cmdlet....".

Can you please take a look?

Thanks Ashish Karnik resolve-dnsname

networkfusion commented 7 years ago

This fix would only work on windows 8 and above (I guess you are using windows 7...) you could try the fix using a later OS or try the change using a command such as:[System.Net.Dns]::GetHostAddresses("www.google.com")

zhang-hua commented 7 years ago

@a-karnik , just as @networkfusion said, this command works only for Windows Server 2012 R2 and Windows 8.1. It is a DNS client tool to support more options (e.g. DNS server) than [System.Net.Dns]::GetHostAddresses(). Here is a document link FYI. What's your OS version and Powershell version(use $PSVersionTable to get it)? please also try this command and let me know the output:

nslookup KarnikCloud14141.azure-devices.net 8.8.8.8
zhang-hua commented 7 years ago

@a-karnik , please have another try with the new branch fix_issue_421. I add some work around logic in the Powershell script to detect DNS issue you have. Hope this can help you! :-)

a-karnik commented 7 years ago

Thanks for your help Zhang-Hua. I downloaded new project and I think I went futher in deploying the project in my Azure Account; came across attached issue. Can you please take a look?

I need one more help from you. Can you please tell me how to debug this solution on my local box? Can I do it without deploying in Azure Cloud? Appreciate your help.

Thanks Ashish Karnik content-type header must be modified

zhang-hua commented 7 years ago

@a-karnik What's your OS version and Powershell version(use $PSVersionTable to get it)? please also try this command and let me know the output。

a-karnik commented 7 years ago

Hi Zhang Hua, please check the PS Version. I am using Windows 7.

Thanks Ashish

On Wed, May 17, 2017 at 1:21 AM, Zhang Hua notifications@github.com wrote:

@a-karnik https://github.com/a-karnik What's your OS version and Powershell version(use $PSVersionTable to get it)? please also try this command and let me know the output。

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-iot-remote-monitoring/issues/421#issuecomment-301996919, or mute the thread https://github.com/notifications/unsubscribe-auth/AHy9yo0P6zv2wdUQIcG2yGWSoBDZJFOcks5r6pHNgaJpZM4NITf8 .

v-limliu commented 7 years ago

@a-karnik
what the powershell version you use, you can use this command "$PSVersionTable" to see that image

a-karnik commented 7 years ago

Hi all, I was able to deploy the solution with windows 10. Thank you all for you help; I really appreciate it.

Thanks Ashish Karnik

On Wed, May 17, 2017 at 9:41 PM, v-limliu notifications@github.com wrote:

@a-karnik https://github.com/a-karnik what the powershell version you use, you can use this command "$PSVersionTable" to see that [image: image] https://cloud.githubusercontent.com/assets/26808087/26184243/41bfa056-3bb6-11e7-8d08-b7d4798773d9.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-iot-remote-monitoring/issues/421#issuecomment-302285007, or mute the thread https://github.com/notifications/unsubscribe-auth/AHy9yobY32vPaecjffkTioVwoaNsct9Zks5r66_xgaJpZM4NITf8 .

zhang-hua commented 7 years ago

@a-karnik great news! So are you using the branch fix_issue_421 which is targetting DNS problem? or you are using master branch without any problem?

a-karnik commented 7 years ago

His Zhang, we used master branch and that worked fine for us.

Thanks Ashish

On May 22, 2017, at 12:31 AM, Zhang Hua notifications@github.com wrote:

@a-karnik great news! So are you using the branch fix_issue_421 which aims to target DNS problem? or you are using master branch without any problem?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

ankitscribbles commented 3 years ago

Note: As of December 10th 2020, Remote Monitoring solution accelerator is no longer supported. All supporting repositories have been archived.