Linux Server Deployment svn common error handling → reprint

Reprint Address →http://blog.seweal.com/post/2013-02-04/svn-errors

"Open svn port" iptables-i input-p TCP--dport 3690-j ACCEPT  #开放3690端口/etc/rc.d/init.d/iptables save   #保存配置, very important, Save to take effect/etc/init.d/iptables status  # Check if it is successful: If prompted Iptables:command not found is not installed Iptables component, install: Yum installs Iptables

Error

A lot of people often miss a step after installing SVN is to import the project on the server side:

SVN import/home/wwwroot/public_html/   file:///data/svndata/project-m "Init"

Error

When the server side executes SVN up, it prompts for an error:

SVN up skipped '. '

The problem is that your server side is not a working copy (working copy)

How to prove it, very simple, as long as the server-side execution

SVN St

(meaning to show the current status of SVN), you will be prompted:

Svn:warning: '. ' is not a working copy

The current directory is not a working copy of SVN, so the problem is solved.

Just check it out again, note that it is checked out on the server side, not checked out at the client, (I think your client should have checked out.) ）

[[Email protected] ~]# SVN co svn://xxx.com/project your_project_dir[[email protected] ~]# CD Your_project_dir[[email Pro Tected] ~]# svn up

Where Your_project_dir is your directory, but if your order is:

[[Email protected] ~]# CD Your_project_dir[[email protected] your_project_dir]# SVN co http://xxx.com/project [email Pro Tected] your_project_dir]# svn up

is prone to skipped '. ' Errors.

Error

Method options failed on could not read status line, the remote host forced the shutdown of an existing connection.

I have ever had this error, whether the client or server side, the server refused the connection.

Check out the service is running, the port is open, also joined the Iptables

And then we found out that the path was wrong.

Svn://xxx.com/project

Was written

Http://xxx.com/project

The SVN protocol is written in the HTTP protocol, how many children have made the same mistake with me.

Linux Server Deployment svn common error handling → reprint