chlor
August 21, 2022, 8:29am
1
Hi
As of 2022-08-20 I have started getting this error:
August 21, 2022 8:59 AM
Updater failed:
runtime: [string “requests”]:430: [string “utils”]:420: Getting URI (https://repo.turris.cz/hbs/omnia/lists/pkglists/lxc.lua ) failed: Operation timed out after 600098 milliseconds with 0 out of 0 bytes received
Updater failed:
runtime: [string “requests”]:430: [string “utils”]:422: Unable to finish URI (https://repo.turris.cz/hbs/omnia/lists/updater.lua ): Signature URI failure: https://repo.turris.cz/hbs/omnia/lists/updater.lua.sig: Download failed
I also tried to run update manually:
root@turris:~# opkg update
Downloading https://repo.turris.cz/hbs/omnia/packages/core/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_core
…
Signature check passed.
Downloading https://repo.turris.cz/hbs/omnia/packages/cesnet/Packages.gz
But it hang after some packages.
I tried with a reboot with the same result.
TurrisOS 5.4.1, Turris Omnia
I tried the Luci interface via System->Software->Update-lists… as this gives the same error as ‘opkg update’.
Hi,
since 3 days I get this update timeout messages too.
It hits files randomly.
Example:
Error notifications
Updater execution failed:
runtime: [string "requests"]:432: [string "utils"]:441: Getting URI (https://repo.turris.cz/hbs/omnia/lists/terminal-apps.lua ) failed: Failed to connect to repo.turris.cz port 443 after 131731 ms: Operation timed out"
My Turris Omnia version:
reForis version 1.4.1
Turris OS version 6.2.2
Turris OS branch HBS
Kernel version 5.15.88
My WAN interface looks good. No errors or drops:
root@xxxx:~# ip -d -s -s -h address show eth2
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1024
link/ether d8:58:d7:xx:xx:xx brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 9676 numtxqueues 8 numrxqueues 8 gso_max_size 65536 gso_max_segs 100
inet x.x.x.x/24 brd x.x.x.x scope global eth2
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped missed mcast
11.5G 24.0M 0 0 0 0
RX errors: length crc frame fifo overrun
0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
278M 3.81M 0 0 0 0
TX errors: aborted fifo window heartbeat transns
0 0 0 0 2
After searching the forum I done the mtr tests:
root@xxxx:~# mtr -T -P 443 -n -r repo.turris.cz
Start: 2023-01-30T11:39:14+0100
HOST: xxxx Loss% Snt Last Avg Best Wrst StDev
1.|-- x.x.x.x 0.0% 10 11.5 11.5 9.7 16.6 2.0
2.|-- x.x.x.x 0.0% 10 9.8 10.5 8.0 15.1 1.8
3.|-- x.x.x.x 0.0% 10 12.8 12.3 10.3 14.1 1.3
4.|-- 145.254.3.102 0.0% 10 16.7 12.2 10.6 16.7 1.8
5.|-- 145.254.2.195 0.0% 10 16.7 17.6 16.2 21.2 1.4
6.|-- 80.81.192.217 0.0% 10 18.9 20.8 16.1 43.7 8.2
7.|-- 82.119.246.102 0.0% 10 27.6 27.3 24.9 30.2 1.6
8.|-- 82.119.246.14 0.0% 10 25.9 28.2 25.8 38.2 3.7
82.119.246.27
9.|-- 82.119.246.238 0.0% 10 25.9 30.1 24.6 60.6 10.8
82.119.246.82
10.|-- 82.113.33.102 0.0% 10 31.0 27.7 25.4 31.3 2.3
11.|-- 84.244.124.39 0.0% 10 26.0 24.3 22.4 27.0 1.7
12.|-- 82.99.180.41 0.0% 10 26.0 25.0 22.2 28.9 2.0
13.|-- 217.31.192.84 20.0% 10 25.2 24.1 22.4 29.9 2.5
root@xxxx:~# mtr -T -P 443 -n -r repo.turris.cz
Start: 2023-01-30T12:03:18+0100
HOST: xxxx Loss% Snt Last Avg Best Wrst StDev
1.|-- x.x.x.x 0.0% 10 10.3 13.5 10.2 24.7 4.5
2.|-- x.x.x.x 0.0% 10 9.6 11.3 9.1 14.2 1.9
3.|-- x.x.x.x 0.0% 10 11.6 11.7 8.8 18.3 2.7
4.|-- 145.254.3.102 0.0% 10 13.6 13.5 10.1 22.6 3.5
5.|-- 145.254.2.195 0.0% 10 16.6 18.2 16.3 22.6 1.8
6.|-- 80.81.192.217 0.0% 10 20.6 19.6 16.8 28.0 3.7
7.|-- 82.119.246.102 0.0% 10 36.7 30.4 25.3 38.4 5.0
8.|-- 82.119.246.14 0.0% 10 36.7 28.5 25.6 36.7 3.2
82.119.246.27
9.|-- 82.119.246.238 0.0% 10 26.8 26.5 24.9 28.5 1.2
82.119.246.82
10.|-- 82.113.33.102 0.0% 10 33.8 28.2 23.9 34.1 3.9
11.|-- 84.244.124.39 0.0% 10 21.7 28.2 21.7 39.9 5.3
12.|-- 82.99.180.41 0.0% 10 23.8 24.0 21.8 25.9 1.5
13.|-- 217.31.192.84 20.0% 10 25.6 26.3 22.7 32.8 3.4
This tells me, that there is no DNS or ISP failor at my side. Only the repo server produces this losses.
Is there somting different at the repo server since 3 days?
Thanks
matfax
January 31, 2023, 1:31pm
3
In my case, the recent issues disappeared after uninstalling the mwan3 package, which I wasn’t utilizing anymore.
In this case, this package isn’t installed at my turris.
opkg list-installed mwan3
But seems the update timeouts are gone.
Last Error record at notifications:
January 31, 2023 9:19 AM