Unable to Update - Timeout kojipkgs

Hey Guys,

I’m currently unable to update because of a weird timeout error.

$ rpm-ostree update
Receiving objects: 35% (4717/13442) 449.1 kB/s 94.8 MB... done
error: While fetching https://kojipkgs.fedoraproject.org/atomic/repo/objects/82/ad02609deba937958861a6e437fff89f749088e4d3b9a6817facc6954cb504.filez: [28] Timeout was reached
$ journalctl -b -u rpm-ostreed
-- Logs begin at Wed 2019-04-10 21:36:12 AEST, end at Tue 2019-08-20 22:46:31 AEST. --
Aug 20 21:53:22 SHERRINFORD systemd[1]: Starting RPM-OSTree System Management Daemon...
Aug 20 21:53:22 SHERRINFORD rpm-ostree[2648]: Reading config file '/etc/rpm-ostreed.conf'
Aug 20 21:53:22 SHERRINFORD rpm-ostree[2648]: In idle state; will auto-exit in 60 seconds
Aug 20 21:53:22 SHERRINFORD systemd[1]: Started RPM-OSTree System Management Daemon.
Aug 20 21:53:22 SHERRINFORD rpm-ostree[2648]: Allowing active client :1.535 (uid 1000)
Aug 20 21:53:22 SHERRINFORD rpm-ostree[2648]: client(id:gnome-software dbus:1.535 unit:session-3.scope uid:1000) added; new total=1
Aug 20 21:53:22 SHERRINFORD rpm-ostree[2648]: Initiated txn RefreshMd for client(id:gnome-software dbus:1.535 unit:session-3.scope uid:1000): /org/projectatomic/rpmostree1/fedora_workstation
Aug 20 21:53:23 SHERRINFORD rpm-ostree[2648]: Txn RefreshMd on /org/projectatomic/rpmostree1/fedora_workstation successful
Aug 20 21:53:29 SHERRINFORD rpm-ostree[2648]: Allowing active client :1.566 (uid 1000)
Aug 20 21:53:29 SHERRINFORD rpm-ostree[2648]: client(id:cli dbus:1.566 unit:gnome-terminal-server.service uid:1000) added; new total=2
Aug 20 21:53:29 SHERRINFORD rpm-ostree[2648]: Initiated txn Upgrade for client(id:cli dbus:1.566 unit:gnome-terminal-server.service uid:1000): /org/projectatomic/rpmostree1/fedora_workstation
Aug 20 21:54:12 SHERRINFORD rpm-ostree[2648]: libostree HTTP error from remote fedora-workstation for <https://kojipkgs.fedoraproject.org/atomic/repo/objects/88/bc222f7a3ca1ac4ffe6a47a96cee92a06e865e5efae49e4dc4f6333f028dd4.dirtree>: Timeout was reached
Aug 20 21:54:12 SHERRINFORD rpm-ostree[2648]: libostree HTTP error from remote fedora-workstation for <https://kojipkgs.fedoraproject.org/atomic/repo/objects/ee/4d43b210620c1f324f2884cc4b0d5045979389a1464a388be433050e862e2f.dirtree>: Timeout was reached
Aug 20 21:54:12 SHERRINFORD rpm-ostree[2648]: libostree HTTP error from remote fedora-workstation for <https://kojipkgs.fedoraproject.org/atomic/repo/objects/31/e023a7f21be181222d5c254aadacd35be113f78e67d6ff0e018363c99a0166.dirtree>: Timeout was reached
Aug 20 21:54:12 SHERRINFORD rpm-ostree[2648]: libostree HTTP error from remote fedora-workstation for <https://kojipkgs.fedoraproject.org/atomic/repo/objects/df/0df6dc1ce0f2ac47c58ace25980800a93c1c3e9c059c3950c2adf435b2d778.dirtree>: Timeout was reached
Aug 20 21:54:12 SHERRINFORD rpm-ostree[2648]: Txn Upgrade on /org/projectatomic/rpmostree1/fedora_workstation failed: While fetching https://kojipkgs.fedoraproject.org/atomic/repo/objects/88/bc222f7a3ca1ac4ffe6a47a96cee92a06e865e5efae49e4dc4f6333f028dd4.dirtree: [28] Timeout was reached
Aug 20 21:54:12 SHERRINFORD rpm-ostree[2648]: client(id:cli dbus:1.566 unit:gnome-terminal-server.service uid:1000) vanished; remaining=1

I’m unsure if this is actually an issue with the remote host, I’ve tried via VPN and without, seems to yield the same result.

I do live in Australia, having terrible connectivity to anywhere, perhaps I need to edit a timeout value somewhere?

Cheers!

Hey @dylanger! You might be using the old configuration that doesn’t take advantage of CDN. We started delivering the new configuration via an rpm… The rpm and the file delivered by the rpm are shown below:

[dustymabe@mactop ~]$ cat /etc/ostree/remotes.d/fedora.conf 
[remote "fedora"]
url=https://ostree.fedoraproject.org
gpg-verify=true
gpgkeypath=/etc/pki/rpm-gpg/
contenturl=mirrorlist=https://ostree.fedoraproject.org/mirrorlist
[dustymabe@mactop ~]$ rpm -qf /etc/ostree/remotes.d/fedora.conf 
fedora-repos-ostree-30-1.noarch

can you check the files in your /etc/ostree/remotes.d/ directory and make sure fedora.conf exists and has those contents? If so you should be able to rpm-ostree rebase fedora: to start using the new remote that is hosted on the CDN.

Cheers @dustymabe, I’ve just checked, I do indeed have the rpm already installed.

It seems to be an issue with fedora-workstation.conf specifically.

Right… You need to either switch to using fedora.conf (by rebasing) or replace the contents of fedora-workstation.conf with what is in fedora.conf.

Fantastic! Simply rebasing to fedora (rpm-ostree rebase fedora:) as you mentioned above fixed my issue, thank you very much @dustymabe :+1:

I had assumed the colon was a typeo lol