哈德森 svnkit SSL
我正在将 Hudson CI 服务器与托管在 Subversion 上的项目（或作业）一起使用。我正在通过 SSL 连接到 Subversion 服务器。
一切都工作正常，Hudson 可以从 subversion 更新，构建，没有任何问题。
就在今天，哈德森停止检查颠覆方面的重大变化。当有很多更改时，Hudson 将从 SVN 开始更新，然后给出此错误：
ERROR: Failed to update https://myserver:8443/svn/myproject/trunk
org.tmatesoft.svn.core.SVNException: svn: 错误记录 MAC
svn: '/svn/CTPN/!svn/vcc 上的 REPORT 请求失败/默认' 并在错误堆栈中
Caused by: javax.net.ssl.SSLException: bad record MAC at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
并且它将每 10 秒尝试一次，并且永远持续下去。它发生在我们正在使用的两台 Hudson 服务器的同一天，
它适用于小更新，但是当它是大更新时，它会给出此错误，
请问有什么反馈吗？
I am using Hudson CI server with a project (or job) that is hosted on Subversion. I am connecting to a Subversion server over SSL.
Everything was working fine, and Hudson can update from subversion, build and there was no problem.
And just today, Hudson stopped checking out big changes on subversion. When there are lots of changes, Hudson, will start update from SVN, and then it gives this error:
ERROR: Failed to update https://myserver:8443/svn/myproject/trunk
org.tmatesoft.svn.core.SVNException: svn: bad record MAC
svn: REPORT request failed on '/svn/CTPN/!svn/vcc/default'
and in the error stack
Caused by: javax.net.ssl.SSLException: bad record MAC at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
and it will try every 10 seconds, and goes forever. It happened on the same day on two Hudson servers we are using
It is working for small update, but when it is large update it gives this error
any feedback please?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
尝试通过 wget 获取存储库的 url。
Try to fetch the url of the repos via wget.
问题解决了。
我们转移到另一台服务器，并且运行良好。
管理员认为Hudson服务器和svn之间要么存在网络问题，要么存在容量问题。
Hudson服务器已满，但错误消息是网络一。
难道是svn插件有一个bug，当容量出现问题时，会生成网络？
因为它在巨额结帐时出错？
The problem was solved.
We moved to another server, and it worked fine.
the admin guy thinks that either there is network problem that is not consistent between the hudson server and svn, or there was a capacity issue.
The hudson server was full, but the error message was network one.
could it be that there is a bug in svn plugin that when there is a capacity issue, it generate network?
because it was erroring out on huge checkout?