Hi Guys, We don't provision SSH key on Azure. You need to use password authentification with username scalr and temporary password that is available on Server extended information page under "Scalr properties" section and called: azure.admin-pass .
I would recommend you to use Orchestration engine to set and maintain authorized keys. In future versions, we will add SSH key management for Azure, but right now it's a low priority task due to a very low customer demand. Regards, Igor On 16 February 2016 at 11:28, KikoV Gimeno <[email protected]> wrote: > Hello, > > I made a script to change the default password for scalr user. So I could > login and see what was happening inside the box. > No ubuntu user was created, just "scalr". > > In the scalarizr_debug.log file, I could see the following: > --- > > 2016-02-15 23:24:49,874+00:00 - DEBUG - scalarizr.messaging.p2p.consumer - > Decoding message: { > > "body": { > > "server_id": "bd149211-678e-4c18-89f3-d4fc31ec0b13", > > "server_index": "1", > > "farm_role_id": "31", > > "handlers": [ > > "base" > > ], > > "event_id": "1a779868-ea03-46fc-a443-7f31778e50cc", > > "farm_role_alias": "KubMaster", > > "local_ip": "172.18.0.8", > > "cloud_location": "westeurope", > > "ssh_pub_key": "", > > --- > > I don't know if it's usual or not, but it looks like the scalr server is not > sending the ssh_pub_key for that box. > > > By the way, SSH Launcher is working fine in Safari for AWS and GCE once you > follow the instruction on how to give file perms to the java applet. I find > it quite useful and comfy. > > > Any other clue you can think of? > > > Thanks you for your time! > > > BR, > > > El martes, 16 de febrero de 2016, 12:41:02 (UTC-5), Jay Farschman escribió: >> >> BR, >> >> With ubuntu, I think you need to look in /home/ubuntu/.ssh/authorized_keys >> for the FARM-7--7c72f829.pem. >> >> Also, I forget which browser, but one of my OS X (Mac) browsers does not >> work with the SSH Launcher. I think it's Firefox. >> >> Have you tried connecting from the CLI? >> >> ssh -i /Users/kikov/.ssh/scalr-ssh-keys/FARM-7--7c72f829.pem -o >> UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no >> -p 22 [email protected] >> >> The Launcher is cool, but I like to use ssh-add to connect all my farm >> keys: >> >> ssh-add -K FARM-7--7c72f829.pem >> >> On Wednesday, February 10, 2016 at 5:41:02 PM UTC-7, KikoV Gimeno wrote: >>> >>> Hello, >>> >>> I've been debugging with an script to look into the box. >>> --- the script --- >>> #!/bin/bash >>> >>> >>> echo "Users===========================" >>> ls -la /home/ >>> >>> echo "Home of Scalr user==============" >>> ls -la /home/scalr/ >>> >>> echo "Content of /home/scalr/.ssh=====" >>> ls -la /home/scalr/.ssh/ >>> >>> echo "Content of /root================" >>> ls -la /root >>> >>> echo "Content of /root.ssh============" >>> ls -la /root/.ssh >>> >>> --- >>> >>> --- this is the output of the script --- >>> Users=========================== >>> total 12 >>> drwxr-xr-x 3 root root 4096 Feb 7 14:00 . >>> drwxr-xr-x 22 root root 4096 Feb 7 14:00 .. >>> drwxr-xr-x 3 scalr scalr 4096 Feb 7 14:00 scalr >>> Home of Scalr user============== >>> total 24 >>> drwxr-xr-x 3 scalr scalr 4096 Feb 7 14:00 . >>> drwxr-xr-x 3 root root 4096 Feb 7 14:00 .. >>> -rw-r--r-- 1 scalr scalr 220 Apr 9 2014 .bash_logout >>> -rw-r--r-- 1 scalr scalr 3637 Apr 9 2014 .bashrc >>> -rw-r--r-- 1 scalr scalr 675 Apr 9 2014 .profile >>> drwx------ 2 scalr scalr 4096 Feb 7 14:00 .ssh >>> Content of /home/scalr/.ssh===== >>> total 8 >>> drwx------ 2 scalr scalr 4096 Feb 7 14:00 . >>> drwxr-xr-x 3 scalr scalr 4096 Feb 7 14:00 .. >>> -rw------- 1 scalr scalr 0 Feb 7 14:00 authorized_keys >>> Content of /root================ >>> total 20 >>> drwx------ 3 root root 4096 Feb 7 14:00 . >>> drwxr-xr-x 22 root root 4096 Feb 7 14:00 .. >>> -rw-r--r-- 1 root root 3106 Feb 20 2014 .bashrc >>> -rw-r--r-- 1 root root 140 Feb 20 2014 .profile >>> drwx------ 2 root root 4096 Feb 7 14:00 .ssh >>> Content of /root.ssh============ >>> total 8 >>> drwx------ 2 root root 4096 Feb 7 14:00 . >>> drwx------ 3 root root 4096 Feb 7 14:00 .. >>> -rw------- 1 root root 0 Feb 7 14:00 authorized_keys >>> ----- >>> >>> Both authorized_keys for scalr and root users are empty. >>> >>> BR, >>> >>> El miércoles, 10 de febrero de 2016, 18:45:26 (UTC-5), KikoV Gimeno >>> escribió: >>>> >>>> Hello community, >>>> >>>> I'm trying to launch Azure VM instances (Ubuntu 1410). >>>> Instances got launched, but ssh keys seem not to be populated into the >>>> server, so I can't login into them. I can see the instances in Azure >>>> console. >>>> >>>> When I use the SSH Launcher, it opens the console and it asks for the >>>> password. >>>> >>>> The console shows the following command: >>>> --- >>>> >>>> /usr/bin/ssh -i /Users/kikov/.ssh/scalr-ssh-keys/FARM-7--7c72f829.pem -o >>>> UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no >>>> -p 22 [email protected] >>>> >>>> -- >>>> >>>> The file exists and it looks good: >>>> >>>> -rw-------@ 1 kikov staff 668 7 feb 09:10 >>>> /Users/kikov/.ssh/scalr-ssh-keys/FARM-7--7c72f829.pem >>>> >>>> >>>> (Scalr 5.11.9) >>>> >>>> Am I missing something? >>>> >>>> Thanks you, >>>> >>>> BR, >>>> >>>> >>>> > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
