core 90 test download errors

core 90 test download errors

[Paul Simmons]

[-- Attachment #1: Type: text/plain, Size: 349 bytes --]

There appear to be only two mirrors from which I can download core 90
testing, and the download fails.  It is probably due to my (substandard)
ISP (HughesNot), but I wonder if it would succeed if there were a closer
mirror to me (USA)?

Failing that, perhaps a tweak to pakfire (enabling more or better
download retries) is in order?

Thanks!
Paul

Re: core 90 test download errors

[Rod Rodolico]

[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]

Paul,

It may not be your network connection. I have a mirror
(mirror.smartappliances.us/ipfire, if I remember right). As of right
now, it was still updating from the main IPFire server. It just takes a
while to get all the new pieces. So, it is possible you were using a
mirror that is not fully updated yet. I do bandwidth limit the sync to
keep from killing my server and the main one.

That being said, I updated my test router a couple of hours ago. Sorry,
I did not see which mirrors it used. I believe the update looks for the
least busy, but I know it doesn't look for the closest as a couple of
routers on the same subnet as my mirror have, in the past, used European
mirrors.

Unless it is your network connection, it may just be that the mirrors
you have been assigned are still updating. So, if you network connection
is good, you might just try again.

NOTE: It appears from the logs that my mirror is working on the
armv5tel, so I believe that means the i386 is completely downloaded.

Rod


On 05/09/2015 09:21 AM, Paul Simmons wrote:
> There appear to be only two mirrors from which I can download core 90
> testing, and the download fails.  It is probably due to my (substandard)
> ISP (HughesNot), but I wonder if it would succeed if there were a closer
> mirror to me (USA)?
> 
> Failing that, perhaps a tweak to pakfire (enabling more or better
> download retries) is in order?
> 
> Thanks!
> Paul
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
> 

-- 
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net

Re: core 90 test download errors

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

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

On Sat, 2015-05-09 at 09:21 -0500, Paul Simmons wrote:
> There appear to be only two mirrors from which I can download core 90
> testing, and the download fails.  It is probably due to my (substandard)
> ISP (HughesNot), but I wonder if it would succeed if there were a closer
> mirror to me (USA)?
> 
> Failing that, perhaps a tweak to pakfire (enabling more or better
> download retries) is in order?
> 
> Thanks!
> Paul
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: core 90 test download errors

[Paul Simmons]

[-- 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