Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server code: 500; Server is possibly experiencing traffic, trying again... #2

Open
mightyphil2000 opened this issue Feb 22, 2021 · 4 comments

Comments

@mightyphil2000
Copy link
Contributor

When I try to upload a GWAS summary data set I alway get this server code error:
Server code: 500; Server is possibly experiencing traffic, trying again...

I've been getting this message for the past 4 weeks. The server doesn't seem to be have been experiencing much traffic lately so the message doesn't seem to make sense.

@mvab
Copy link

mvab commented Apr 30, 2021

I can't get past this message too:

Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server error: 500
Failed to retrieve results from server. See error status message in the returned object and contact the developers if the problem persists.
Failed to uploaded metadata
Response [http://ieu-db-interface.epi.bris.ac.uk:8082/edit/add]
  Date: 2021-04-30 17:52
  Status: 500
  Content-Type: application/json
  Size: 37 B
{"message": "Internal Server Error"}

@mvab
Copy link

mvab commented Feb 18, 2022

@explodecomputer I haven't been able to get past this error at the x$api_metadata_upload() step. What does this error actually mean? Is possible to debug it somehow?

Using access token. For info on how this is used see logging_info()
 The googleAuthR package is using a cached token for ######.
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server code: 500; Server is possibly experiencing traffic, trying again...
Server error: 500
Failed to retrieve results from server. See error status message in the returned object and contact the developers if the problem persists.
Failed to uploaded metadata
Response [http://ieu-db-interface.epi.bris.ac.uk:8082/edit/add]
  Date: 2022-02-18 17:09
  Status: 500
  Content-Type: application/json
  Size: 37 B
{"message": "Internal Server Error"}

@mvab
Copy link

mvab commented Feb 23, 2022

Hi, I'm still trying to solve this issue: I've tested the upload process on (1) Mac with VPN (2) Mac on eduroam (3) university windows PC, but the error is the same. At the same time, another person tested the process using exactly the same code and it worked for them (so it is likely not a real issue with the server)

I think something might be wrong with my google auth credentials. I've tried deleting the ieugwasr_oauth folder and generating the access token again, but that didn't help.

I noticed that when I run x <- Dataset$new(filename=filename) it does not generate a igd_id as I suppose it should (it is NULL in x$), so this could perhaps be linked to the problem.
I tried setting the id manually (and also using the randomly generated testing id as in the example), but then I get another error:

Failed to uploaded metadata
Response [http://ieu-db-interface.epi.bris.ac.uk:8082/edit/add]
  Date: 2022-02-23 18:17
  Status: 400
  Content-Type: application/json
  Size: 70 B
{"message": "Could not add study: Identifier has already been taken"}

which does not make sense when using a random testing id. So perhaps this is still a part of the same bigger problem why I can't access/connect to the server.

I'm not sure what else to try! I just really want to upload some data 😀

@mightyphil2000
Copy link
Contributor Author

I've also been having the same problem lately. I get the same error when I try to release a GWAS dataset after upload. It was working for me a few weeks ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants