Re: Feedback on problems with Core Update 168 Testing

[Adolf Belka <adolf.belka@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 11698 bytes --]

Hi All,

On 11/05/2022 16:00, Adolf Belka wrote:
> Hi Leo,
>
> On 11/05/2022 15:26, Leo Hofmann wrote:
>> Hi Adolf,
>>
>> Pakfire always automatically reinstalls the current release before updating if you are in the testing branch. See this function in the Pakfire code:
> So that proves that I haven't been looking so closely on my upgrades in the past because I have never noticed that.
>> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/pakfire/lib/functions.pl;h=d4e338f23ae8ae97d6f18c6d8890d13463dc5d30;hb=refs/heads/next#l762
> Now I see it in the code. Thanks very much.
>>
>> But unfortunately this is all I can contribute, my test system updated to 168 without problems!
> Thanks for your help anyway. It's got rid of one of my questions.
>
> Just need to understand now why 2 out of 3 updates resulted in a complete loss of the interface assignments.
> Will wait to hear other inputs on this problem.
> Maybe will try running setup on the first try I had to confirm that I can re-assign the interfaces again.
>
Running setup does not help. None of the interfaces are available to be assigned to the red, green etc zones.

I checked the interfaces in the vm setup and they are as previously defined and previously working on all earlier CU's of my vm.

When rebooting I did see a fast scrolling message that seemed to say something like Invalid Kernel Argument but that is as much as I was able to see/

Regards,

Adolf.

