Date: Mon, 17 Nov 2008 16:14:39 -0500 From: jT <toyj@union.edu> To: "Jeremy Chadwick" <koitsu@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: CSUP failure Message-ID: <9f8af95f0811171314qe41077yae993ca4e9eec10e@mail.gmail.com> In-Reply-To: <20081117150530.GA32196@icarus.home.lan> References: <9f8af95f0811151550q6d4d48cfv28034e5403dde028@mail.gmail.com> <20081116023011.GA89222@icarus.home.lan> <9f8af95f0811161057r48b8c5a0k3b5c9653e25e3912@mail.gmail.com> <20081116203604.GB10691@icarus.home.lan> <9f8af95f0811161249i9419c0dn3c3473b9e2d4a42e@mail.gmail.com> <9f8af95f0811161249wb29f535vf5ac9f7ce6a1b32e@mail.gmail.com> <9f8af95f0811170658q3e09b541sf862561cab340a23@mail.gmail.com> <20081117150530.GA32196@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
All / Jeremy / Maxime, [root@bigmac ~]# csup -L 2 current-supfile Parsing supfile "current-supfile" Connecting to cvsup3.freebsd.org Connected to 128.31.0.28 Server software version: SNAP_16_1h Invalid server reply to AUTHMD5 [root@bigmac ~]# cvsup -g -L 2 -h cvsup2.us.freebsd.org current-supfile Parsing supfile "current-supfile" Connecting to cvsup2.us.freebsd.org Connected to cvsup2.us.freebsd.org Server software version: SNAP_16_1h Premature EOF from server Will retry at 16:14:29 [root@bigmac ~]# cvsup -g -L 2 -h cvsup11.us.freebsd.org current-supfile Parsing supfile "current-supfile" Connecting to cvsup11.us.freebsd.org Connected to cvsup11.us.freebsd.org Server software version: SNAP_16_1h Premature EOF from server Will retry at 16:14:56 On Mon, Nov 17, 2008 at 10:05 AM, Jeremy Chadwick <koitsu@freebsd.org> wrote: > On Mon, Nov 17, 2008 at 09:58:48AM -0500, jT wrote: >> All, >> Again after a few hours i get: >> >> [root@bigmac ~]# csup -h cvsup11.us.freebsd.org current-supfile >> Connected to 130.94.149.166 >> Invalid server reply to AUTHMD5 >> [root@bigmac ~]# >> >> This time its on cvsup11 -- this is the most bizarre behavior I have >> ever noticed. I was checking my bash_history and noted that i did a >> make makesum in nvidia-driver because I updated the version and wanted >> the new sum files. Since this was a port I have no idea how it could >> be related -- but noticed that it had to do with checksums -- could >> this have really fouled things up? And is there a solution to fix >> this? Thanks a lot. > > "make makesum" just changes the contents of the port distinfo file. > That definitely has nothing to do with the oddities you're seeing with > csup. > > Things to try that come to my mind: > > Could you provide the output of the above csup command but with -L 2 > added to the argument list? > > Next, could you try cvsup? You can add the binary as a package (it's a > "standalone" package, e.g. no runtime dependencies, so you can > pkg_delete it when you're done). This should do the trick: pkg_add -r > cvsup-without-gui. Then try using "cvsup" instead of "csup" in your > command. > > If the issue continues with cvsup, some pcaps or truss's will be needed > to figure out what's going across the wire. > > I've CC'd mux@FreeBSD.org, who is the author of csup, to help out. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > -- /jT http://git.zen-sources.org/?p=kernel/zenmm.git;a=summary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9f8af95f0811171314qe41077yae993ca4e9eec10e>