Clojurians Log v2

The site seems to be down. I'm working on it now. The repo is still up at http://repo.clojars.org.

I get a 504 Gateway Error...

Should be back up now.

I'll try a release (success).

This is the second time an instance has become unresponsive in the last two days. I need to dig in to it.

Glad it is working now!

I didn't notice any issues downloading fwiw.

When it was down I got this error when releasing:

Failed to deploy artifacts: Could not transfer artifact clojure.java-time:clojure.java-time:jar:1.4.3 from/to clojars (): transfer failed for 

Yes, that part is more stable, thankfully. It is a Fastly CDN backed by S3. The server isn't involved in serving from the repository itself.

That's what you got when it was down, or you got that since I started a new instance?

That's what I got when it was down.

Ah, gotcha. Deploys also go through http://repo.clojars.org, but fastly just sends that to http://clojars.org/repo/. So if the server is down, you can't deploy.

Hopefully I'm making sense :)

ah thanks.

Hopefully I gave you all the useful information I had 🙂

Thanks! When this happens, the network in/out on the instance drops to zero, and I can't ssh in. Last CPU metric I see is ~66%.

Eeep

Is it the same instance that has become unresponsive twice? Could be the case of a "decaying" machine

No, my only recourse when it is unresponsive is to kill it and start a new one (this is on EC2)

This happened to me on EC2 quite frequently as well (over a very large fleet of instances). But two different instances in a short span is probably not it.

Not being able to SSH in could be caused by a file handles leak.

Another detail I missed, I searched for a status page and found https://status.clojars.org/ which was blocked due to a "privacy error" in Chrome. It still does for me. > http://status.clojars.org normally uses encryption to protect your information. When Chrome tried to connect to http://status.clojars.org this time, the website sent back unusual and incorrect credentials.

Re: status - https://clojars.statuspage.io/ is the correct page. I should remove the http://status.clojars.org cname, as statuspage doesn't give me the option to use certificate with the correct name.

> Not being able to SSH in could be caused by a file handles leak That's a good point, I should look at that.

> I should remove the http://status.clojars.org cname, as statuspage doesn't give me the option to use certificate with the correct name. Thanks. It's my top hit on duckduckgo for "Clojars status page".

https://clojars.statuspage.io/ isn't in the first page of results for some reason.