Fork me on GitHub
#clojars
<
2021-11-11
>
steffan11:11:24

I could be doing something daft, but today I'm getting errors when trying to run cljdoc locally, indicating clojars is unreachable?? I've been happily running cljdoc locally recently, its just today its acting strangely.

INFO [2021-11-11 11:02:24,144] Tea-Time 1 - cljdoc.server.search.artifact-indexer Failed to download artifacts from Clojars
java.net.UnknownHostException: 

tcrawley12:11:51

Weird. Can you dig ? I can resolve it here

steffan12:11:22

It seems dig works:

❯ dig 

; <<>> DiG 9.16.1-Ubuntu <<>> 
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63141
;; flags: qr rd ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;clojars.org.                   IN      A

;; ANSWER SECTION:
.            0       IN      A       3.20.175.150
.            0       IN      A       3.143.41.59
.            0       IN      A       18.189.33.7

;; Query time: 40 msec
;; SERVER: 172.28.144.1#53(172.28.144.1)
;; WHEN: Thu Nov 11 12:42:32 GMT 2021
;; MSG SIZE  rcvd: 88

tcrawley12:11:35

Odd. Is it consistently failing in the cljdoc process or was it a one-time blip?

steffan13:11:45

Running the Docker image cljdoc/cljdoc is consistently failing today. I've rebooted a couple of times. I'm running WSL 2 on a Windows 10 machine. I've just tried dig from a bash prompt started with docker run --rm -it ubuntu:20.04 bash and that seems to be working fine, it gives me the same output as running from a terminal directly in WSL 2.

steffan13:11:43

...and now everything is working, seems there was some temporary issue. On running cljdoc/cljdoc I'm getting a benign error, but the server starts up and I'm able to proceed.

INFO [2021-11-11 13:16:35,042] Tea-Time 1 - cljdoc.server.search.artifact-indexer Failed to download artifacts from Clojars
clojure.lang.ExceptionInfo: Unexpected HTTP status from Clojars

tcrawley13:11:25

Hmm. Glad it is working now!

steffan13:11:24

Not sure if it was a blip or me being dumb, but at least I'm unstuck now! 😌