I have installed IPFire core 172 on IPFire Mini Appliance, but something seems to block outgoing requests: ping reports normal delays (a few ms) a few times, but then one or two very long delays occur (several hundreds or a few thousands ms). The same delay occur when browing. It does not seem to be related to DNS lookup, as I get similar delays when I ping a known IP address.
I tried to update to core 182, but the update does not work. Under “Packfire Configuration”, under “Available updates” there is one line:
Core-Update --2.27 -x86_64 – Release: 172 → 182
but it is greyed out. What is the likely problem here?
What do you mean by ‘it is greyed out’?
If there is some Core Update mentioned in the right box, you can apply this update by clicking the button at the bottom of the box.
Feb 11 22:07:10 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.27-x86_64 started!
Feb 11 22:07:10 ipfire pakfire: CORE INFO: Checking for Core-Updates…
Feb 11 22:07:10 ipfire pakfire: CORE INFO: core-list.db is 20076 seconds old. - DEBUG: force
Feb 11 22:07:10 ipfire pakfire: DOWNLOAD STARTED: lists/core-list.db
Feb 11 22:07:10 ipfire pakfire: MIRROR INFO: 20 servers found in list
Feb 11 22:07:10 ipfire pakfire: DOWNLOAD INFO: Host: mirror.clarkson.edu (HTTPS) - File: ipfire/pakfire2/2.27-x86_64/lists/core-list.db
Feb 11 22:07:27 ipfire pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.27-x86_64/lists/core-list.db has size of bytes
Feb 11 22:07:44 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can’t connect to mirror.clarkson.edu:443 (Name or service not known)
Feb 11 22:07:44 ipfire pakfire: Giving up: There was no chance to get the file lists/core-list.db from any available server. There was an error on the way. Please fix it.
Feb 11 22:07:45 ipfire pakfire: CORE UPGR: Upgrading from release 172 to 182
Feb 11 22:07:45 ipfire pakfire: DOWNLOAD STARTED: meta/meta-core-upgrade-174
Feb 11 22:07:45 ipfire pakfire: MIRROR INFO: 20 servers found in list
Feb 11 22:07:45 ipfire pakfire: DOWNLOAD INFO: Host: firemirror.scp-systems.ch (HTTPS) - File: pakfire2/2.27-x86_64/meta/meta-core-upgrade-174
Feb 11 22:07:45 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.27-x86_64/meta/meta-core-upgrade-174 has size of bytes
Feb 11 22:07:45 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can’t connect to firemirror.scp-systems.ch:443 (Name or service not known)
Feb 11 22:07:45 ipfire pakfire: Giving up: There was no chance to get the file meta/meta-core-upgrade-174 from any available server. There was an error on the way. Please fix it.
Feb 11 22:07:45 ipfire pakfire: PAKFIRE ERROR: Unable to retrieve core-upgrade-174 metadata.
Feb 11 22:07:45 ipfire pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
Upgrading over 11 releases would take a long time, involving several reboots. There might also have been a change in partitioning schema, within those releases and that would leave you with a non-viable size for /boot.
You would do better to backup core 172 and save the backup to your workstation. Then do a fresh install at (say) core 181. After which you could check that upgrade to core 182 proceeds.
BTW: nevermind about the line Feb 11 22:07:27 ipfire pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.27-x86_64/lists/core-list.db has size of bytes. It is a small ‘anomaly’. The message following ( Feb 11 22:07:44 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can’t connect to mirror.clarkson.edu:443 (Name or service not known ) shows the real error.
I placed the core-list.db on the USB stick and it seems an upgrade was started but failed:
Feb 12 01:09:01 ipfire pakfire: DOWNLOAD ERROR: The downloaded file (sites/downloads.ipfire.org/pakfire2/2.27-x86_64/paks/core-upgrade-2.27-174.ipfire) wasn’t verified by IPFire.org. Sorry - Exiting…
Is there a way to completely erase IPFIRE-MINI-EU-R1 and start anew?
A new installation should be possible just as described in the wiki.
The installation process wipes the hard disk fully, regardless whether the contents is a IPFire system, any other Linux, Windows, …
But I fear the DNS problems remain, if the the new system is configured according to the ‘old’ CU 172.
It is necessary that the serial interface speed for the mini appliance ( a PCEngines APU board ) matches the IPFire configuration ( 115200 Baud ).
Also the boot sequence has to been set to ‘USB first’ ( see e.g. https://pcengines.ch/pdf/apu2.pdf ).
I downloaded ipfire-2.27-core181-x86_64 and copied it onto a new USB stick:
sudo dd bs=4M if=/home/sg/ipfire-2.27-core181-x86_64.iso of=/dev/sdc status=progress oflag=sync
I can get into the boot menu on IPFIRE-MINI-EU-R1 by pressing F10, but the menu is a bit jumbled; can it be realated to mu serial connection?
sudo screen /dev/ttyUSB0 115200
Anyway, pressing seems to get things started but it then hangs. Any suggestions?
Yes, if you use serial connection, just scroll down to “SSeerriiall cconsole…”
and it should work much smoother.
I usually choose the “Unattended installation” option
The jumbled words is is a very common , but no worries, I think everyone gets that one
I am curious, what hardware appliance or board are you using?
