| View previous topic :: View next topic |
| Author |
Message |
Majed17
Guru
Joined: 31 Aug 2011
Posts: 333
Location: Minsk, Belarus
|
 Posted: Thu Jun 27, 2024 7:51 am Post subject: why is rsync not working? [solved] |
 |
|
| Code: | sudo emerge --sync
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys via WKD ... [ ok ]
>>> Starting rsync with rsync://89.238.71.6/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.3.0]
>>> Retrying...
>>> Starting retry 1 of 3 with rsync://81.91.253.252/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.3.0]
>>> Retrying...
>>> Starting retry 2 of 3 with rsync://[2a01:90:200:10::1a]/gentoo-portage
>>> Checking server timestamp ...
rsync: [Receiver] failed to connect to 2a01:90:200:10::1a (2a01:90:200:10::1a): Network is unreachable (101)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0]
>>> Retrying...
>>> Starting retry 3 of 3 with rsync://[2a00:1828:a00d:ffff::6]/gentoo-portage
>>> Checking server timestamp ...
rsync: [Receiver] failed to connect to 2a00:1828:a00d:ffff::6 (2a00:1828:a00d:ffff::6): Network is unreachable (101)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.3.0]
>>> Retrying...
!!! Exhausted addresses for rsync.gentoo.org
Action: sync for repo: gentoo, returned code = 1 |
| Code: |
ping -c 3 rsync.gentoo.org
PING rsync.gentoo.org (89.238.71.6) 56(84) bytes of data.
64 bytes from turnstone.gentoo.org (89.238.71.6): icmp_seq=1 ttl=54 time=42.0 ms
64 bytes from turnstone.gentoo.org (89.238.71.6): icmp_seq=2 ttl=54 time=39.3 ms
64 bytes from turnstone.gentoo.org (89.238.71.6): icmp_seq=3 ttl=54 time=40.0 ms
|
| Code: | systemctl status systemd-resolved
○ systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; preset: enabled)
Active: inactive (dead)
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
|
what to do?
_________________
Seek and you shall find, Knock and it shall be opened, cry and you shall find comfort.
Last edited by Majed17 on Thu Jun 27, 2024 11:11 am; edited 1 time in total |
|
| Back to top |
|
 |
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5114
Location: Bavaria
|
|
| Back to top |
|
|
Majed17
Guru
Joined: 31 Aug 2011
Posts: 333
Location: Minsk, Belarus
|
| Posted: Thu Jun 27, 2024 11:11 am Post subject: |
|
|
thanks, it works
_________________
Seek and you shall find, Knock and it shall be opened, cry and you shall find comfort. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
