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

mirror not answering, but status still Up in mirrorbits #103

Open
stormi opened this issue Apr 15, 2020 · 0 comments
Open

mirror not answering, but status still Up in mirrorbits #103

stormi opened this issue Apr 15, 2020 · 0 comments

Comments

@stormi
Copy link

stormi commented Apr 15, 2020

Hi,

I've had several users reporting failed downloads. I tracked it down to a specific mirror that mirrorbits still considers up though it can't contact it...

avril 15 14:21:35 xcpng-repo mirrorbits[36752]: 2020/04/15 14:21:35.206 CEST [mirror.buf.us.smartcrew.xyz] Timeout waiting for daemon connection
avril 15 14:36:05 xcpng-repo mirrorbits[36752]: 2020/04/15 14:36:05.194 CEST [mirror.buf.us.smartcrew.xyz] Requesting file list via rsync...
avril 15 14:36:25 xcpng-repo mirrorbits[36752]: 2020/04/15 14:36:25.192 CEST [mirror.buf.us.smartcrew.xyz] fetching trace file failed: Get http://mirror.buf.us.smartcrew.xyz/xcp-ng/trace: dial tcp 107.175.70.118:80: i/o timeout
avril 15 14:36:35 xcpng-repo mirrorbits[36752]: 2020/04/15 14:36:35.208 CEST [mirror.buf.us.smartcrew.xyz] Timeout waiting for daemon connection
avril 15 14:51:05 xcpng-repo mirrorbits[36752]: 2020/04/15 14:51:05.194 CEST [mirror.buf.us.smartcrew.xyz] Requesting file list via rsync...
avril 15 14:51:25 xcpng-repo mirrorbits[36752]: 2020/04/15 14:51:25.192 CEST [mirror.buf.us.smartcrew.xyz] fetching trace file failed: Get http://mirror.buf.us.smartcrew.xyz/xcp-ng/trace: dial tcp 107.175.70.118:80: i/o timeout
avril 15 14:51:35 xcpng-repo mirrorbits[36752]: 2020/04/15 14:51:35.208 CEST [mirror.buf.us.smartcrew.xyz] Timeout waiting for daemon connection
avril 15 15:06:05 xcpng-repo mirrorbits[36752]: 2020/04/15 15:06:05.194 CEST [mirror.buf.us.smartcrew.xyz] Requesting file list via rsync...
avril 15 15:06:25 xcpng-repo mirrorbits[36752]: 2020/04/15 15:06:25.192 CEST [mirror.buf.us.smartcrew.xyz] fetching trace file failed: Get http://mirror.buf.us.smartcrew.xyz/xcp-ng/trace: dial tcp 107.175.70.118:80: i/o timeout
avril 15 15:06:35 xcpng-repo mirrorbits[36752]: 2020/04/15 15:06:35.208 CEST [mirror.buf.us.smartcrew.xyz] Timeout waiting for daemon connection
avril 15 15:21:05 xcpng-repo mirrorbits[36752]: 2020/04/15 15:21:05.193 CEST [mirror.buf.us.smartcrew.xyz] Requesting file list via rsync...
avril 15 15:21:25 xcpng-repo mirrorbits[36752]: 2020/04/15 15:21:25.192 CEST [mirror.buf.us.smartcrew.xyz] fetching trace file failed: Get http://mirror.buf.us.smartcrew.xyz/xcp-ng/trace: dial tcp 107.175.70.118:80: i/o timeout
avril 15 15:21:35 xcpng-repo mirrorbits[36752]: 2020/04/15 15:21:35.208 CEST [mirror.buf.us.smartcrew.xyz] Timeout waiting for daemon connection
avril 15 15:36:05 xcpng-repo mirrorbits[36752]: 2020/04/15 15:36:05.193 CEST [mirror.buf.us.smartcrew.xyz] Requesting file list via rsync...
avril 15 15:36:25 xcpng-repo mirrorbits[36752]: 2020/04/15 15:36:25.192 CEST [mirror.buf.us.smartcrew.xyz] fetching trace file failed: Get http://mirror.buf.us.smartcrew.xyz/xcp-ng/trace: dial tcp 107.175.70.118:80: i/o timeout
avril 15 15:36:35 xcpng-repo mirrorbits[36752]: 2020/04/15 15:36:35.203 CEST [mirror.buf.us.smartcrew.xyz] Timeout waiting for daemon connection
avril 15 15:51:05 xcpng-repo mirrorbits[36752]: 2020/04/15 15:51:05.194 CEST [mirror.buf.us.smartcrew.xyz] Requesting file list via rsync...
avril 15 15:51:25 xcpng-repo mirrorbits[36752]: 2020/04/15 15:51:25.192 CEST [mirror.buf.us.smartcrew.xyz] fetching trace file failed: Get http://mirror.buf.us.smartcrew.xyz/xcp-ng/trace: dial tcp 107.175.70.118:80: i/o timeout
avril 15 15:51:35 xcpng-repo mirrorbits[36752]: 2020/04/15 15:51:35.204 CEST [mirror.buf.us.smartcrew.xyz] Timeout waiting for daemon connection

It's doing it only for this mirror. The rest is fine.

Any idea what's going on and how to avoid this in the future?

We might be able to contribute a fix if a fix must be done, if we get an understanding of what is going on.

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

1 participant