> Regards,
> Adolf.
>
>>
>> Best regards
>> Leo
>>
>> Am 11.05.2022 um 15:11 schrieb Adolf Belka:
>>> Hi All,
>>>
>>> I have tried to update my Core Update 167 vm machine three times now (using a clone) and have had several problems so I thought I would outline what has happened for further thoughts.
>>>
>>> Normally my updates go without any real problems. This is the first time where this is not the case.
>>>
>>>
>>> First try:-
>>>
>>> After running the update, which went quite quickly, the bottom of the screen had
>>>
>>> Core Update 167 Development Build: master/c22d834c
>>>
>>> I couldn't remember if this is what is expected or not for Testing releases.
>>>
>>> Rebooted the vm and on booting a large number of error messages scrolled across the console screen. My Virtualbox terminal for IPFire has no scroll capability so I can only write on things I saw as they flew past or what was on the screen when it stopped.
>>>
>>> Lots of ipset restore error but went by too fast to get more detail.
>>>
>>> Tried to access via the WUI and no access. Tried via SSH and no access.
>>>
>>> Checked the red0 directory and there were no files present. Tried restarting red0 and got the following message
>>>
>>> starting
>>> DUID 00:04:70:........
>>> red0: interface not found
>>>
>>> So I ran ip address show and it came up with only the lo interface. No red0, green0, blue0 or orange0.
>>>
>>> Looked in bootlog and this was filled with around 4000 lines all the same
>>>
>>> Loading of module with unavailable key is rejected
>>>
>>>
>>> Second try:-
>>>
>>> This time running the update took over 10 mins.
>>>
>>> Noticed on the pakfire screen that it first ran a Core Update 167 upgrade then it ran the Core Update 168. My IPFire vm was definitely on Core Update 167.
>>>
>>> /opt/pakfire/db/core/mine contained 167 beforehand.
>>>
>>> Before doing the reboot I accessed via ssh and saw that in the /var/log/pakfire/ directory the update-core-upgrade-167 file has been updated as well as there being a 168. Both files had the same last modified date/time.
>>>
>>> Rebooted. This time everything came back up okay but the bottom of the screen now just said Core Update 167 and there was no update-core-upgrade-168 file in the pakfire directory and the 167 version was back to its date of Apr 28
>>>
>>> Repository was set back to Stable.
>>>
>>> Changed again to Testing and it said again that there was an update from 167 to 168.
>>>
>>> Before running the pakfire directory had the following
>>>
>>> -rw-r--r--  1 root root 1.8K Mar 31 23:26 update-core-upgrade-166.log
>>> -rw-r--r--  1 root root 323K Apr 28 09:47 update-core-upgrade-167.log
>>>
>>> After running it had
>>>
>>> -rw-r--r--  1 root root 1.8K Mar 31 23:26 update-core-upgrade-166.log
>>> -rw-r--r--  1 root root 604K May 11 13:24 update-core-upgrade-167.log
>>> -rw-r--r--  1 root root  175 May 11 13:24 update-core-upgrade-168.log
>>>
>>> back to Core Update 167 Development Build: master/c22d834c at bottom of screen.
>>>
>>> Rebooted.
>>>
>>> All interfaces present. Pakfire under System Status: says Core-Update-Level: 168 and the bottom of the screen showed Core Update 167 Development Build: master/c22d834c
>>>
>>> /opt/pakfire/db/core/mine has 168 in it
>>>
>>> I checked the WIO wio.pl file that had a bug fix and it was as expected for CU168.
>>>
>>>
>>> Third try:-
>>>
>>> -rw-r--r--  1 root root 323K Apr 28 09:47 update-core-upgrade-167.log
>>>
>>> Selected Testing and ran update from 167 to 168 which occurred very quickly.
>>>
>>> -rw-r--r--  1 root root 604K May 11 14:00 update-core-upgrade-167.log
>>> -rw-r--r--  1 root root  63K May 11 14:01 update-core-upgrade-168.log
>>>
>>> Here is the log file info for pakfire from messages.1.gz and messages which shows it downloading and upgrading CU167 first then doing CU168 as far as I can tell.
>>>
>>> May 11 13:59:30 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.27.1-x86_64 started!
>>> May 11 13:59:30 ipfire pakfire: CORE INFO: core-list.db is 27 seconds old. - DEBUG: noforce
>>> May 11 13:59:30 ipfire pakfire: CORE UPGR: Upgrading from release 166 to 168
>>> May 11 13:59:30 ipfire pakfire: DOWNLOAD STARTED: paks/core-upgrade-2.27-167.ipfire
>>> May 11 13:59:30 ipfire pakfire: MIRROR INFO: 2 servers found in list
>>> May 11 13:59:30 ipfire pakfire: DOWNLOAD INFO: Host: ipfire.earl-net.com (HTTPS) - File: pakfire2/2.27.1-x86_64/paks/core-upgrade-2.27-167.ipfire
>>> May 11 13:59:30 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.27.1-x86_64/paks/core-upgrade-2.27-167.ipfire has size of 71914825 bytes
>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD INFO: Signature of core-upgrade-2.27-167.ipfire is fine.
>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD FINISHED: pakfire2/2.27.1-x86_64/paks/core-upgrade-2.27-167.ipfire
>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD STARTED: meta/meta-core-upgrade-168
>>> May 11 13:59:32 ipfire pakfire: MIRROR INFO: 2 servers found in list
>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD INFO: Host: mirror1.ipfire.org (HTTPS) - File: pakfire2/2.27.1-x86_64/meta/meta-core-upgrade-168
>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.27.1-x86_64/meta/meta-core-upgrade-168 has size of 1804 bytes
>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD INFO: Signature of meta-core-upgrade-168 is fine.
>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD FINISHED: pakfire2/2.27.1-x86_64/meta/meta-core-upgrade-168
>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD STARTED: paks/core-upgrade-2.27-168.ipfire
>>> May 11 13:59:33 ipfire pakfire: MIRROR INFO: 2 servers found in list
>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD INFO: Host: ipfire.earl-net.com (HTTPS) - File: pakfire2/2.27.1-x86_64/paks/core-upgrade-2.27-168.ipfire
>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.27.1-x86_64/paks/core-upgrade-2.27-168.ipfire has size of 34355484 bytes
>>> May 11 13:59:34 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
>>> May 11 13:59:34 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
>>> May 11 13:59:34 ipfire pakfire: DOWNLOAD INFO: Signature of core-upgrade-2.27-168.ipfire is fine.
>>> May 11 13:59:34 ipfire pakfire: DOWNLOAD FINISHED: pakfire2/2.27.1-x86_64/paks/core-upgrade-2.27-168.ipfire
>>> May 11 13:59:34 ipfire pakfire: PAKFIRE UPGR: core-upgrade-167: Decrypting...
>>> May 11 13:59:34 ipfire pakfire: CLEANUP: tmp
>>> May 11 13:59:34 ipfire pakfire: DECRYPT STARTED: core-upgrade-167
>>> May 11 13:59:35 ipfire pakfire: DECRYPT FINISHED: core-upgrade-167 - Status: 0
>>> May 11 13:59:35 ipfire pakfire: PAKFIRE UPGR: core-upgrade-167: Upgrading files and running post-upgrading scripts...
>>> May 11 14:00:31 ipfire pakfire: CLEANUP: tmp
>>> May 11 14:00:31 ipfire pakfire: PAKFIRE UPGR: core-upgrade-167: Finished.
>>> May 11 14:00:31 ipfire pakfire: PAKFIRE UPGR: core-upgrade-168: Decrypting...
>>> May 11 14:00:31 ipfire pakfire: CLEANUP: tmp
>>> May 11 14:00:31 ipfire pakfire: DECRYPT STARTED: core-upgrade-168
>>> May 11 14:00:32 ipfire pakfire: DECRYPT FINISHED: core-upgrade-168 - Status: 0
>>> May 11 14:00:32 ipfire pakfire: PAKFIRE UPGR: core-upgrade-168: Upgrading files and running post-upgrading scripts...
>>>
>>>
>>> May 11 14:01:10 ipfire pakfire: CLEANUP: tmp
>>> May 11 14:01:10 ipfire pakfire: PAKFIRE UPGR: core-upgrade-168: Finished.
>>> May 11 14:01:10 ipfire pakfire: CORE INFO: core-list.db is 127 seconds old. - DEBUG: noforce
>>> May 11 14:01:10 ipfire pakfire: PAKFIRE RESV: wio: Resolving dependencies...
>>> May 11 14:01:10 ipfire pakfire: PAKFIRE UPGR: We are going to install all packages listed above.
>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD STARTED: paks/wio-1.3.2-15.ipfire
>>> May 11 14:01:10 ipfire pakfire: MIRROR INFO: 2 servers found in list
>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD INFO: Host: mirror1.ipfire.org (HTTPS) - File: pakfire2/2.27.1-x86_64/paks/wio-1.3.2-15.ipfire
>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.27.1-x86_64/paks/wio-1.3.2-15.ipfire has size of 47216 bytes
>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD INFO: Signature of wio-1.3.2-15.ipfire is fine.
>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD FINISHED: pakfire2/2.27.1-x86_64/paks/wio-1.3.2-15.ipfire
>>> May 11 14:01:10 ipfire pakfire: PAKFIRE UPGR: wio: Decrypting...
>>> May 11 14:01:10 ipfire pakfire: CLEANUP: tmp
>>> May 11 14:01:10 ipfire pakfire: DECRYPT STARTED: wio
>>> May 11 14:01:10 ipfire pakfire: DECRYPT FINISHED: wio - Status: 0
>>> May 11 14:01:10 ipfire pakfire: PAKFIRE UPGR: wio: Upgrading files and running post-upgrading scripts...
>>> May 11 14:01:11 ipfire pakfire: CLEANUP: tmp
>>> May 11 14:01:11 ipfire pakfire: PAKFIRE UPGR: wio: Finished.
>>> May 11 14:01:11 ipfire pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
>>>
>>> Rebooted
>>> Lots of ipset restore error but went by too fast to get more detail.
>>> Several repeats of the following two lines on the console screen:-
>>>
>>> iptables v1.8.7 (legacy): can't initialize iptables table `filter' : Table does not exist (do you need to insmod?)
>>> Perhaps iptables or your kernel needs to be upgraded.
>>>
>>>
>>> Only lo interface present. All other interfaces red0, green0, blue0, orange0 not present.
>>>
>>>
>>> I have given up at this point.
>>>
>>> I have kept the clones of all three attempts so if you need any additional info from logs or files just let me know.
>>>
>>> If this is something obviously wrong that I am doing, please let me know. If not then I will probably raise a bug on this.
>>>
>>> Regards,
>>>
>>> Adolf.
>>>