-
Notifications
You must be signed in to change notification settings - Fork 52
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
'Remote end closed connection without response' and other issues #206
Comments
We are also having this problem, which I think is supposed to be a problem with the EGA server. |
It is not a new problem and I was able to download only when they gave an Aspera box to me, |
Same here. It is also related to this issue: #192, which has been open since February. I've also sent an e-mail to the helpdesk and hope they can give us aspera access. |
So far, when I wrote to helpdesk, I got an email with the message: "This ticket has been untaken by ega-rt-support." without further explanation. I assume "untaken" means that they will not pursue this issue (?!). In any case, yes I would be happy if I could get an Aspera link or any response from the EGA that actually lets me download EGAD00001001991. I have already set up Aspera on the cluster here on my end in Japan. Thank you for the comments. |
Same problem here:
Any suggestions? is this a EGA server problem? is this a temporary issue? |
I feel if research data has been deposited into EGA-archive, there should be a practical and reasonable method of getting the data out of EGA-Archive. |
The server worked last week, but suddenly didn't work this week. |
Might be, but on my end no download worked since 3 weeks ago. Fragments of files and some specific individual files, yes. But no way to download an entire microbiome data set from Lifelines DEEP. |
For me it worked on Monday this week. I didn't try on Tuesday, but since Wednesday (yesterday) I wasn't able to download a single byte. It shows the progress bar as in the first message from @antonkratz and after a few minutes times out and tells me that the connection is broken. Definitely a EGA server bug. Please fix this! |
I am also having the same issue. download hangs at 0.00 and then breaks. I'll watch this thread to see if it gets resolved... |
The problem still seems to be unresolved and I still can't download any data. |
Same problem as everybody else. I contacted the Help desk which created a ticket, to soon after mark it as "untaken". I guess we are on our own, with no data :( |
I found a different problem now, I am not even able to connect to the EGA server for the last 2 days:
` |
Hi, |
Is there any movement in this problem? Maybe a statement from the EGA team? |
Our team is aware of the issues impacting the download of files via the python client currently; we are actively investigating to determine its root cause and implement a resolution as quickly as possible. We apologise for any inconvenience it may be causing. We are committed to resolving this issue promptly and ensuring the continued stability and functionality of the client. We appreciate your patience and understanding during this time. We hope to have a resolution in place soon and will keep you updated on our progress. In the meantime, please ensure that you are trying to download via the latest version of the python client (v5.0.2). If you have any questions or concerns, please feel free to reach out to our helpdesk team at [email protected] and if you already have, we will get in touch with you. |
Hi, I have the same error as you. how can I slove it? I didn't find the silmilar solution. |
It is a EGA server problem that EGA is trying to solve. Still no timeline when it would be solved. |
Dear @antonkratz |
Hi, |
I get the same error for some files. However, after failing pyega3 automatically restarts the download several times and after a while successfully finishes the download. |
I have been able to download 100+ FASTQ files (between 2 and 16Gb in size) in a couple of days. It is still running. As previously mentioned, pyega3 quickly restarts and finishes the download, and it does so much faster than it was a few months back. Very happy the server is back on!!! Thanks! |
Yeah, there is no problems downloading files up to 65Gb; larger files throws a checksum error and it is not possible to download.. |
Hi, |
I have the same problem with version 5.1.0 when trying to download a file with around 150GB. Are there any news concerning this? |
I think u may can send this messages in mail to the author. This is a problem about internet. He may be solve this problem. |
I am trying to download EGAD00001001991, ~3.5 terabyte in in size. The current error message that I have is 'Remote end closed connection without response'. I have been trying to download EGAD00001001991 over the past three weeks at different time points. No success. Other errors I encountered: failed md5 checksum which can not be resolved in an unsupervised fashion (pyega3 simply hangs), and memory issues. Is it even realistic to attempt a 3.5 TB download from EGA-Archive to Japan? Or how can I download EGAD00001001991 in an unsupervised fashion and with correct md5 checksums? Would Aspera help? I wrote to helpdesk multiple times but get the "untaken" message. With over 1500 files and 3.5 TB size, I cannot manually download individual files, hunt down files with broken md5 checksums, kill hanging processes... so I am seeking a method that works in an unsupervised fashion. Reaching out for some advice how to attempt such a large download.
The text was updated successfully, but these errors were encountered: