Cannot update from core 183 with CLI

Community
1

My IPfire was at version core 182.

[root@ipfire ~]# pakfire status
Core-Version: 2.27-x86_64
Core-Update-Level: 182
Last update: 79d 12h 57m 56s ago
Last core-list update: 13s ago
Last server-list update: 16s ago
Last packages-list update: 14s ago
Core-Update available: yes (183)
Package-Updates available: 0
Reboot required: no

I updated it from console with pakfire to version 183, there was no issue. I rebooted the box.

I know there is version 184 but pakfire cannot see it:

[root@ipfire ~]# pakfire status
Core-Version: 2.29-x86_64
Core-Update-Level: 183
Last update: 4m 56s ago
Last core-list update: 12m 36s ago
Last server-list update: 12m 39s ago
Last packages-list update: 12m 37s ago
Core-Update available: no
Package-Updates available: 0
Reboot required: no

[root@ipfire ~]# pakfire update
[root@ipfire ~]# pakfire upgrade
CORE INFO: Checking for Core-Updates...
CORE INFO: No new Core-Updates available. You are on release 183
PAKFIRE INFO: Checking for package updates...
PAKFIRE WARN: No new package upgrades available.

I tried to use GUI, with button “Refresh List”. An error was reported but I cannot see error in the log and I see I can update to new version. This is log from GUI:

Mar 24 12:39:18 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.29-x86_64 started!
Mar 24 12:39:18 ipfire pakfire: DOWNLOAD INFO: Signature of meta-libseccomp is fine.
Mar 24 12:39:18 ipfire pakfire: PAKFIRE ERROR: Another instance of pakfire is already running!
Mar 24 12:39:18 ipfire pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
Mar 24 12:39:18 ipfire pakfire: DOWNLOAD FINISHED: pakfire2/2.29-x86_64/meta/meta-libseccomp
Mar 24 12:39:18 ipfire pakfire: DOWNLOAD STARTED: meta/meta-tor
Mar 24 12:39:18 ipfire pakfire: MIRROR INFO: 21 servers found in list
Mar 24 12:39:18 ipfire pakfire: DOWNLOAD INFO: Host: ftp.belnet.be (HTTPS) - File: mirror/ipfire/current/pakfire2/2.29-x86_64/meta/meta-tor
Mar 24 12:39:19 ipfire pakfire: DOWNLOAD INFO: mirror/ipfire/current/pakfire2/2.29-x86_64/meta/meta-tor has size of 1072 bytes
Mar 24 12:39:19 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Mar 24 12:39:19 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
Mar 24 12:39:19 ipfire pakfire: DOWNLOAD INFO: Signature of meta-tor is fine.
Mar 24 12:39:19 ipfire pakfire: DOWNLOAD FINISHED: mirror/ipfire/current/pakfire2/2.29-x86_64/meta/meta-tor
Mar 24 12:39:19 ipfire pakfire: DOWNLOAD STARTED: meta/meta-haproxy
Mar 24 12:39:19 ipfire pakfire: MIRROR INFO: 21 servers found in list
Mar 24 12:39:19 ipfire pakfire: DOWNLOAD INFO: Host: ftp.belnet.be (HTTPS) - File: mirror/ipfire/current/pakfire2/2.29-x86_64/meta/meta-haproxy
Mar 24 12:39:20 ipfire pakfire: DOWNLOAD INFO: mirror/ipfire/current/pakfire2/2.29-x86_64/meta/meta-haproxy has size of 1067 bytes
Mar 24 12:39:20 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Mar 24 12:39:20 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
Mar 24 12:39:20 ipfire pakfire: DOWNLOAD INFO: Signature of meta-haproxy is fine.
Mar 24 12:39:20 ipfire pakfire: DOWNLOAD FINISHED: mirror/ipfire/current/pakfire2/2.29-x86_64/meta/meta-haproxy
Mar 24 12:39:20 ipfire pakfire: DOWNLOAD STARTED: meta/meta-git
Mar 24 12:39:20 ipfire pakfire: MIRROR INFO: 21 servers found in list
Mar 24 12:39:20 ipfire pakfire: DOWNLOAD INFO: Host: mirrors.ocf.berkeley.edu (HTTPS) - File: ipfire/pakfire2/2.29-x86_64/meta/meta-git
Mar 24 12:39:22 ipfire pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.29-x86_64/meta/meta-git has size of 1103 bytes
Mar 24 12:39:23 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Mar 24 12:39:23 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
Mar 24 12:39:23 ipfire pakfire: DOWNLOAD INFO: Signature of meta-git is fine.
Mar 24 12:39:23 ipfire pakfire: DOWNLOAD FINISHED: ipfire/pakfire2/2.29-x86_64/meta/meta-git
Mar 24 12:39:23 ipfire pakfire: DOWNLOAD STARTED: meta/meta-fmt
Mar 24 12:39:23 ipfire pakfire: MIRROR INFO: 21 servers found in list
Mar 24 12:39:23 ipfire pakfire: DOWNLOAD INFO: Host: ipfire.earl-net.com (HTTPS) - File: pakfire2/2.29-x86_64/meta/meta-fmt
Mar 24 12:39:24 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.29-x86_64/meta/meta-fmt has size of 1035 bytes
Mar 24 12:39:24 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Mar 24 12:39:24 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
Mar 24 12:39:24 ipfire pakfire: DOWNLOAD INFO: Signature of meta-fmt is fine.
Mar 24 12:39:24 ipfire pakfire: DOWNLOAD FINISHED: pakfire2/2.29-x86_64/meta/meta-fmt
Mar 24 12:39:24 ipfire pakfire: CORE INFO: core-list.db is 820 seconds old. - DEBUG: force
Mar 24 12:39:24 ipfire pakfire: DOWNLOAD STARTED: lists/core-list.db
Mar 24 12:39:24 ipfire pakfire: MIRROR INFO: 21 servers found in list
Mar 24 12:39:24 ipfire pakfire: DOWNLOAD INFO: Host: mirror.marwan.ma (HTTPS) - File: ipfire/pakfire2/2.29-x86_64/lists/core-list.db
Mar 24 12:39:25 ipfire pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.29-x86_64/lists/core-list.db has size of 903 bytes
Mar 24 12:39:26 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Mar 24 12:39:26 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
Mar 24 12:39:26 ipfire pakfire: DOWNLOAD INFO: Signature of core-list.db is fine.
Mar 24 12:39:26 ipfire pakfire: DOWNLOAD FINISHED: ipfire/pakfire2/2.29-x86_64/lists/core-list.db
Mar 24 12:39:26 ipfire pakfire: PAKFIRE INFO: Pakfire has finished. Closing.

