[ensembl-dev] REST API Help - Service Unavailable from IP

[Z. Dickson]

Hello,

Thanks for getting back to me.
We are still seeing the same problems, but are beginning to believe that
the issue lies with the architecture on our end, as we can get the client
to work on the head of our cluster, but not from within the cluster.
While we have not been able to solve the problem, we have found a few
workarounds.
Any feedback from the infrastructure team would be appreciated.

It is good to hear that the issue is not an explicit ban.

Thank you,
Zachery Dickson


On Fri, Apr 12, 2019 at 9:28 AM Andy Yates <ayates at ebi.ac.uk> wrote:

> Dear Zachery,
>
> I'm sorry that you've not had a response to your question yet. I've passed
> your query onto our web and infrastructure teams. As far as I am aware we
> have not explicitly IP banned yourself or anywhere from McMaster
> University.
>
> Are you still seeing the same problems?
>
> Many thanks
>
> Andy
>
> ------------
> Andrew Yates - Genomics Technology Infrastructure Team Leader
> The European Bioinformatics Institute (EMBL-EBI)
> Wellcome Genome Campus
> Hinxton, Cambridge
> CB10 1SD, United Kingdom
> Tel: +44-(0)1223-492538
> Fax: +44-(0)1223-494468
> Skype: andy.yates.ebi
> http://www.ebi.ac.uk/
> http://www.ensembl.org/
>
> > On 5 Apr 2019, at 17:36, Z. Dickson <dicksoz at mcmaster.ca> wrote:
> >
> > Hello,
> >
> > I recently wrote a small client for interacting with Ensembl's REST
> server, which made use of the POST lookup endpoint to map gene id's to
> transcript and protein id's.
> > I had believed it followed all the guildlines for request size, and
> request rate, however during a run of the script, the server began to
> intermittently respond with either "503 -Service Unavailable" or "599 -
> Internal Exception - timeout waiting for socket", which could not be
> resolved with a sleep-and-retry. Eventually this progressed to the current
> state, where this is the only response we receive, It is not even possible
> to view the endpoint documentation through a web-browser, seeing only the
> 503 error.
> > This only affects the IP of our cluster, which unfortunately includes
> the most used machines in our department. Machines with separate IP's can
> successfully contact the server.
> >
> > From all appearances the IP of our cluster has been banned, but without
> error messages which would indicate as much. I am hoping to find out if
> this is indeed the case, and more importantly restore access to the REST
> server for the cluster.
> >
> > Please let me know what additional information would be required to help
> me (IP, code, etc.).
> >
> > Thank you in advance,
> > --
> > Zachery Dickson
> > Bioinformatics Master's Student
> > Department of Biology
> >
> > location: LSB 522
> >
> > _______________________________________________
> > Dev mailing list    Dev at ensembl.org
> > Posting guidelines and subscribe/unsubscribe info:
> http://mail.ensembl.org/mailman/listinfo/dev_ensembl.org
> > Ensembl Blog: http://www.ensembl.info/
>
>
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info:
> http://mail.ensembl.org/mailman/listinfo/dev_ensembl.org
> Ensembl Blog: http://www.ensembl.info/
>


--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20190412/20f9c991/attachment.html>