From: Paul Simmons <redneckmother@hughes.net>
To: development@lists.ipfire.org
Subject: Re: core 90 test download errors
Date: Sun, 10 May 2015 07:27:41 -0500 [thread overview]
Message-ID: <1431260861.7117.15.camel@hughes.net> (raw)
In-Reply-To: <1431245301.31910.53.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Sun, 2015-05-10 at 10:08 +0200, Michael Tremer wrote:
> Hello Paul,
>
> can you tell us what exact error you get?
>
> We have multiple mirror servers but only use two for the testing
> releases because mirror syncing is an issue which takes sometimes a long
> time.
>
> All the mirrors are OK right now: http://mirrors.ipfire.org/
>
> Pakfire should try each mirror once. If all fail, pakfire will use the
> master mirror.
>
> -Michael
Thanks for your quick reply, Michael.
I enclose an excerpt from the terminal session, and one from the system
log.
After some experimentation, I was able to use "wget" to copy the needed
paks from mirror.lightningwirelabs.com/pub/*blah* to /var/cache/pakfire/
on the firewall and invoke the upgrade.
I am willing to continue using that method, because I understand the
constraints on mirroring. As I said, I believe the root cause is the
inadequacy of my ISP, but I have no other service available :-( . That
is the downside of "life in the boonies".
Best regards,
Paul
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: pakfire1.log --]
[-- Type: text/x-log, Size: 2557 bytes --]
14:01:52 pakfire: PAKFIRE INFO: IPFire Pakfire 2.17.1 started!
14:01:52 pakfire: CRYPTO INFO: Checking GnuPG Database
14:01:52 pakfire: CRYPTO INFO: Database is okay
14:01:52 pakfire: CORE INFO: core-list.db is 21723 seconds old. - DEBUG: force
14:01:52 pakfire: DOWNLOAD STARTED: lists/core-list.db
14:01:52 pakfire: MIRROR INFO: 2 servers found in list
14:01:53 pakfire: PING INFO: ipfire.earl-net.com is alive
14:01:53 pakfire: DOWNLOAD INFO: Host: ipfire.earl-net.com (HTTP) - File: pakfire2/2.17.1/lists/co re-list.db
14:01:56 pakfire: DOWNLOAD INFO: pakfire2/2.17.1/lists/core-list.db has size of 248 bytes
14:01:59 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
14:01:59 pakfire: DOWNLOAD INFO: File received. Start checking signature...
14:01:59 pakfire: DOWNLOAD INFO: Signature of core-list.db is fine.
14:01:59 pakfire: DOWNLOAD FINISHED: pakfire2/2.17.1/lists/core-list.db
14:01:59 pakfire: CORE UPGR: Upgrading from release 89 to 90
14:02:00 pakfire: DOWNLOAD STARTED: paks/core-upgrade-2.17-90.ipfire
14:02:00 pakfire: MIRROR INFO: 2 servers found in list
14:02:00 pakfire: PING INFO: ipfire.earl-net.com is alive
14:02:00 pakfire: DOWNLOAD INFO: Host: ipfire.earl-net.com (HTTP) - File: pakfire2/2.17.1/paks/cor e-upgrade-2.17-90.ipfire
14:02:03 pakfire: DOWNLOAD INFO: pakfire2/2.17.1/paks/core-upgrade-2.17-90.ipfire has size of 5702 0596 bytes
14:09:07 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can't read entity body: Connection re set by peer
14:09:07 pakfire: Giving up: There was no chance to get the file paks/core-upgrade-2.17-90.ipfire from any available server. There was an error on the way. Please fix it.
14:09:07 pakfire: PAKFIRE UPGR: core-upgrade-90: Decrypting...
14:09:07 pakfire: CLEANUP: tmp
14:09:07 pakfire: DOWNLOAD STARTED: paks/core-upgrade-2.17-90.ipfire
14:09:07 pakfire: MIRROR INFO: 2 servers found in list
14:09:08 pakfire: PING INFO: mirror1.ipfire.org is alive
14:09:08 pakfire: DOWNLOAD INFO: Host: mirror1.ipfire.org (HTTP) - File: pakfire2/2.17.1/paks/core -upgrade-2.17-90.ipfire
14:09:11 pakfire: DOWNLOAD INFO: pakfire2/2.17.1/paks/core-upgrade-2.17-90.ipfire has size of 5702 0596 bytes
14:16:31 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can't read entity body: Connection re set by peer
14:16:31 pakfire: Giving up: There was no chance to get the file paks/core-upgrade-2.17-90.ipfire from any available server. There was an error on the way. Please fix it.
14:16:31 pakfire: DECRYPT STARTED: core-upgrade-90
14:16:31 pakfire: DECRYPT FINISHED: core-upgrade-90 - Status: 2
[-- Attachment #3: pakfire.terminal.txt --]
[-- Type: text/plain, Size: 818 bytes --]
pakfire upgrade --force
core-list.db 100.00% |=============================>| 248.00 B
CORE UPGR: Upgrading from release 89 to 90
core-upgrade-2.17... 91.62% |==========================> | 49.82 MB
Giving up: There was no chance to get the file "paks/core-upgrade-2.17-90.ipfire" from any available server.
There was an error on the way. Please fix it.
PAKFIRE UPGR: core-upgrade-90: Decrypting...
core-upgrade-2.17... 91.16% |==========================> | 49.57 MB
Giving up: There was no chance to get the file "paks/core-upgrade-2.17-90.ipfire" from any available server.
There was an error on the way. Please fix it.
sh: /opt/pakfire/cache/core-upgrade-2.17-90.ipfire: No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
prev parent reply other threads:[~2015-05-10 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 14:21 Paul Simmons
2015-05-09 22:18 ` Rod Rodolico
2015-05-10 8:08 ` Michael Tremer
2015-05-10 12:27 ` Paul Simmons [this message]
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=1431260861.7117.15.camel@hughes.net \
--to=redneckmother@hughes.net \
--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