Now I can update, from GUI or from CLI:

[root@ipfire ~]# pakfire status
Core-Version: 2.29-x86_64
Core-Update-Level: 183
Last update: 6m 59s ago
Last core-list update: 57s ago
Last server-list update: 1m 17s ago
Last packages-list update: 1m 15s ago
Core-Update available: yes (184)
Package-Updates available: 6
Reboot required: no

[root@ipfire ~]# pakfire update
meta-iperf3          100.00% |=============================>|    1.01 KB
meta-cpufrequtils... 100.00% |=============================>|    1.03 KB
meta-mpfire          100.00% |=============================>|    1.03 KB
meta-haproxy         100.00% |=============================>|    1.04 KB
meta-git             100.00% |=============================>|    1.08 KB
meta-fmt             100.00% |=============================>|    1.01 KB

file pakfire.log is empty and was not updated for a year…

[root@ipfire ~]# ll /var/log/pakfire.log 
-rw-r--r-- 1 root nobody 0 Oct 18  2022 /var/log/pakfire.log

[root@ipfire ~]# ll /var/log/pakfire/update-core-upgrade-18*
-rw-r--r-- 1 root root 364741 Oct 15 22:01 /var/log/pakfire/update-core-upgrade-180.log
-rw-r--r-- 1 root root 784162 Nov 25 20:35 /var/log/pakfire/update-core-upgrade-181.log
-rw-r--r-- 1 root root  91799 Jan  4 23:27 /var/log/pakfire/update-core-upgrade-182.log
-rw-r--r-- 1 root root 944629 Mar 24 12:33 /var/log/pakfire/update-core-upgrade-183.log

Similar report is here

2

Read the whole of that thread, where i give an explanation for why i think that is happenning and then see @methusalix post near the end where he confirmed my understanding.

1 Like
3

I cannot see explanation in that thread. There is some guess but I do not think it is the explanation. I upgraded from 182 to 183, no issue, just one small upgrade. And I was not able to continue, to upgrade from 183 to 184. I tried step by step (as recommended in that thread) and it was not working.

I upgraded a minute ago to version 184, from CLI but help from GUI was required. And I do not see difference in major version, it is still 2.29.

