Btw. maybe we should overwork the logging of this problem.
If I look at the pakfire logfile I can't see whats wrong.

Contrary to the console where I'm able to read the complete outpunt.

Message from syslogd@ipfire at Wed Feb  5 11:16:00 2020 ...
ipfire ipfire: core-update-141: ERROR cannot update because not enough free space on root.
PAKFIRE ERROR: Returncode: 2. Sorry. Please search our forum to find a solution for this problem.

Hi,

On 6 Feb 2020, at 11:23, Daniel Weismüller <daniel.weismueller@ipfire.org> wrote:


Am 05.02.20 um 14:50 schrieb Michael Tremer:

On 5 Feb 2020, at 12:26, Daniel Weismüller <daniel.weismueller@ipfire.org> wrote:

Hi

I've tried to upgrade to core 141 but I got an error.

[root@ipfire ~]# pakfire upgrade
CORE UPGR: Upgrading from release 139 to 141
meta-core-upgrade... 100.00% |=============================>| 994.00 B
core-upgrade-2.25... 100.00% |=============================>|    3.48 KB
meta-core-upgrade... 100.00% |=============================>| 997.00 B
core-upgrade-2.25... 100.00% |=============================>| 35.42 MB
PAKFIRE UPGR: core-upgrade-140: Decrypting...
PAKFIRE UPGR: core-upgrade-140: Upgrading files and running post-upgrading scripts...
PAKFIRE UPGR: core-upgrade-140: Finished.

PAKFIRE UPGR: core-upgrade-141: Decrypting...
PAKFIRE UPGR: core-upgrade-141: Upgrading files and running post-upgrading scripts...

Message from syslogd@ipfire at Wed Feb  5 11:16:00 2020 ...
ipfire ipfire: core-update-141: ERROR cannot update because not enough free space on root.
PAKFIRE ERROR: Returncode: 2. Sorry. Please search our forum to find a solution for this problem.
[root@ipfire ~]# df
Filesystem     1K-blocks      Used Available Use% Mounted on
devtmpfs         4010228         4   4010224   1% /dev
shm               262144        12    262132   1% /dev/shm
tmpfs            4053012       736   4052276   1% /run
/dev/sda3        1998672   1759992    117440  94% /
/dev/sda1          60400     29232     26584  53% /boot
/dev/sda4      381285708 190566412 171328012  53% /var
/var/lock           8192        12      8180   1% /var/lock
none             4053012        32   4052980   1% /var/log/vnstat
none             4053012     48768   4004244   2% /var/log/rrd
[root@ipfire ~]#


At first thanks for the implementation of the of the check if there is enough disc space before upgrading!

But what should I do now?

Reinstall or remove some addons?

Ok so I'm out of testing for a while because I have to reinstall both of my machines.

Just uninstall Qemu (that should be enough), then update and install Qemu again.

You will survive the 10 minutes without your VMs running.

-Michael

On both machine I use Libvirt/Qemu. I know this is a huge add-on so I'm one of the earliest which have to reinstall IPfire but I think not the only one.
So we have to think about how we could tell our community that all machines with an installation version older than core xxx have to be reinstalled because their root will run out of space.

-

Daniel

Am 04.02.20 um 19:15 schrieb Stefan Schantl:

Hello Arne,

thanks for your hint. I've reinstalled core 141 for the latest changes
on my dad's IPFire with PPPoE dialin and so far everything runs smooth.

No problems during reboot or any kind of DNS issue.

Best regards,

-Stefan

Hi

i have build IPFire core141 after some late changes and put the
images
in my people folder and
the updates to pakfire 2.25 trees for testing.
Because the critical dns changes i have not put into the 2.23.1
testing
trees yet. I hope i can do this
after some feedback. So please help testing.

Make sure your installations are on core139 before change the tree
from
2.23(.1) to 2.25 for updater testing!

Arne