This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-22
Channels
- # announcements (6)
- # babashka (8)
- # beginners (136)
- # cider (5)
- # cljs-dev (1)
- # cljsrn (1)
- # clojure (198)
- # clojure-argentina (4)
- # clojure-australia (1)
- # clojure-europe (25)
- # clojure-italy (4)
- # clojure-nl (5)
- # clojure-poland (1)
- # clojure-spec (4)
- # clojure-uk (4)
- # clojuredesign-podcast (4)
- # clojurescript (36)
- # conjure (11)
- # data-science (1)
- # datomic (6)
- # defnpodcast (1)
- # deps-new (5)
- # emacs (7)
- # events (1)
- # fulcro (10)
- # graalvm (9)
- # graalvm-mobile (10)
- # helix (9)
- # introduce-yourself (1)
- # jackdaw (1)
- # jobs-discuss (5)
- # kaocha (6)
- # lsp (10)
- # malli (11)
- # missionary (28)
- # off-topic (2)
- # pathom (24)
- # pedestal (7)
- # portal (1)
- # re-frame (12)
- # reagent (2)
- # reitit (1)
- # remote-jobs (1)
- # sci (7)
- # shadow-cljs (6)
- # sql (6)
- # tools-deps (10)
- # vim (9)
- # xtdb (19)
Hi!
I restarted my dev laptop this morning and the peer can’t connect to the transactor anymore. I get an ActiveMQ error Error communicating with HOST localhost on PORT 43304
. This says it’s a configuration problem: https://docs.datomic.com/on-prem/operation/deployment.html#peer-fails-to-connect
The configuration hasn’t changed in months, files didn’t move, rights didn’t change, and my laptop got restarted and updated many times since then. But all of a sudden it stopped working today.
So there’s def. something that changed and I don’t see it.
What could cause the peer to fail connecting to the transactor if configuration and access rights are not the issue?
Turns out the issue is not related to Datomic but was caused by the terminal process from which I was starting the transactor. The buggy state survived reboots.