Univention Bugzilla – Bug 39650
Test case 81alternativessl failed in Jenkins
Last modified: 2019-01-03 07:19:10 CET
See here: http://jenkins.knut.univention.de:8080/job/UCS-4.1/job/UCS-4.1-0/job/Autotest%20MultiEnv/82/SambaVersion=s4,Systemrolle=backup/testReport/01_base/81alternativessl/test/ *** BEGIN *** ['/bin/bash', '81alternativessl'] *** *** 01_base/81alternativessl *** checking alternative ssl-certificate for apache *** *** START TIME: 2015-10-28 04:20:01 *** List all certificates 01 unassigned-hostname.unassigned-domain 02 master093.autotest093.local 03 ucs-sso.autotest093.local 04 backup093.autotest093.local Creating certificate: ucs-test Syntax error on line 20 of /etc/apache2/sites-enabled/default-ssl: SSLCertificateFile: file '/etc/univention/ssl/ucs-test/cert.pem' does not exist or is empty Action 'configtest' failed. The Apache error log may have more information. failed! invoke-rc.d: initscript apache2, action "restart" failed. diff: /etc/univention/ssl/ucs-test/cert.pem: Datei oder Verzeichnis nicht gefunden Unsetting apache2/ssl/certificate Unsetting apache2/ssl/key Multifile: /etc/simplesamlphp/metadata/saml20-idp-hosted.php Multifile: /etc/apache2/sites-available/default-ssl Restarting web server: apache2 ... waiting . diff: /etc/univention/ssl/ucs-test/cert.pem: Datei oder Verzeichnis nicht gefunden und das ist auch gut so! Revoke certificate: ucs-test W: The config registry variable 'apache2/ssl/certificate' does not exist W: The config registry variable 'apache2/ssl/key' does not exist Restarting web server: apache2 ... waiting . *** END TIME: 2015-10-28 04:20:11 *** *** TEST DURATION (H:MM:SS.ms): 0:00:09.959607 *** *** END *** 110 ***
@Felix → caused by Bug #39476 ?
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.