What does the subversion error "Could not read status line" mean?

Question

This is a fairly basic question, but it is driving me nuts. I have set up a brand new repository at beanstalk.com. They give me the url, http://my_name.svn.beanstalkapp.com/blog. They also automatically create the tag, trunk and branches folder in the repository. I have checked out the trunk folder and used

svn add

to add the new file. I am trying to do my first commit, but I get this error:

Commit failed (details follow):
CHECKOUT of '/foo/!svn/bln/1': Could not read status line: 
connection was closed by server. (http://user_name@my_name.svn.beanstalkapp.com)

What does this mean, and what causes it? I have googled for a definition of what "Could not read status line" means, but was unable to find anything explaining it.

edit: I was getting this error while trying to manipulate my repository from behind a firewall. I still don't know what was causing it, but I don't have this problem at home. Strangeness.

Answer 1

Don't think that the question is an exact duplicate. Simply because the error message has some slight differences -- 'CHECKOUT' vs 'OPTIONS' -- and they arose from different subversion tasks -- a commit vs an update.

I myself am facing this problem and have been scouring the web for an answer.

Answer 2

i had same issue.. until i remebered i needed https at front

Answer 3

so what is the solution? i have the same exact problem

Answer 4

so what is the solution? i have the same exact problem

Answer 5

Hi, I also had the same problem when I typed the wrong URL:

Bad behavior: $ svn list https://zh3.beanstalkapp.com/repo

To fix the problem, the URL should be: zh3.svn.beanstalkapp.com/repo

(Hmm, I was expecting "bad URL" or something like that.

Hmm, I would type the correct URL above, but this stupid stackoverflow says: "We're sorry, but as a spam prevention mechanism, new users can only post a maximum of one hyperlink. Earn 10 reputation to post more hyperlinks." )

• JDB

Answer 6

I'm having this problem as well, but only on older checked-out repositories. On something checked out recently it works fine.