rubydoc.info icon indicating copy to clipboard operation
rubydoc.info copied to clipboard

Service unavailable (503)

Open sthyregod opened this issue 3 years ago • 16 comments

I've been running into a few 503 errors when browsing the site, specifically when trying to browse the documentation on the following link:

https://www.rubydoc.info/github/rails/activeresource

screenshot

sthyregod avatar Apr 27 '21 06:04 sthyregod

I also observed this yesterday afternoon (Apr 26).

@lsegal Did the hosting for rubydoc.info change recently?

whatisdot avatar Apr 27 '21 15:04 whatisdot

Also experiencing this with my own gem.

nateleavitt avatar Apr 27 '21 16:04 nateleavitt

There was an outage that seemed to be only affecting github projects. We investigated and it should now be resolved. Will be looking into how that happened. Thanks for reporting!

lsegal avatar Apr 27 '21 17:04 lsegal

I am having this same issue please fix it

Crusader500 avatar May 09 '21 13:05 Crusader500

Still with error 😢

pedrofurtado avatar Jul 05 '21 19:07 pedrofurtado

We ran a quick restart on the service and it should be working now. We had an out of memory error which is pretty abnormal and will be investigating what caused it so we can fix and avoid this in the future.

Thanks for reporting!

lsegal avatar Jul 05 '21 19:07 lsegal

@lsegal Looks like we're still seeing some disruption: https://rubydoc.info/gems/yard/File

whatisdot avatar Jul 16 '21 20:07 whatisdot

Thanks again! Made some adjustments just now to the memory usage so we can start working out how to better improve service.

Looks like people are catching this before our own uptime notifications are, so that's something we will also adjust.

lsegal avatar Jul 16 '21 20:07 lsegal

(PS: service is now functioning again)

lsegal avatar Jul 16 '21 20:07 lsegal

@lsegal down again, right now I'm unable to view the docs for StdLib StringIO

SampsonCrowley avatar Aug 13 '21 02:08 SampsonCrowley

@lsegal This seems to come back up with the same problem quite frequently. maybe it is time for a more robust resolution? (not that I have any suggestions without knowing what the original resolutions have been, every issue just says it's "being worked on", or "been fixed")

Very much appreciate the rubydocs service and would be willing to contribute to solving the solution in a more permanent manner if possible

https://github.com/docmeta/rubydoc.info/issues/53 https://github.com/docmeta/rubydoc.info/issues/109 https://github.com/docmeta/rubydoc.info/issues/122 (mentioned, not main issue) https://github.com/docmeta/rubydoc.info/issues/124 https://github.com/docmeta/rubydoc.info/issues/134 https://github.com/docmeta/rubydoc.info/issues/147 https://github.com/docmeta/rubydoc.info/issues/158

SampsonCrowley avatar Aug 13 '21 02:08 SampsonCrowley

I share @SampsonCrowley's thoughts. The rubydocs project is a tremendous help for my team and we're willing to help contribute to a solution for this issue.

whatisdot avatar Aug 17 '21 16:08 whatisdot

Getting this error too on the RGL gem.

Duartemartins avatar Sep 17 '21 13:09 Duartemartins

I'm still running into errors like this as well.

iloveitaly avatar Oct 15 '21 13:10 iloveitaly

Its still happening quite often, more 503 then not. If you need help with hosting or the API connection, I'm glad if I can help.

If its an issue with a rate limit by github, which https://github.com/docmeta/rubydoc.info/issues/156#issuecomment-827774478 suggests, maybe they're willing to up the qouta for an open source project that has such a huge audience/impact?

jk779 avatar Oct 26 '21 18:10 jk779

503 have become less frequent, but apparently, docs (most notably generated off GitHub main) are often garbled. I mention it here because it could be a memory issues as mentioned above.

@lsegal YARD is tremendously useful for the community! That said, maybe Ruby Central would be willing to host (or sponsor the hosting) – having more CPU and mem resources for rubydoc.info might help.

svoop avatar Apr 30 '23 10:04 svoop