Install CRIO - Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: 95.216.238.135 443]

[rsjatnika]

What happened?

E: Failed to fetch https://mirror.aardsoft.fi/opensuse/repositories/devel%3A/kubic%3A/libcontainers%3A/stable/xUbuntu_22.04/amd64/cri-o-runc_1.1.12~0_amd64.deb Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: 95.216.238.135 443]

What did you expect to happen?

this IP 95.216.238.135 443 will available to support CRIO installation

How can we reproduce it (as minimally and precisely as possible)?

I just follow below web site :

https://www.linuxtechi.com/install-crio-container-runtime-on-ubuntu/

and previously it's ok, but now it's always failed with below error:

running apt-update && apt install

running: command not found
root@control-plane:/home/kubernetes# apt-update && apt install
apt-update: command not found
root@control-plane:/home/kubernetes# sudo apt install cri-o cri-o-runc -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
containernetworking-plugins
The following NEW packages will be installed:
cri-o-runc
The following packages will be upgraded:
cri-o
1 upgraded, 1 newly installed, 0 to remove and 97 not upgraded.
Need to get 3,095 kB/35.3 MB of archives.
After this operation, 34.1 MB of additional disk space will be used.
Ign:1 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04 cri-o-runc 1.1.120
Ign:1 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04 cri-o-runc 1.1.120
Ign:1 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04 cri-o-runc 1.1.120
Err:1 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04 cri-o-runc 1.1.120
Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: 95.216.238.135 443]
E: Failed to fetch https://mirror.aardsoft.fi/opensuse/repositories/devel%3A/kubic%3A/libcontainers%3A/stable/xUbuntu_22.04/amd64/cri-o-runc_1.1.12~0_amd64.deb Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: 95.216.238.135 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Anything else we need to know?

No response

CRI-O and Kubernetes version

$ crio --version
# paste output here

$ export OS=xUbuntu_22.04
$ export CRIO_VERSION=1.24

also have tried with CRIO 1.28 but the same error

$ kubectl version --output=json
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output hereroot@control-plane:/#  cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
root@control-plane:/#

 
$ uname -a
# paste output here

root@control-plane:/# uname -a
Linux control-plane 5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
root@control-plane:/#

Additional environment details (AWS, VirtualBox, physical, etc.)

user Oracle VM virtual box manager

[rsjatnika]

seem ping to IP 95.216.238.135 have packet loss.
Any one that can sync with server owner, please help.

root@node02:/home/kubernetes# ping 95.216.238.135
PING 95.216.238.135 (95.216.238.135) 56(84) bytes of data.
64 bytes from 95.216.238.135: icmp_seq=1 ttl=42 time=564 ms
64 bytes from 95.216.238.135: icmp_seq=2 ttl=42 time=359 ms
64 bytes from 95.216.238.135: icmp_seq=3 ttl=42 time=353 ms
64 bytes from 95.216.238.135: icmp_seq=4 ttl=42 time=355 ms
64 bytes from 95.216.238.135: icmp_seq=5 ttl=42 time=357 ms
64 bytes from 95.216.238.135: icmp_seq=6 ttl=42 time=348 ms
64 bytes from 95.216.238.135: icmp_seq=7 ttl=42 time=357 ms
64 bytes from 95.216.238.135: icmp_seq=9 ttl=42 time=537 ms
64 bytes from 95.216.238.135: icmp_seq=11 ttl=42 time=333 ms
64 bytes from 95.216.238.135: icmp_seq=12 ttl=42 time=358 ms
64 bytes from 95.216.238.135: icmp_seq=13 ttl=42 time=351 ms
64 bytes from 95.216.238.135: icmp_seq=14 ttl=42 time=354 ms
64 bytes from 95.216.238.135: icmp_seq=15 ttl=42 time=356 ms
64 bytes from 95.216.238.135: icmp_seq=16 ttl=42 time=349 ms
64 bytes from 95.216.238.135: icmp_seq=17 ttl=42 time=354 ms
^C
--- 95.216.238.135 ping statistics ---
19 packets transmitted, 15 received, 21.0526% packet loss, time 18073ms
rtt min/avg/max/mdev = 333.180/378.972/563.669/67.627 ms
root@node02:/home/kubernetes#

[sohankunkerkar]

@rsjatnika, did you try this link? we have changed the packaging for cri-o sarting with v1.29. Let me know if this resolves your issue.