Svn error:
Error running context : The server unexpectedly closed the connection
Error analysis:
means that the remote service has closed the connection. The inspection idea is as follows
1. view firewall firewalld&&iptables
firewall-cmd --stat
If the return is not running, firewalld is not on
iptables -nL
Check if the rule has a 3690 drop
If you have not used iptables in the environment, you can use iptables -F to clear the rules! Use with caution!
2. Check if the svn service is up
ps uax | grep svn && netstat -lnpt | grep 2690
This method is used to determine the process and port
3. If you are using nginx reverse proxy, pay attention to the configuration of tcp forwarding
Note that especially if you use IF.Svnadmin and forget to configure it
server {
listen xxx so_keepalived=on;
server_name xxx;
proxy_pass svn_server:3690;
}
There are more methods than problems. Come on!!!!
Read More:
- [Solved] GVM Error: rsync: connection unexpectedly closed & rsync: read error: Connection reset by peer (104)
- Deepin svn Error: svn: E120171: Error running context: An error occurred during SSL communication
- [Solved] Node uploads files to FTP server error: timed out while making data connection
- stream copy error: reading from a closed fifo [How to Solve]
- [Solved] Win 10 VS Code Connect to the container of the server error: Cannot connect to the Docker daemon at … Is the docker daemon running
- Install and start the tftp-server server and possible solutions to Redirecting to /bin/systemctl restart xinetd.service problems
- Git Clone RPC failed;curl 18 transfer closed with outstanding read data remaining
- [Solved] Error: Connection activation failed: No suitable device found for this connection.
- Ffmpeg about Avio_alloc_Context application for memory release
- [Solved] Module yaml error: Unexpected key in data: static_context
- [Solved] Remote Server error: Server sent passive reply with unroutable address…
- [Solved] Web server failed to start. Port 8080 was already in use.
- SSH Connect Service Error: Could not connect to ‘xxx.xxx.xx.xx‘ (port 22): Connection failed.
- [Solved] gnutls_handshake() failed: The TLS connection was non-properly terminated
- [Solved] Ubuntu Error: Failed to connect to 127.0.0.1 port xxxxx: Connection refused
- Centos6.8vnc error: connect: Connection refused 10061
- [Solved] websocket: the client is not using the websocket protocol: ‘upgrade’ token not found in ‘Connection’ head
- [Solved] Failed to connect to 127.0.0.1 port XXXX: Connection refused
- How to Solve No approve protocol error when running kettle on Linux
- [Solved] Linux error: SSH_exchange_identification: read: Connection reset by peer