Failure to report availability of Core 160 update

sky7176 · 6 October 2021 16:30

Good morning,
my ipfire does not report the presence of the update to 160.
I currently have the 159.
My hardware configuration is IPFire 2.27 (x86_64) - Core Update 159 on intel j1900.
I tried to restart, to update pakfire, but nothing I do not get the update report.

If I run this command:
pakfire update --force

I received this anser:

Giving up: There was no chance to get the file "2.27-x86_64/lists/server-list.db" from any available server.
There was an error on the way. Please fix it.
packages_list.db     100.00% |=============================>|    4.34 KB
core-list.db         100.00% |=============================>|   903.00 B

When I run this command after pakfire update --force, I received the message:

CORE ERROR: No new upgrades available. You are on release 159.

How can I do?
Thanks

bonnietwin · 6 October 2021 20:19

There should be some error messages in the logs and those might help give a clue what the issue is. Look in the System Logs and select Pakfire from the dropdown box.

I am not seeing any problems with accessing the servers so it is not a problem with the servers themselves. Here is the output from my log.

| --- | --- | --- |
|22:09:07|pakfire:|MIRROR INFO: server-list.db is 783 seconds old. - DEBUG: force|
|22:09:07|pakfire:|DOWNLOAD STARTED: 2.27-x86_64/lists/server-list.db|
|22:09:07|pakfire:|DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.27-x86_64/lists/serve r-list.db|
|22:09:07|pakfire:|DOWNLOAD INFO: 2.27-x86_64/lists/server-list.db has size of 2170 bytes|
|22:09:07|pakfire:|DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK|
|22:09:07|pakfire:|DOWNLOAD INFO: File received. Start checking signature...|
|22:09:07|pakfire:|DOWNLOAD INFO: Signature of server-list.db is fine.|
|22:09:07|pakfire:|DOWNLOAD FINISHED: 2.27-x86_64/lists/server-list.db|
|22:09:07|pakfire:|DB INFO: packages_list.db is 782 seconds old. - DEBUG: force|
|22:09:07|pakfire:|DOWNLOAD STARTED: lists/packages_list.db|
|22:09:07|pakfire:|MIRROR INFO: 23 servers found in list|
|22:09:07|pakfire:|DOWNLOAD INFO: Host: mirror.csclub.uwaterloo.ca (HTTPS) - File: ipfire/pakfire2 /2.27-x86_64/lists/packages_list.db|
|22:09:08|pakfire:|DOWNLOAD INFO: ipfire/pakfire2/2.27-x86_64/lists/packages_list.db has size of 4 418 bytes|
|22:09:09|pakfire:|DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK|
|22:09:09|pakfire:|DOWNLOAD INFO: File received. Start checking signature...|
|22:09:09|pakfire:|DOWNLOAD INFO: Signature of packages_list.db is fine.|
|22:09:09|pakfire:|DOWNLOAD FINISHED: ipfire/pakfire2/2.27-x86_64/lists/packages_list.db|
|22:09:09|pakfire:|CORE INFO: core-list.db is 784 seconds old. - DEBUG: force|
|22:09:09|pakfire:|DOWNLOAD STARTED: lists/core-list.db|
|22:09:09|pakfire:|MIRROR INFO: 23 servers found in list|
|22:09:09|pakfire:|DOWNLOAD INFO: Host: ftp.nluug.nl (HTTPS) - File: os/Linux/distr/ipfire/pakfire 2/2.27-x86_64/lists/core-list.db|
|22:09:09|pakfire:|DOWNLOAD INFO: os/Linux/distr/ipfire/pakfire2/2.27-x86_64/lists/core-list.db ha s size of 903 bytes|
|22:09:10|pakfire:|DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK|
|22:09:10|pakfire:|DOWNLOAD INFO: File received. Start checking signature...|
|22:09:10|pakfire:|DOWNLOAD INFO: Signature of core-list.db is fine.|
|22:09:10|pakfire:|DOWNLOAD FINISHED: os/Linux/distr/ipfire/pakfire2/2.27-x86_64/lists/core-list.d b|
|22:09:10|pakfire:|PAKFIRE INFO: Pakfire has finished. Closing.|````

sky7176 · 6 October 2021 21:10

Hi,
this is a my pakfire log:

