dcos service log requires ssh credentials about dcos-core-cli HOT 13 CLOSED

I think this is related. I am doing dcos node ssh --leader --master-copy and it is asking me for a password. I can't find this password anywhere.

from dcos-core-cli.

If you are using Vagrant, the --user=vagrant switch works. Note it still asks for a password, I entered the password as vagrant and I got in.

from dcos-core-cli.

@fpapleux I am trying to use dcos node ssh to get into Redis as per the tutorial but I'm having the same issue as you. Were you able to find a solution?

from dcos-core-cli.

Why isn’t this mentioned as part of DCOS 101 tutorial? Or better yet, add vagrant as a user option to the ssh command:

dcos node ssh --master-proxy --mesos-id=$(dcos task redis --json | jq -r '.[] | .slave_id’) --user=vagrant

Knowing the correct combination of username/password for vagrant is not exactly common knowledge.

from dcos-core-cli.

I suspect that's because we're using IPs and jumping hosts. We need to make it obvious how to do that config!

from dcos-core-cli.

Hi @r0c. What manual are you referring to and where are you running the cli from? Is the master node publicly from where the cli is running from? You probably need to add your aws key to your ssh-agent.

from dcos-core-cli.

@tamarrow and @r0c I think the other possible issue is that core in ssh [email protected] may not be a valid user. It should be possible to set the right user with the --ssh-config-file flag.

We should add features to DC/OS to make it possible to expose the journald logs without having to ssh. cc. @pyronicide and @malnick

from dcos-core-cli.

I figure it would be easiest to add a new setting called user to the config file, then anytime you ssh via node ssh or look at marathon logs, it would use that as default.

from dcos-core-cli.

@ddispaltro what do you think about configuring the SSH options instead?

from dcos-core-cli.

You mean in your ~/.ssh/config, if so I am good with that. The tool doesn't seem to respect it though.

from dcos-core-cli.

@fpapleux by default, dcos ssh utilize default user 'core'. For vagrant local installation of dcos, it's 'vagrant'.

dcos node ssh --master-proxy --user=vagrant --mesos-id=$(dcos task redis --json | jq -r '.[] | .slave_id')

from dcos-core-cli.

Hello @ALL
You are all right on how to change the user when SSHing into one node's name/ip.
But ,what can I do in the following case when there is a pswd for the user core requested:
'dcos service log marathon'?
I did not find any 'workaround' to change the user with, e.g., '--user=vagrant'.
Is there any solution to change the user from 'core' to 'vagrant' when executing above mentioned dcos service log command?
Your response will be highly appreciated.
Regards,
Roger

from dcos-core-cli.

I fixed this issue by going through https://docs.mesosphere.com/1.7/administration/sshcluster/

1. chmod 600 .pem (Grant permissions)
2. cp .pem ~/.ssh/.pem (Copy key to local ssh path)
3. ssh-add ~/.ssh/.pem
4. dcos node ssh --master-proxy --mesos-id=

Now it is not asking for a password. Hope this helps.

from dcos-core-cli.