This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-02
Channels
- # announcements (1)
- # aws (5)
- # babashka (13)
- # beginners (202)
- # bristol-clojurians (3)
- # cider (16)
- # clojure (283)
- # clojure-dev (8)
- # clojure-finland (30)
- # clojure-italy (4)
- # clojure-nl (6)
- # clojure-spec (17)
- # clojure-survey (161)
- # clojure-sweden (7)
- # clojure-uk (62)
- # clojurescript (4)
- # core-async (31)
- # cursive (3)
- # datomic (7)
- # defnpodcast (1)
- # fulcro (8)
- # jobs (2)
- # lumo (2)
- # malli (2)
- # off-topic (24)
- # other-languages (1)
- # overtone (1)
- # re-frame (6)
- # remote-jobs (3)
- # shadow-cljs (6)
- # spacemacs (17)
- # tools-deps (20)
we had an issue where our latest Ions revision failed to deploy, and then so did all previously working revisions. CodeDeploy reports a ScriptTimedOut error:
[stdout]Received 000ip-xx-xxx-xxx-xxx login: /dev/fd/11: line 1: /sbin/plymouthd: No such file or directory(inspired by https://jacobobryant.com/post/2019/aws-battles-ep-1/ 😉 )
ha... I was just about to say, "hey, I saw that error last week!"
Sometimes I've seen errors from bad code I committed in the cloudwatch logs... but if your previously working deploys also fail, idk if cloudwatch would have anything useful
What's the Most recent event from codedeploy?
also is this solo or prod topology? I've seen other people in this channel say that sometimes solo deploys just get wonky and you have to terminate the ec2 instance