23:09:28	pakfire:	PAKFIRE INFO: Pakfire has finished. Closing.
23:09:28	pakfire:	DOWNLOAD FINISHED: ipfire/pakfire2/2.25-x86_64/lists/core-list.db
23:09:28	pakfire:	DOWNLOAD INFO: Signature of core-list.db is fine.
23:09:28	pakfire:	DOWNLOAD INFO: File received. Start checking signature...
23:09:28	pakfire:	DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
23:09:27	pakfire:	DOWNLOAD INFO: ipfire/pakfire2/2.25-x86_64/lists/core-list.db has size of 903 b ytes
23:09:26	pakfire:	DOWNLOAD INFO: Host: mirror.clarkson.edu (HTTPS) - File: ipfire/pakfire2/2.25-x 86_64/lists/core-list.db
23:09:26	pakfire:	MIRROR INFO: 25 servers found in list
23:09:26	pakfire:	DOWNLOAD STARTED: lists/core-list.db
23:09:26	pakfire:	CORE INFO: core-list.db is 6217 seconds old. - DEBUG: force
23:09:26	pakfire:	DOWNLOAD FINISHED: ipfire/pakfire2/2.25-x86_64/lists/packages_list.db
23:09:26	pakfire:	DOWNLOAD INFO: Signature of packages_list.db is fine.
23:09:26	pakfire:	DOWNLOAD INFO: File received. Start checking signature...
23:09:26	pakfire:	DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
23:09:26	pakfire:	DOWNLOAD INFO: ipfire/pakfire2/2.25-x86_64/lists/packages_list.db has size of 4 441 bytes
23:09:25	pakfire:	DOWNLOAD INFO: Host: mirror.uta.edu.ec (HTTPS) - File: ipfire/pakfire2/2.25-x86 _64/lists/packages_list.db
23:09:25	pakfire:	MIRROR INFO: 25 servers found in list
23:09:25	pakfire:	DOWNLOAD STARTED: lists/packages_list.db
23:09:25	pakfire:	DB INFO: packages_list.db is 6216 seconds old. - DEBUG: force
23:09:25	pakfire:	Giving up: There was no chance to get the file 2.27-x86_64/lists/server-list.db from any available server. There was an error on the way. Please fix it.
23:09:25	pakfire:	DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can't connect to pakfire.ipfire.org: 443 (Name or service not known)
23:09:20	pakfire:	DOWNLOAD INFO: 2.27-x86_64/lists/server-list.db has size of bytes
23:09:10	pakfire:	DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.27-x86_64/lists/serve r-list.db
23:09:09	pakfire:	DOWNLOAD STARTED: 2.27-x86_64/lists/server-list.db
23:09:09	pakfire:	MIRROR INFO: server-list.db is 5901930 seconds old. - DEBUG: force
23:09:09	pakfire:	PAKFIRE INFO: IPFire Pakfire 2.27-x86_64 started!

sky7176 · 6 October 2021 21:33

I resolved in this mode:

https://community.ipfire.org/t/after-update-to-core-141-no-more-pakfire-list-available/1378/15
Michael Tremer
ms
Mar '20

    I accessed the firewall using SSH and used vim /etc/hosts to edit the hosts file.
    These are the two lines i added to get the pakfire update to work.
    81.3.27.38 pakfire.ipfire.org
    130.225.254.116 mirrors.dotsrc.org

After modify the hosts file I run:

/etc/init.d/unbound restart
pakfire update --force

and my " Available updates:" show the update file

bonnietwin · 6 October 2021 21:42

Your error message of not knowing the name pakfire.ipfire.org makes me think there is a dns problem.

The solution used overcomes that but I am not sure it is what should be done. The reason for the dns not working needs to be understood. Putting pakfire.ipfire.org into hosts is bypassing the dns problem.

What is the status of your Domain Name System wui page and the individual dns servers that are listed.

sky7176 · 6 October 2021 21:52

bonnietwin · 6 October 2021 21:59

OK, that is the problem that you need to resolve first.

Your overall status is marked as broken even though the individual dns servers status is marked as OK.

What does the System Log for “DNS: Unbound” show. There will be error messages in there that should help to understand what the problem is.

sky7176 · 6 October 2021 22:10

Ok, it seems that the problem is the resolution of the dns.
But the strange thing is that I have another ipfire, located in another city, with the same drawback.
The thing in common is that we have the same internet provider.
Now check with the manager if there is no mess about DNS name resolution, it has already happened.

For now, thanks

anon42188109 · 6 October 2021 22:48

For 8.8.8.8 and 8.8.4.4 the rDNS is dns.google

hjkl · 8 October 2021 07:05

Sir,
This simple solution you used makes my day!
I just wanted to say big thank you!!

Ps: my problem is different - 95% of countries are blocked so pakfire has some difficulties (LOL) to get the packages… I always asked myself how can I tell pakfire to use only one mirror… Now I know… Thanks!