2016-08-25 59 views
0

客戶端錯誤:svn:E175002:svn/xxx上的MERGE請求失敗:504 Gateway超時。無法寫入響應輸出:斷的管

svn: E175002: Commit failed (details follow): 

svn: E175002: MERGE request on '/svn/my_repos/trunk/app' failed: 504 Gateway Time-out 

Server錯誤日誌:

[Thu Aug 25 09:24:49.466833 2016] [dav:error] [pid 20669] [client 192.168.2.99:31447] Could not MERGE resource "/svn/my_repos/!svn/txn/68582-1h18" into "/svn/my_repos/trunk/app". [500, #0] 

[Thu Aug 25 09:24:49.466882 2016] [dav:error] [pid 20669] [client 192.168.2.99:31447] Error constructing resource list. [500, #32] 

[Thu Aug 25 09:24:49.466884 2016] [dav:error] [pid 20669] [client 192.168.2.99:31447] Can't write response to output: Broken pipe [500, #32] 

回答

0

在我的情況下,錯誤是由導致的post-commit svnsync的。

我改變此命令:

/usr/bin/svnsync sync --non-interactive --username svnsync --password ****** ${svn_mirror_url}

運行背景和重定向輸出和錯誤到/ dev/null的

/usr/bin/svnsync sync --non-interactive --username svnsync --password ****** ${svn_mirror_url} >/dev/null 2>/dev/null &

參考鏈接:

http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&viewType=browseAll&dsMessageId=685574#messagefocus 
http://stackoverflow.com/questions/4584904/what-causes-the-broken-pipe-error 
http://unix.stackexchange.com/questions/60222/why-does-subversion-give-a-broken-pipe-error-when-piped-into-head 
相關問題