[root@ipfire ~]# pakfire status
Core-Version: 2.29-x86_64
Core-Update-Level: 184
Last update: 3m 17s ago
Last core-list update: 1h 56s ago
Last server-list update: 1h 1m 16s ago
Last packages-list update: 1h 1m 14s ago
Core-Update available: no
Package-Updates available: 6
Reboot required: yes

Packages upgraded:

[root@ipfire ~]# pakfire status
Core-Version: 2.29-x86_64
Core-Update-Level: 184
Last update: 11m 35s ago
Last core-list update: 8m 7s ago
Last server-list update: 1h 9m 34s ago
Last packages-list update: 8m 6s ago
Core-Update available: no
Package-Updates available: 0
Reboot required: yes

I have to reboot now…

I checked /srv/web/ipfire/cgi-bin/pakfire.cgi and I see it calls pakfire update --force --no-colors, that could be the difference, I used only pakfire update

IMPORTANT UPDATE

There is a problem at your servers related to pakfire updates. Some of them report version 183, others 184:

Version 183:

user@ubuntu:/tmp$ curl https://mirror.ihost.md/ipfire/pakfire2/2.27-x86_64/lists/core-list.db
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

$core_release="183";
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPsqKpEeCCLkku5Ygb+96jtcTWUsFAmX//gwACgkQb+96jtcT
WUtlmg//b6wfxo3Ev7sOpm04xXm1Kag2DpwShsl82nmxPFDnxZ/0tnQxI30PNhbZ
IioyIdkky4bl2DTRIHwDxT2f7Gx+6T337sj5ZpWlscgJSa3rHpHMobK5wDO3VkIA
C/dZdOjLRig9KEmLpL2ovx+zMCthdoCuTi38eItrzehjKwBQT6id9F6WOfK6LHI2
vkOr7kFYPdaoaUbYCtkHxaZLOri6taJG0zfENKaiFLY3pOTcmg6ubqeyOjNFcvif
xUVu9n5PkboWLnEsebxm7s1n0e9KKLTFfecFyvu/26Sh6kfzXNnF8nUK20sMKdzW
Z6NavY+eWI3WkIIyH4LWCnEYafTapZXgtk/RuEcdMvjeV0htGe4usbNMQLbQ4o9+
9IasPAdN2nNl7MrFIFv6hpflLqkauVuMSy2BbSy+PySnghe8B3A5R9nyxeJmPZU0
pYXew0Ou8u+YFq5sFaPRmu017D7BGFlKGtbafaj6rvjRwQy/OEBp8nNZ0D1hE0ru
9WTr3IcuEz8SHxLUwu9dCqfUOmJgMykAE3XMmg/pvXPXqbcrAgTEoXXMhL3O0PPu
oCxP7abNnGJA1PBbQfsEkdvYy/Ovs0C17pCWfR/7azpAhbVfOmyLNbdderRmJcAo
KU2w6TKCv0odEwUho5NIaUV+mi7kggJ0AIaij8aB/3z5c4YbOhU=
=i+uR
-----END PGP SIGNATURE-----

user@ubuntu:/tmp$ curl -I https://mirror.ihost.md/ipfire/pakfire2/2.27-x86_64/lists/core-list.db
HTTP/2 200 
etag: "387-65fffe0c-38078a7f2;;;"
last-modified: Sun, 24 Mar 2024 10:18:52 GMT
content-type: application/octet-stream
content-length: 903
accept-ranges: bytes
date: Sun, 24 Mar 2024 13:34:42 GMT
x-accelerated: +www.ihost.md
server: ihost-sws/ols
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"

Version 184:

user@ubuntu:/tmp$ curl https://mirror.marwan.ma/ipfire/pakfire2/2.29-x86_64/lists/core-list.db
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

