From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Feedback on problems with Core Update 168 Testing Date: Wed, 11 May 2022 21:08:08 +0200 Message-ID: <9b302f4a-9335-fbd9-9083-ead20a61e872@ipfire.org> In-Reply-To: <64D90667-4C2C-4D88-A1D5-D6F961F212AB@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3616846745667418837==" List-Id: --===============3616846745667418837== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All, On 11/05/2022 20:48, Jon Murphy wrote: > I just did an update from CU 167 (stable) to CU 168 (testing) and I got the= same build info: >=20 > *IPFire 2.27 (x86_64) - Core Update 167 Development Build: master/c22d834c* >=20 > Shouldn=E2=80=99t this be Core Update 168? That was what I thought but I couldn't precisely remember what it was in the = past with Testing Releases. I then downloaded the Core 168 iso from the nightlies build of master/latest/= x86_64 and did an install on the First attempt vm. I got to the stage of entering the root and admin passwords. Entered what I u= sually do for the vm's and after pressing OK on the admin password screen I g= ot as message box saying "Problem setting IPFire 'admin' user password". I pr= essed the OK button and got another message box saying "Initial setup was not= entirely complete. You must ensure that Setup is properly finished by runnin= g setup again at the shell.". Pressing the OK button on that message box caus= es setup to restart but again after entering a valid admin password twice I g= ot the same "Problem setting IPFire 'admin' user password" message box. I then tried installing CU168 from the same iso onto a clone of my running CU= 167 vm. Same result with "Problem setting IPFire 'admin' user password" messa= ge box. Then I created a completely new vm from scratch and tried installing CU168 Te= sting iso and again got "Problem setting IPFire 'admin' user password" messag= e box. Don't know if this is related to the problem with the missing interfaces but = if not then it is another problem. I think I am going to raise a bug on this. Regards, Adolf. >=20 > Jon >=20 >=20 >> On May 11, 2022, at 9:19 AM, Adolf Belka > wrote: >> >> 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 updat= ing 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 t= he past because I have never noticed that. >>>> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dsrc/pakfire/lib/= functions.pl;h=3Dd4e338f23ae8ae97d6f18c6d8890d13463dc5d30;hb=3Drefs/heads/nex= t#l762 >>> Now I see it in the code. Thanks very much. >>>> >>>> But unfortunately this is all I can contribute, my test system updated t= o 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 as= signed to the red, green etc zones. >> >> I checked the interfaces in the vm setup and they are as previously define= d and previously working on all earlier CU's of my vm. >> >> When rebooting I did see a fast scrolling message that seemed to say somet= hing 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 (u= sing 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 tim= e where this is not the case. >>>>> >>>>> >>>>> First try:- >>>>> >>>>> After running the update, which went quite quickly, the bottom of the s= creen had >>>>> >>>>> Core Update 167 Development Build: master/c22d834c >>>>> >>>>> I couldn't remember if this is what is expected or not for Testing rele= ases. >>>>> >>>>> Rebooted the vm and on booting a large number of error messages scrolle= d 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 resta= rting 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 sa= me >>>>> >>>>> 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 upgra= de then it ran the Core Update 168. My IPFire vm was definitely on Core Updat= e 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 Ap= r 28 >>>>> >>>>> Repository was set back to Stable. >>>>> >>>>> Changed again to Testing and it said again that there was an update fro= m 167 to 168. >>>>> >>>>> Before running the pakfire directory had the following >>>>> >>>>> -rw-r--r--=C2=A0 1 root root 1.8K Mar 31 23:26 update-core-upgrade-166.= log >>>>> -rw-r--r--=C2=A0 1 root root 323K Apr 28 09:47 update-core-upgrade-167.= log >>>>> >>>>> After running it had >>>>> >>>>> -rw-r--r--=C2=A0 1 root root 1.8K Mar 31 23:26 update-core-upgrade-166.= log >>>>> -rw-r--r--=C2=A0 1 root root 604K May 11 13:24 update-core-upgrade-167.= log >>>>> -rw-r--r--=C2=A0 1 root root=C2=A0 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-L= evel: 168 and the bottom of the screen showed Core Update 167 Development Bui= ld: 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--=C2=A0 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 qui= ckly. >>>>> >>>>> -rw-r--r--=C2=A0 1 root root 604K May 11 14:00 update-core-upgrade-167.= log >>>>> -rw-r--r--=C2=A0 1 root root=C2=A0 63K May 11 14:01 update-core-upgrade= -168.log >>>>> >>>>> Here is the log file info for pakfire from messages.1.gz and messages w= hich shows it downloading and upgrading CU167 first then doing CU168 as far a= s 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 o= ld. - DEBUG: noforce >>>>> May 11 13:59:30 ipfire pakfire: CORE UPGR: Upgrading from release 166 t= o 168 >>>>> May 11 13:59:30 ipfire pakfire: DOWNLOAD STARTED: paks/core-upgrade-2.2= 7-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.co= m (HTTPS) - File: pakfire2/2.27.1-x86_64/paks/c= ore-upgrade-2.27-167.ipfire >>>>> May 11 13:59:30 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.27.1-x86_64/p= aks/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 che= cking signature... >>>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD INFO: Signature of core-upgrad= e-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-upgrad= e-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/met= a-core-upgrade-168 >>>>> May 11 13:59:32 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.27.1-x86_64/m= eta/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 che= cking signature... >>>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD INFO: Signature of meta-core-u= pgrade-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.2= 7-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.co= m (HTTPS) - File: pakfire2/2.27.1-x86_64/paks/c= ore-upgrade-2.27-168.ipfire >>>>> May 11 13:59:33 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.27.1-x86_64/p= aks/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 che= cking signature... >>>>> May 11 13:59:34 ipfire pakfire: DOWNLOAD INFO: Signature of core-upgrad= e-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: Decrypt= ing... >>>>> 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 - St= atus: 0 >>>>> May 11 13:59:35 ipfire pakfire: PAKFIRE UPGR: core-upgrade-167: Upgradi= ng 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: Finishe= d. >>>>> May 11 14:00:31 ipfire pakfire: PAKFIRE UPGR: core-upgrade-168: Decrypt= ing... >>>>> 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 - St= atus: 0 >>>>> May 11 14:00:32 ipfire pakfire: PAKFIRE UPGR: core-upgrade-168: Upgradi= ng 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: Finishe= d. >>>>> 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 dependenci= es... >>>>> May 11 14:01:10 ipfire pakfire: PAKFIRE UPGR: We are going to install a= ll packages listed above. >>>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD STARTED: paks/wio-1.3.2-15.ipf= ire >>>>> 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/p= aks/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 che= cking signature... >>>>> May 11 14:01:10 ipfire pakfire: DOWNLOAD INFO: Signature of wio-1.3.2-1= 5.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. Clo= sing. >>>>> >>>>> 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' : Ta= ble 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, or= ange0 not present. >>>>> >>>>> >>>>> I have given up at this point. >>>>> >>>>> I have kept the clones of all three attempts so if you need any additio= nal info from logs or files just let me know. >>>>> >>>>> If this is something obviously wrong that I am doing, please let me kno= w. If not then I will probably raise a bug on this. >>>>> >>>>> Regards, >>>>> >>>>> Adolf. >>>>> >=20 --===============3616846745667418837==--