trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: May 2012

Re: [trinity-users] *still* 404s on nightly builds

From: Marvin L Jones <trinity@...>
Date: Fri, 25 May 2012 13:43:52 -0600 (MDT)
On Fri, 25 May 2012, Dexter Filmore wrote:

>
>... and I removed precise-security and updates. Still gives me this:
>
>Mirroring to /mnt/media/trinity from
>http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ubuntu/
>Arches: amd64
>Dists: precise
>Sections: main,restricted,universe,multiverse
>Pdiff mode: use
>Will clean up after mirroring.
>Attempting to get lock ...
>Updating remote trace files (using rsync) ...
>sending incremental file list
>rsync:
>change_dir "/mnt/media/trinity//ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds::ubuntu"
>failed: No such file or directory (2)
>
>sent 12 bytes  received 12 bytes  48.00 bytes/sec
>total size is 0  speedup is 0.00
>rsync error: some files/attrs were not transferred (see previous errors) (code
>23) at main.c(1070) [sender=3.0.9]
>Warning: failed to use rsync to download extra files.
>Getting meta files ...
>[  0%] Getting: dists/precise/Release... 	 #** GET
>http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ubuntu/dists/precise/Release
>==> 301 Moved Permanently (8s)
>** GET
>http://ppa2.quickbuild.pearsoncomputing.net/redirect.php?file=trinity-nightly-builds/ubuntu/dists/precise/Release
>==> 500 Status read failed: Connection reset by peer (16s)
>failed 500 Status read failed: Connection reset by peer
>Errors:
> Download of dists/precise/Release failed: 500 Status read failed: Connection
>reset by peer
>Failed to download some Release or Release.gpg files!
>WARNING: releasing 1 pending lock...
>
>
>What does the 301 message mean and why do I get the reset-by-peer?

A 301 is a URL REDIRECT by the other end -- responding to your request
by telling the program on your end to go to a different URL.

Just guessing here: "...and why do I get the reset-by-peer?" The
software on your end may not be honoring 301 ReDirects (probably for
'security' reasons).  There may be an optional parameter setting to tell
it to follow a 301 ReDirect.

But, the 500 error code is probably the Big Problem here.  It could be
the 301 ReDirect is re-directing to ITSELF!  Again, just a guess...

HTH,
Jonesy
-- 
  Marvin L Jones     | jonz         | W3DHJ  |  linux
   Pueblo, Colorado  |  @           | Jonesy |   OS/2     __
    38.238N 104.547W |   config.com | DM78rf |            SK