SUSE Support

Here When You Need Us

smt-mirror returns 500 CURL ERROR(35) SSL connect error

This document (7023988) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12


Situation

While syncing a repository (in this example SLES12-SP4-Updates for x86_64) the following error may be experienced:

smt:~ # smt-mirror  --repository 2769
Mirroring: https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update/
Target:    /srv/www/htdocs/repo/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update/
E 'https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update/repodata/repomd.xml': 500 CURL ERROR(35) SSL connect error
E 'https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update/repodata/repomd.xml': 500 CURL ERROR(35) SSL connect error
E 'https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update/repodata/repomd.xml': 500 CURL ERROR(35) SSL connect error
SMT::Parser::RpmMdLocation Invalid XML in '/srv/www/htdocs/repo/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update//.repodata/repomd.xml':
no element found at line 1, column 0, byte 0 at /usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi/XML/Parser.pm line 187.
Unable to recognise encoding of this document at /usr/lib/perl5/vendor_perl/5.18.2/XML/SAX/PurePerl/EncodingDetect.pm line 100.
SMT::Parser::RpmMdLocation Invalid XML in '/srv/www/htdocs/repo/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update//.repodata/repomd.xml': Document requires an element [Ln: 1, Col: 0]
Unable to recognise encoding of this document at /usr/lib/perl5/vendor_perl/5.18.2/XML/SAX/PurePerl/EncodingDetect.pm line 100.
SMT::Parser::RpmMdLocation Invalid XML in '/srv/www/htdocs/repo/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update//.repodata/repomd.xml': Document requires an element [Ln: 1, Col: 0]
Finished downloading and parsing the metadata, going to download the rest of the files...
=> Finished mirroring 'https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update/'
=> Total files                 : 1
=> Total transferred files     : 0
=> Total transferred file size : 0 bytes (0 Bytes)
=> Total linked files          : 0
=> Total copied files          : 0
=> Files up to date            : 0
=> Errors                      : 2
=> Mirror Time                 : 00:00:01
=> New security updates        : 0
=> New recommended updates     : 0

Summary
Total transfered files    : 0
Total transfered file size: 0 (0 Bytes)
Total linked files        : 0
Total copied files        : 0
New security updates      : 0
New recommended updates   : 0
Errors:                   : 2
Total Mirror Time         : 00:00:01
Repositories with errors  :
  * SLES12-SP4-Updates for sle-12-x86_64 (https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update/):
    - E 'https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP4/x86_64/update/repodata/repomd.xml': 500 CURL ERROR(35) SSL connect error

Resolution

In /etc/smt.conf look for the line starting with HTTPSProxy and check if the url pointed to is http and not https.

Cause

The string for the HTTPS connection should be in the form http://proxy.example.com:3128

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7023988
  • Creation Date: 04-Jul-2019
  • Modified Date:03-Mar-2020
    • Subscription Management Tool

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

tick icon

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

tick icon

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

tick icon

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.