sync timeouts on a system running under WSL

Message

larand54 · Post by **larand54** » Wed Dec 13, 2023 10:47 am

Using a stage3 tar ball in WSL I managed to make it work, but running "emerge --sync" times out all time.
I tried different repos but all failed. Adding new packages using emerge seems to work and even websync does,
so why not "emerge --sync"?

I can't see that there are any firewall problem as theres no rules for outgoing requests.

Any ideas?

logrusx · Post by **logrusx** » Wed Dec 13, 2023 2:05 pm

I heard WSL had terrible IO and I guess you're using rsync so this should answer your question. I think webrsync should work fine as (to my understanding) it grabs a snapshot and the rest is done locally. Did you try using git?

Best Regards,
Georgi

Genone · Post by **Genone** » Wed Dec 13, 2023 2:14 pm

First question would be WSL1 or WSL2, as those operate very differently under the hood (syscall emulation vs. full virtualization) which can have significant impact on IO performance. If using WSL2 you could use wireshark to check network traffic on the virtual network interface to maybe give you a clue what is going wrong.

CaptainBlood · Post by **CaptainBlood** » Wed Dec 13, 2023 3:39 pm

Do you have /etc/resolv.conf provided?
EDIT: My bad, overlooked OP, sorry...
Thks 4 ur attention, interest & support.

Post by Hu » Wed Dec 13, 2023 3:53 pm

What is the output of LC_MESSAGES=C emerge --sync when it fails? Knowing the exact error message may help us offer better guidance.

larand54 · Post by **larand54** » Wed Dec 13, 2023 6:47 pm

Answer to Hu:
JME-SSD /etc/portage/repos.conf # LC_MESSAGES=C 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://rsync.se.gentoo.org...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.2.7]
>>> Retrying...

>>> Starting retry 1 of 1 with rsync://rsync.se.gentoo.org
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.2.7]
>>> Retrying...
!!! Exhausted addresses for rsync.se.gentoo.org
>>> Syncing repository 'guru' into '/var/db/repos/guru'...
/usr/bin/git fetch origin --depth 1
remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
/usr/bin/git reset --merge refs/remotes/origin/master
=== Sync completed for guru

Action: sync for repo: gentoo, returned code = 1
Action: sync for repo: guru, returned code = 0

=====================================
Answer to logrusx:

Yes I tried git too but having the same result.

========================================
Answer to CaptainBlood:
JME-SSD /etc/portage/repos.conf # cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver 8.8.8.8
nameserver 192.168.80.1

====================================
Answer to Genone:

I have it captured in a file but I'm not sure how I could post that here?

CaptainBlood · Post by **CaptainBlood** » Wed Dec 13, 2023 7:20 pm

Currently using WSL2,

I had similar symptom less than 2 weeks ago.
fixed resetting as follow:

Code: Select all

cat /etc/portage/repos.conf/gentoo.conf
[DEFAULT]
main-repo = gentoo

[gentoo]
location = /var/db/repos/gentoo
sync-type = rsync
#sync-uri = rsync://rsync.gentoo.org/gentoo-portage
sync-uri = rsync://rsync.europe.gentoo.org/gentoo-portage
auto-sync = yes
sync-rsync-verify-jobs = 1
sync-rsync-verify-metamanifest = yes
sync-rsync-verify-max-age = 24
sync-openpgp-key-path = /usr/share/openpgp-keys/gentoo-release.asc
sync-openpgp-keyserver = hkps://keys.gentoo.org
sync-openpgp-key-refresh-retry-count = 40
sync-openpgp-key-refresh-retry-overall-timeout = 1200
sync-openpgp-key-refresh-retry-delay-exp-base = 2
sync-openpgp-key-refresh-retry-delay-max = 60
sync-openpgp-key-refresh-retry-delay-mult = 4
sync-webrsync-verify-signature = yes

EDIT: My backbone is Europe based, despite I'm far oversea.
You may have to adapt to your environment.

Thks 4 ur attention, interest & support.

Genone · Post by **Genone** » Thu Dec 14, 2023 8:58 am

Regarding the wireshark log, just open it and in the text field below the symbol bar (should say sth, like "Apply a display filter") enter "tcp.port == 873" (without the quotes). Then it should be relatively obvious if there is any actual rsync traffic, or just failed connection attempts. If the list is completely empty with that filter the issue is probably that portage doesn't find any actual servers for your configuration, so might be worth trying a different sync-uri setting. The output you posted kinda points into that direction.