From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Titjen To: development@lists.ipfire.org Subject: RE: PFire 2.21 Date: Thu, 28 Jun 2018 21:51:56 +0100 Message-ID: <001201d40f21$d9ec33a0$8dc49ae0$@ministc.com> In-Reply-To: <8987a19707614c9fd4c4a0c88beb176d60c2d7c0.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8594218362618108516==" List-Id: --===============8594218362618108516== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, Sorry no logfiles as I just reloaded 2.21 from the nightly build. So all his= tory in old partitions is lost. If the upgrade from 2.19 120 has been ok wit= h other machines then my experience may have been a one off. I am not overly= confident of the BIOS of this machine I have either. As for 2.21 - running well=20 CPU usage is as expected. Response is fast no issues. OpenVPN running for r= oad warrior connections and no issues there. If any oddities come up I will = report. The backup issue is tricky. Even if you make it right before the upgrade it w= ould still contain the conf for apache in this case with the php enabled. Th= e upgrade would then remove the php reference but of course if for any reason= you needed to restore then it will come back and web GUI would not restart. Because of your release a few upgrades ago I knew php was going so was relat= ively quick to spot the fix I needed to do. I had enabled the SSH server befo= re web GUI was lost and could fix. My lesson is backup before upgrade - and then again after upgrade labelling t= hem with the release #. Maybe it is prudent to mention anything in release n= otes that might affect web GUI. Regards, Paul -----Original Message----- From: Michael Tremer =20 Sent: 28 June 2018 11:41 To: Peter M=C3=BCller ; Paul Titjen Cc: development(a)lists.ipfire.org Subject: Re: PFire 2.21 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, On Wed, 2018-06-27 at 23:07 +0200, Peter M=C3=BCller wrote: > Hello Paul, >=20 > this is the right place. Testing reports are always welcome. :-) >=20 > A crashing grub does not sound so good - especially if a firewall=20 > machine is physical unreachable and no remote KVM console or similar=20 > is available. >=20 > The 2.12 release was split up in two parts (one includes the new=20 > kernel, firmware files are in the second) and as far as I am aware,=20 > both should installed before rebooting. Yes, you should install both in one go and then reboot. Pakfire should not re= ally allow you to only install one. > > This may be my machine as I had used a live parted in the past to=20 > > make a properly useful size var partition. >=20 > I did not get this. Changing the partition layout should not create any problems, because... > @Core developers: Are we changing partition layout on existing=20 > installations (enlarge /boot, drop /var)? ... once the system is installed we never change any partition layout and bas= ically don't about it. @Paul: Do you have any log files or so that can be useful to find out what we= nt wrong here? > Yes, restoring too old backup files causes trouble. IPFire creates a=20 > new backup before running a core upgrade, but if this fails, it is=20 > hard to recover it. So better create a fresh backup before updating to=20 > 2.21. Should we include this in the release notes? Pakfire automatically creates one. But people of course have to download that= from the system. > Any observations after running on 2.21 (faster/slower/unstable/...)? Best, - -Michael >=20 > Thanks, and best regards, > Peter M=C3=BCller >=20 >=20 > > Dear all, > >=20 > > =20 > >=20 > > Hopefully I am in the right place to report on 2.21 > >=20 > > Just in case not - a quick summary > >=20 > > Moved to testing from stable 120. > >=20 > > Pakfire upgraded first to 121 - no reboot suggested. > >=20 > > Pakfire upgraded next to 2.21 - This time reboot required. > >=20 > > =20 > >=20 > > Reboot failed with a broken grub. I could not fix this with the=20 > > manual grub commands to get ipfire running at all so could not=20 > > rewrite grub from a running system. > >=20 > > This may be my machine as I had used a live parted in the past to=20 > > make a properly useful size var partition. > >=20 > > =20 > >=20 > > Bit the bullet and downloaded nightly build of 2.21 and reinstalled=20 > > a clean ipfire. > >=20 > > So far so good. > >=20 > > =20 > >=20 > > Only one comment about restoring previous settings from a backup. > >=20 > > My backup was old and from a time when php was supported. After=20 > > restoring the backup a surprise was in store the next time apache=20 > > web interface was restarted. Apache failed as there is a reference=20 > > in the conf files from backup to load php so extension. > >=20 > > Commenting out the line fixes it of course. Just thought I would=20 > > mention that restoring backups from a version prior to the latest=20 > > may have issues as features start to get expired. > >=20 > > =20 > >=20 > > By the way I really admire the stuff you do and a donation is en-route.=20 > >=20 > > =20 > >=20 > > Regards, > >=20 > > Paul > >=20 > > =20 > >=20 > > =20 > >=20 > >=20 > >=20 > > =20 > >=20 > >=20 >=20 >=20 -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAls0u0oACgkQgHnw/2+Q CQea5RAAlwmc2rNnuAO5vjeKkQRpRy2HqPrP3awFP/aCXMEiKHL5sSHCbMiuR/nF tPaINsZPOCtTX4amaKCdy+5/XU0mtahnFcP1DtHvCDhByEQ6o/xSCVuMmGOx5gZQ 8n/IUHGgL9z4WTAM2pDUdIoOQlOIlXAU+4DZyPAaXoccAF5nHRRX7CSm7QfymcW9 Kes/Gm8QuJzW5oAj4TsPW1UUN9QF3qd3LzsINdyfCDKDZTLfwlgpoEZSWe36LzQp jTVVVBZJpzJxs2O5hZ34hZXXl8GzkaL+oOpeuwFgAneydPhT9Qe4HjjTzNT2dAC1 GsjBRGXPwSC7s4qqTmiEwPRVopEAarEZBPEYU6KwW1Mhh72xAxi+lPqmges5S6M8 9V7zwUqkgOTsItJLqiRvW+pLj2cgSJ3lKvP2hTyS+YWaTm01xJ9Y/PleqXsK4r+T B7U04EwRULiTkSVJqI4metGVKLHdee3zAvBRFtkyNITzIT+FGBiF5xEArh5JQPiq W/pgGKRJ2pJylzTL9jU8eJ26go53RB8i9VVac6hDPl3N6n0/tXNkAWJrToCJHibW FMPXBngRofWpTcfumphYKCmu1RyruMO76qgUKq1deHAJkER9jULs3OnkWd2K3r+A 0H2JUp2COUH188FMfEo7kyYodZ9ZO3cYaNVe5n1vehJe/ubnVGQ=3D =3DPYHD -----END PGP SIGNATURE----- --===============8594218362618108516==--