Hi, On Tue, Sep 24, 2013 at 4:33 PM, Niemann, Hartmut <hartmut.niem...@siemens.com> wrote: > Hello! > > > > What is going wrong if I get > > svn: warning: W120171: Error running context: An error > occurred during SSL communication > > five out of six times I try to update a repository or to do some other > subversion command? >
the error code comes from the serf library, more specifically this is error SERF_ERROR_SSL_COMM_FAILED. It indicates that the OpenSSL library reported an error during ssl/tls communication. It should be unrelated to certificate validation as that's another error code. > > (This is Tortoise SVN/64 > > TortoiseSVN 1.8.2, Build 24708 - 64 Bit , 2013/08/27 19:20:39 > > Subversion 1.8.3, -release > > apr 1.4.8 > apr-util 1.5.2 > serf 1.3.1 > OpenSSL 1.0.1e 11 Feb 2013 > zlib 1.2.8 > > > > and it’s command line tool > > > svn, version 1.8.3 (r1516576) > > compiled Aug 27 2013, 22:13:03 on x86-microsoft-windows [...] > > * ra_serf : Module for accessing a repository via WebDAV protocol using > serf. > > - using serf 1.3.1 > - handles 'http' scheme > - handles 'https' scheme > on Windows 7) > > > > The problems started yesterday (tsvn 1.8.1, about 3 out of 4 tries failed), > today nothing works. > Was something in the server configuration related to ssl/tls modified? Or, do you use a proxy server that was changed recently? > I upgraded to 1.8.3, tried both the gui and the command line version. > > Where do I have to look for the cause of this failure? > First of all check the apache access and error logs, if the server raised an ssl alert it should be in the logs. Second, run wireshark. If you're using a proxy, check that the ssl tunnel setup was done correctly. Also check that the proxy is not configured to close the connection after the first request (Connection:Close header on the response to the CONNECT request). Check if there are ssl alerts, check if it's the client or the server that closed the connection, check if session initialisation was successful. Third, get yourself a build of serf with logging activated (#define SSL_VERBOSE 1), send the logs to the list or to me privately, should give us a lot of info to analyse what's wrong. Lieven > > Mit freundlichen Grüßen > Dr. Hartmut Niemann > > Siemens AG > Infrastructure & Cities Sector > Rail Systems Division > Locomotives and Components > IC RL LOC EN LE 8 > Werner-von-Siemens-Str. 67 > 91052 Erlangen, Deutschland > Tel: +49 9131 7-34264 > Fax: +49 9131 7-26254 > mailto:hartmut.niem...@siemens.com > > Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; > Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Brigitte Ederer, Klaus > Helmrich, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. > Solmssen, Michael Süß; Sitz der Gesellschaft: Berlin und München, > Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB > 6684; WEEE-Reg.-Nr. DE 23691322
