This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-04
Channels
- # beginners (31)
- # boot (24)
- # braid-chat (17)
- # cider (4)
- # cljs-dev (33)
- # cljsrn (5)
- # clojure (79)
- # clojure-austin (1)
- # clojure-poland (229)
- # clojure-russia (51)
- # clojure-uk (3)
- # clojurescript (68)
- # core-async (1)
- # core-matrix (1)
- # datomic (18)
- # editors (24)
- # emacs (7)
- # hoplon (118)
- # jobs (1)
- # jobs-discuss (1)
- # juxt (7)
- # off-topic (16)
- # om (121)
- # onyx (3)
- # parinfer (224)
- # protorepl (3)
- # re-frame (29)
- # reagent (1)
- # rethinkdb (2)
- # ring (1)
- # spacemacs (2)
- # untangled (182)
@bridget. im able to stream logs from my ec2 instance.Unfortunately i did a couple things at the same time. So its unclear which solved the issue. I’ll probably wipe the slate tomorrow and be slightly more systematic. But in case work sweeps me away and i dont get back to investigating it properly, here is what might correct it: add
[ssh_connection]
control_path = %(directory)s/%%h-%%p-%%r
to ansible config. There seems to be an issue with long socket names: https://stackoverflow.com/questions/35595468/ansible-connection-to-aws-host-fails-with-unknown-ssh-error
Run provisioning script with sudo, because you my user didnt have the sufficient permissions. It seems reasonable to assume permissions could be adjusted to allow for it to work.
more on someone else with similar issues here: https://www.mail-archive.com/[email protected]/msg09336.htmlThanks for the update @drewverlee!
Thank you @drewverlee!