klaemo commented on pull request #182: URL: https://github.com/apache/couchdb-docker/pull/182#issuecomment-804739641
I tried to get it running the way @rkleine described. Definitely got much further than I did on my own :D Unfortunately clouseau crashes the instant I `curl http://localhost:5984`, though 🤔 ``` clouseau1_1 | 2021-03-23 08:59:14,788 clouseau.main [INFO] Clouseau running as [email protected] clouseau1_1 | 2021-03-23 08:59:14,796 scalang.ErlangNode [DEBUG] deliverMonitor Pid('[email protected],2,1,2) -> Pid('[email protected],3,1,2) (Reference('[email protected],WrappedArray(0, 0, 0),2)) clouseau1_1 | 2021-03-23 08:59:14,799 scalang.ErlangNode [DEBUG] deliverMonitor Pid('[email protected],2,1,2) -> Pid('[email protected],4,1,2) (Reference('[email protected],WrappedArray(1, 0, 0),2)) clouseau1_1 | 2021-03-23 08:59:14,801 scalang.ErlangNode [DEBUG] deliverMonitor Pid('[email protected],2,1,2) -> Pid('[email protected],5,1,2) (Reference('[email protected],WrappedArray(2, 0, 0),2)) clouseau1_1 | 2021-03-23 08:59:43,372 scalang.node.ErlangHandler [DEBUG] handler message HandshakeSucceeded('[email protected],[id: 0x0f3eed1a, /127.0.0.1:45801 => /127.0.0.1:36147]) clouseau1_1 | 2021-03-23 08:59:43,380 scalang.node.ErlangHandler [DEBUG] handler message MonitorMessage(Pid('couchdb@1,4876,0,2),'net_k,Reference('couchdb@1,Vector(80488, 1221066753, 1159136377),2)) clouseau1_1 | 2021-03-23 08:59:43,381 scalang.ErlangNode [DEBUG] monitor Pid('couchdb@1,4876,0,2) -> 'net_k (Reference('couchdb@1,Vector(80488, 1221066753, 1159136377),2)) clouseau1_1 | 2021-03-23 08:59:43,382 scalang.ErlangNode [DEBUG] pids List(Pid('[email protected],1,1,2), Pid('[email protected],2,1,2), Pid('[email protected],3,1,2), Pid('[email protected],5,1,2), Pid('[email protected],0,0,2), Pid('[email protected],4,1,2)) clouseau1_1 | 2021-03-23 08:59:43,382 scalang.ErlangNode [WARN] Try to monitor non-live process: Pid('couchdb@1,4876,0,2) -> 'net_k (Reference('couchdb@1,Vector(80488, 1221066753, 1159136377),2)) clouseau1_1 | 2021-03-23 08:59:43,382 scalang.ErlangNode [DEBUG] handling monitor exit for Monitor(Pid('couchdb@1,4876,0,2),'net_k,Reference('couchdb@1,Vector(80488, 1221066753, 1159136377),2)) clouseau1_1 | 2021-03-23 08:59:43,383 scalang.ErlangNode [DEBUG] node scalang.ErlangNode@2e775cbc sending MonitorExitMessage('net_k,Pid('couchdb@1,4876,0,2),Reference('couchdb@1,Vector(80488, 1221066753, 1159136377),2),'noproc) clouseau1_1 | 2021-03-23 08:59:43,385 scalang.epmd.EpmdHandler [DEBUG] Oh snap channel closed. clouseau1_1 | 2021-03-23 08:59:43,385 scalang.epmd.EpmdHandler [DEBUG] Oh snap channel closed. clouseau1_1 | 2021-03-23 08:59:43,387 scalang.node.ErlangHandler [DEBUG] handler message RegSend(Pid('couchdb@1,4876,0,2),'net_k,('$gen_,(Pid('couchdb@1,4876,0,2),Reference('couchdb@1,Vector(80488, 1221066753, 1159136377),2)),('is_a,'couchdb@1))) clouseau1_1 | 2021-03-23 08:59:43,388 scalang.node.ErlangHandler [ERROR] error caught in erlang handler '[email protected] [...] java stacktrace clouseau1_1 | 2021-03-23 08:59:43,389 scalang.node.ErlangHandler [INFO] channel disconnected org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext@3f55b189 [id: 0x0f3eed1a, /127.0.0.1:45801 :> /127.0.0.1:36147] DISCONNECTED. peer: '[email protected] ``` I'm not sure what's going on. It looks like it can indeed reach `epmd`, but then it exits? CouchDB is running fine in its container and I can successfully reach couch on localhost from within the `clouseau` container: ``` [info] 2021-03-23T08:50:58.630473Z [email protected] <0.11.0> -------- Application couch started on node '[email protected]' [...] [notice] 2021-03-23T08:54:50.455952Z [email protected] <0.2199.0> a6c58336d7 finish_cluster: ok [...] [notice] 2021-03-23T08:55:53.487534Z [email protected] <0.3014.0> 6488627f8b localhost:5984 172.24.0.1 undefined GET / 200 ok 84 ``` Any ideas? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
