| View previous topic :: View next topic |
| Author |
Message |
vode
n00b
Joined: 16 Jul 2002
Posts: 35
Location: Finland
|
 Posted: Mon Mar 11, 2024 6:24 pm Post subject: emerge --sync and ipv6 |
 |
|
When I do emerge --sync:
spac ~ # emerge --sync -q
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.2.7]
>>> Retrying...
>>> Starting retry 1 of 3 with rsync://[2a01:90:200:10::1a]/gentoo-portage
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.2.7]
>>> Retrying...
>>> Starting retry 2 of 3 with rsync://81.91.253.252/gentoo-portage
Sync completes. But only by IP4 address. Otherwise ipv6 works if I test by web (test-ipv6.com, ipv6test.google.com)
Must be something wrong with my configs that portage cannot do ipv6?
Though not in trouble with that - cuorisity.
vode |
|
| Back to top |
|
 |
flexibeast
Guru
Joined: 04 Apr 2022
Posts: 324
Location: Naarm/Melbourne, Australia
|
| Posted: Tue Mar 12, 2024 1:20 am Post subject: |
|
|
| Are you sure that the host specified by 2a01:90:200:10::1a is both up and a current Gentoo rsync mirror? |
|
| Back to top |
|
|
vode
n00b
Joined: 16 Jul 2002
Posts: 35
Location: Finland
|
| Posted: Tue Mar 12, 2024 4:55 pm Post subject: |
|
|
I have not specified any mirrors in make.conf. Kind of thinking that defaults are fine.
I will do the optional instructions from Gentoo install guide to select mirrors. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54270
Location: 56N 3W
|
| Posted: Tue Mar 12, 2024 5:45 pm Post subject: |
|
|
vode,
I can reproduce the problem but with a different error message.
| Code: | Pi5 ~ # 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://[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): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]
>>> Retrying...
>>> Starting retry 1 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): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]
>>> Retrying...
>>> Starting retry 2 of 3 with rsync://81.91.253.252/gentoo-portage
>>> Checking server timestamp ...
Welcome to starling.gentoo.org / rsync.gentoo.org |
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
vode
n00b
Joined: 16 Jul 2002
Posts: 35
Location: Finland
|
| Posted: Mon Apr 15, 2024 2:15 pm Post subject: |
|
|
| NeddySeagoon wrote: | vode,
I can reproduce the problem but with a different error message.
| Code: | Pi5 ~ # 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://[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): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]
>>> Retrying...
>>> Starting retry 1 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): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]
>>> Retrying...
>>> Starting retry 2 of 3 with rsync://81.91.253.252/gentoo-portage
>>> Checking server timestamp ...
Welcome to starling.gentoo.org / rsync.gentoo.org |
|
--------------------------------------------------------------------------
Continued...
This is my symmary.log of last sync:
1713189327: Started emerge on: huhti 15, 2024 16:55:26
1713189327: *** emerge --regex-search-auto=y --sync
1713189327: === sync
1713189328: >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
1713189330: >>> Starting rsync with rsync://[2a00:1828:a00d:ffff::6]/gentoo-portage
1713189345: >>> Starting retry 1 of 3 with rsync://[2a01:90:200:10::1a]/gentoo-portage
1713189360: >>> Starting retry 2 of 3 with rsync://81.91.253.252/gentoo-portage
1713189562: === Sync completed for gentoo
1713189563: *** terminating.
So sync succeeds with ipv4.
This is my ping out put:
markku@spac ~ $ ping -c 3 2a00:1828:a00d:ffff::6
PING 2a00:1828:a00d:ffff::6 (2a00:1828:a00d:ffff::6) 56 data bytes
64 bytes from 2a00:1828:a00d:ffff::6: icmp_seq=1 ttl=54 time=42.7 ms
64 bytes from 2a00:1828:a00d:ffff::6: icmp_seq=2 ttl=54 time=42.7 ms
64 bytes from 2a00:1828:a00d:ffff::6: icmp_seq=3 ttl=54 time=42.7 ms
--- 2a00:1828:a00d:ffff::6 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 42.664/42.693/42.745/0.036 ms |
|
| Back to top |
|
|
|
Portage & Programming
