Resource temporarily unavailable

[jmsnavarro]

When running sudo apt update, it shows the following:

Ign:14 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bionic InRelease
Err:15 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bionic Release
  Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: 35.231.52.82 443]
Reading package lists... Done
E: The repository 'https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bionic Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I am using Ubuntu over WSL 1

$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
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"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

[karianna]

@jmsnavarro - I think it's back up, can you try again?

[jmsnavarro]

@jmsnavarro - I think it's back up, can you try again?

Same issue remains after re-running sudo apt update

[aahlenst]

It's working in a container, so either there are intermittent problems with Artifactory or the problem is somewhere else. I do not have a machine with WSL at hand, so hard to say if the problem is WSL. @jmsnavarro How did you configure the repositories?

[aahlenst]

I tried it on a machine with Windows 10, WSL 1, and Ubuntu 18.04 using the installation instructions on https://adoptopenjdk.net/installation.html#linux-pkg. Worked like a charm.

[jmsnavarro]

Ok, what I noticed was no issues (was able to run sudo apt update) at home except from our corporate office. Any ideas?

[aahlenst]

Proxy? Does apt-get update work for other servers?

[jmsnavarro]

Proxy? Does apt-get update work for other servers?

I think so.

I am now connected to our corporate network. After running an apt update, the issue remains.

Where the update somewhat pauses while attempting to connect to https://adoptopenjdk.jfrog.io over 35.231.52.82

And then finish with this:

[aahlenst]

Could you run curl https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/dists/bionic/Release within WSL? Should output something like (shortened):

Origin: Artifactory
Label: Artifactory
Suite: bionic
Codename: bionic
Date: Tue, 28 Jan 2020 13:40:44 UTC
Acquire-By-Hash: yes
Components: main
Architectures: amd64 arm64 armhf i386 ppc64el s390x
MD5Sum:
 1b4204818448440b22082d922a2eafd8            94715 main/binary-amd64/Packages
 7557e1e35c1dad91741c2f238f6ea8b7             7787 main/binary-amd64/Packages.bz2

[aahlenst]

Closing due to inactivity. Feel free to reopen if you have new information.

[draganbjedov]

I got same problem today:

Err:29 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bionic Release                               
  Unknown date format Bad header data [IP: 35.231.52.82 443]
Hit:30 http://ppa.launchpad.net/rvm/smplayer/ubuntu bionic InRelease                               
Hit:31 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu bionic InRelease         
Hit:33 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease                                                              
Hit:34 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic InRelease                                                          
Hit:28 https://packagecloud.io/AtomEditor/atom/any any InRelease        
Reading package lists... Done                      
E: The repository 'https://adoptopenjdk.jfrog.io/adoptopenjdk/deb bionic Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details

My OS is Linux Mint 19.3

[aahlenst]

@draganbjedov This time, it's different. Please see adoptium/infrastructure#1399.

[RobinsonShai]

edit the sources file located at /etc/apt/sources.list and remove the repositories causing that problem.