@Doron_Raz Sounds like this may be a transient error in setting up resources on Azure. A few things to check
Did all of the resources deploy successfully? You'll be able to see this by looking at the resource group in the Azure portal and looking at the "Deployments" sub header in the resource group blade.
Is the Network Security Group for Kibana set up correctly? An NSG should be attached to allow TCP traffic on port 22 (to allow you to ssh into the machine) and port 5601
When you ssh into the Kibana machine, is the Kibana service running? You can ssh into Kibana using its public IP address or DNS name
ssh <admin>@<dnsname>.<region>.cloudapp.azure.com
where admin is the admin username that you chose in step 1 of the portal. You'll need the password or ssh key that you specified for the admin in step 1 of the portal.
You can check the status of the service with
sudo service kibana status
If the service is not running, you can start it with
sudo service kibana start
If the kibana service does not start, you can check the kibana logs with
cat /var/log/kibana.log
There may be some useful information in the log that can help diagnose the issue.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.