Re: CVS update fails with "Broken pipe"

[Todd Denniston]

Klaus Zeitler wrote, On 04/14/2008 03:04 AM:
> For the last few feeks I have a strange problem.
> When I try to update my CVS emacs version with "cvs update"
> nothing happens for approximately 8 min and then I get the following error:
> cvs [checkout aborted]: error writing to server: Broken pipe
>
> The first anonymous CVS checkout with
> "cvs -z3 -d:pserver:address@hidden:/sources/emacs co"
> works just fine. From then on, an update (or checkout again) command
> fails like mentioned above.
>
> Here's an example:
> $ cvs -t update
>   -> main: Session ID is wFsBDcMzUa1LMxYs
>   -> main loop with CVSROOT=/sources/emacs
>   -> open_connection_to_server (:pserver:address@hidden:/sources/emacs)
>   -> Connecting to cvs.savannah.gnu.org(199.232.41.69):2401.
>   -> rename(CVS/Entries.Backup,CVS/Entries)
>   -> unlink_file(CVS/Entries.Log)
>   -> rename(CVS/Entries.Backup,CVS/Entries)
>   -> unlink_file(CVS/Entries.Log)
>   -> rename(CVS/Entries.Backup,CVS/Entries)
>   -> unlink_file(CVS/Entries.Log)
>   -> rename(CVS/Entries.Backup,CVS/Entries)
>   -> unlink_file(CVS/Entries.Log)
>   -> rename(CVS/Entries.Backup,CVS/Entries)
>   -> unlink_file(CVS/Entries.Log)
>
> And after approx 8 minutes I get:
> cvs [update aborted]: error writing to server: Broken pipe
>
> I had used this command for more than 2 years without any problems
> and I haven't changed anything in my environment (not that I can think
> of at least).
> When I remove my emacs directory and try the checkout command,
> it works just fine. But when I now follow up with an update or
> a 2nd checkout command, I get the same 'Broken pipe' error.
>
> OS: SunOS 5.8 Generic_117350-28 sun4u
> sparc SUNW,Sun-Blade-1500 Solaris
>
> Does anybody have an idea how I can investigate this?
> I appreciate any help. Thank you
>
> Klaus


I can't check from here, so here is what I would suggest you do.
Assuming you can create another user on your machine, then do so, but don't 
put anything in that user's account that does not get put there by making the 
user.
then login as that user and do the checkout and update on the command line 
(with out using emacs).

If you get the same fault, I would expect you have one of the following 
conditions:
A) you or the machine admin changed something in the profile that is used by 
everyone, i.e., /etc/profile (or similar shell config in /etc), hope it is 
under version control so you can figure out what changed.
B) something changed at savannah; contact their administrative contact and see 
if [s]he knows what is up.

If it works, then you need to look at your account again.

Other diagnostics might include strace'ing cvs.


--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter