From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.25 core141 build and put into new 2.25 pakfire trees
Date: Thu, 06 Feb 2020 14:30:39 +0100 [thread overview]
Message-ID: <8451f0663143c440e86077d830f29f5b@ipfire.org> (raw)
In-Reply-To: <f3c7ad86-ac3f-f1d7-369b-b0f7675589bd@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 6781 bytes --]
The entry "ipfire: core-update-141: ERROR cannot update because not
enough free space on root."
should displayed on the main IPFire log section.
Arne
Am 2020-02-06 13:10, schrieb Daniel Weismüller:
> Btw. maybe we should overwork the logging of this problem.
> If I look at the pakfire logfile I can't see whats wrong.
>
> 13:02:39
> pakfire:
> PAKFIRE ERROR: Returncode: 2. Sorry. Please search our forum to
> find a solution for this problem.
>
> 13:02:36
> pakfire:
> PAKFIRE UPGR: core-upgrade-141: Upgrading files and running
> post-upgrading scri pts...
>
> 13:02:36
> pakfire:
> DECRYPT FINISHED: core-upgrade-141 - Status: 0
>
> 13:02:35
> pakfire:
> DECRYPT STARTED: core-upgrade-141
>
> 13:02:35
> pakfire:
> CLEANUP: tmp
>
> 13:02:35
> pakfire:
> PAKFIRE UPGR: core-upgrade-141: Decrypting...
>
> 13:02:35
> pakfire:
> DOWNLOAD FINISHED:
> ipfire/pakfire2/2.25-x86_64/paks/core-upgrade-2.25-141.ipfir e
>
> 13:02:35
> pakfire:
> DOWNLOAD INFO: Signature of core-upgrade-2.25-141.ipfire is fine.
>
> 13:02:35
> pakfire:
> DOWNLOAD INFO: File received. Start checking signature...
>
> 13:02:35
> pakfire:
> DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
>
> 13:02:05
> pakfire:
> DOWNLOAD INFO:
> ipfire/pakfire2/2.25-x86_64/paks/core-upgrade-2.25-141.ipfire ha s
> size of 37139755 bytes
>
> 13:02:03
> pakfire:
> DOWNLOAD INFO: Host: mirror.csclub.uwaterloo.ca (HTTPS) - File:
> ipfire/pakfire2 /2.25-x86_64/paks/core-upgrade-2.25-141.ipfire
>
> 13:02:03
> pakfire:
> MIRROR INFO: 23 servers found in list
>
> 13:02:03
> pakfire:
> DOWNLOAD STARTED: paks/core-upgrade-2.25-141.ipfire
>
> 13:02:03
> pakfire:
> CORE UPGR: Upgrading from release 140 to 141
>
> 13:02:03
> pakfire:
> DOWNLOAD FINISHED: pakfire2/2.25-x86_64/lists/core-list.db
>
> 13:02:03
> pakfire:
> DOWNLOAD INFO: Signature of core-list.db is fine.
>
> 13:02:03
> pakfire:
> DOWNLOAD INFO: File received. Start checking signature...
>
> 13:02:03
> pakfire:
> DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
>
> 13:02:03
> pakfire:
> DOWNLOAD INFO: pakfire2/2.25-x86_64/lists/core-list.db has size of
> 903 bytes
>
> 13:02:03
> pakfire:
> DOWNLOAD INFO: Host: ipfire-mirror.eissler.pro (HTTPS) - File:
> pakfire2/2.25-x8 6_64/lists/core-list.db
>
> 13:02:03
> pakfire:
> MIRROR INFO: 23 servers found in list
>
> 13:02:03
> pakfire:
> DOWNLOAD STARTED: lists/core-list.db
>
> 13:02:03
> pakfire:
> CORE INFO: core-list.db is 31857 seconds old. - DEBUG: force
>
> 13:02:03
> pakfire:
> PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
>
> Contrary to the console where I'm able to read the complete outpunt.
>
> Message from syslogd(a)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.
>
> Am 06.02.20 um 12:25 schrieb Michael Tremer:
>
>> Hi,
>>
>> On 6 Feb 2020, at 11:23, Daniel Weismüller
>> <daniel.weismueller(a)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(a)ipfire.org> wrote:
>>
>> Hi
>>
>> I've tried to upgrade to core 141 but I got an error.
>>
>> [root(a)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(a)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(a)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(a)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
next parent reply other threads:[~2020-02-06 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f3c7ad86-ac3f-f1d7-369b-b0f7675589bd@ipfire.org>
2020-02-06 13:30 ` Arne Fitzenreiter [this message]
2020-02-07 14:37 ` Michael Tremer
2020-02-07 15:18 ` Tom Rymes
2020-02-07 15:36 ` Michael Tremer
[not found] <e23b18138732dc26f1ffe3239e9a3451@ipfire.org>
2020-02-06 10:47 ` Michael Tremer
2020-02-04 18:05 Arne Fitzenreiter
2020-02-04 18:15 ` Stefan Schantl
2020-02-05 10:18 ` Michael Tremer
2020-02-05 12:26 ` Daniel Weismüller
2020-02-05 13:50 ` Michael Tremer
2020-02-06 11:23 ` Daniel Weismüller
2020-02-06 11:25 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8451f0663143c440e86077d830f29f5b@ipfire.org \
--to=arne_f@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox