Hello,
I just upgraded subversion to v1.2.0 on our server which is a Win2000 system
running Cygwin. I realize this is not really the best choice for a svn server,
but it is what I have for now. All of my repositories are fsfs and we are using
svn+ssh for client access. I applied the svn updrade last Tuesday without any
problems until today. I also know that there was some software updates applied
to the Win2000 server over the weekend.
One of our developers was trying to checkout a full repository on a Linux
client, also recently upgraded to svn v1.2.0. Part way through transfering
files he would get a "svn: Connection closed unexpectedly" error message.
I could not find any other error messages on the server, so I logged in as
the same user on the server and attempted a local checkout. I also noticed that
there was a svnserve.exe.stackdump file in his home directory. I did the same
checkout in both his home directory and mine which both resulted in
"Segmentation fault (core dumped)" at the same file.
But then I chdir'ed to the directory where the last file was added to the
working copy, did 'svn cleanup' and 'svn update'. Then the rest of the files
under that path were updated. So, I went back to the root of the working copy
and did the cleanup and update again. More files were add to the W/C, but it
eventually core dumped again. I repeated this process several times until the
repository was current in the W/C.
I then had our developer do a similar process from his Linux account and we
eventually got his W/C up to date.
I also did a 'svnadmin verify' on the repository and all the revisions were
verified successfully.
Does anyone have any idea why svn.exe/svnserve.exe might be getting
Segmentation faults?
Thanks,
Matthew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 21 00:57:26 2005