$core_release="184";
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPsqKpEeCCLkku5Ygb+96jtcTWUsFAmYAGhYACgkQb+96jtcT
WUu/pxAAkE8Ag6aquobz39OzGIIPDu+YalIaRXcO6vXKLK2piUi5LpC9OpV8JNeo
tYgQ2UambXunT6JPAYLlHFFTo+DGWTMG6qYpHOuI3vy6Q0hlnxS/UaSYXkkNGYHR
Ho182hWpcp4lnKumd/hxmZutaUXGkS/BoyI/vVCUd/08AF4l7/6yQ2hWprIXA3Oj
6beIuNsM/Bsuuz5STYVm3q2Z61HcSPRjvFXuSiC9j2kyJd7F6eABNQ0wodzMinx7
sgqeNdg7GCzyYbwPiEBXBfE/kEo+fJK2HUFUEiYtpqGkSG2/nB2FPlElXXX7di3K
FxlD0mwZv1ezbEMh2DhjxtxHNy3RRnVtl5fUvd0HKG35XUGxd312EZJRZyT/JdJJ
Z5MUYTArjGvIe/ExInyk1TGrQ6Y5dtRXIugFnFTg5yOJLcNCdH2t8Fwg1XAThQHx
bj7AkB0YG0nu6lAs3YfK716qXfl1ggIW+55rY25NiPgmTKvski29PePXsVF2Cb0H
dtSv1D+mmaejomfwK9ZwmrmCg8+zoO0VoqrBg6btF78yFeZWVNq56PvXB9jGA5uI
vDPDKgq/ZmPXJwpLQTV5GQ663Q0LzV6tQxv3+TyhZwkMfuQ13TyLLF1gqze7e6qV
oo479RHtMc8fbCF4XjfxxQcTTappmRXA4VOkMgXZUzjHrI/pi8c=
=wMQN
-----END PGP SIGNATURE-----

user@ubuntu:/tmp$ curl -I https://mirror.marwan.ma/ipfire/pakfire2/2.29-
HTTP/2 200 
server: nginx/1.20.1
date: Sun, 24 Mar 2024 13:33:03 GMT
content-type: application/octet-stream
content-length: 903
last-modified: Sun, 24 Mar 2024 12:18:30 GMT
etag: "66001a16-387"
accept-ranges: bytes
4

That is because you are looking in different directories.

One set is major version 2.27 and the other major version 2.29

The last update in a 2.27 major version directory will be CU183 as it moved to 2.29 but was updated from 182 which was major version 2.27.
There will be no CU184 in a major version 2.27 directory.

The update for 183 to 184 will be in a major version 2.29 directory as 183 is already 2.29 going to 184 which is also 2.29

1 Like
5

I was looking to those files because I found them in log file (/var/log/messages) that pakfire was checking those… I tried to find why pakfire reported that there is no update after 183. I found the answer, pakfire was looking to a wrong directory… :wink:

Explanation is that parameter --force is important, it changes from 2.27 to 2.29, it is visible in the log here:

Mar 24 12:25:40 ipfire pakfire: MIRROR INFO: server-list.db is 44370 seconds old. - DEBUG: force
Mar 24 12:25:40 ipfire pakfire: DOWNLOAD STARTED: 2.27-x86_64/lists/server-list.db
Mar 24 12:25:40 ipfire pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.27-x86_64/lists/server-list.db
Mar 24 12:25:41 ipfire pakfire: DOWNLOAD INFO: 2.27-x86_64/lists/server-list.db has size of 2054 bytes
Mar 24 12:25:41 ipfire pakfire: DOWNLOAD INFO: Signature of server-list.db is fine.
Mar 24 12:25:41 ipfire pakfire: DOWNLOAD FINISHED: 2.27-x86_64/lists/server-list.db
Mar 24 12:33:40 ipfire pakfire: MIRROR INFO: server-list.db is 479 seconds old. - DEBUG: noforce
Mar 24 12:34:15 ipfire pakfire: MIRROR INFO: server-list.db is 514 seconds old. - DEBUG: noforce
Mar 24 12:37:31 ipfire pakfire: MIRROR INFO: server-list.db is 710 seconds old. - DEBUG: noforce
Mar 24 12:38:30 ipfire pakfire: MIRROR INFO: server-list.db is 769 seconds old. - DEBUG: noforce
Mar 24 12:39:04 ipfire pakfire: MIRROR INFO: server-list.db is 803 seconds old. - DEBUG: force
Mar 24 12:39:04 ipfire pakfire: DOWNLOAD STARTED: 2.29-x86_64/lists/server-list.db
Mar 24 12:39:04 ipfire pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.29-x86_64/lists/server-list.db
Mar 24 12:39:06 ipfire pakfire: DOWNLOAD INFO: 2.29-x86_64/lists/server-list.db has size of 2054 bytes
Mar 24 12:39:06 ipfire pakfire: DOWNLOAD INFO: Signature of server-list.db is fine.
Mar 24 12:39:06 ipfire pakfire: DOWNLOAD FINISHED: 2.29-x86_64/lists/server-list.db
1 Like