Univention Bugzilla – Bug 39646
memcached and stunnel restart not working on Upgrade 4.0->4.1, distributed sessions not working until reboot
Last modified: 2019-01-03 07:18:32 CET
Memcache and stunnel get installed as univention-saml dependencies. They are started before their final config files are written, which depends on UCRVs from joinscripts. The daemons then hang in this state and are not stoppable by their init scripts. As they run with the wrong config, the SAML memcache sessions are not stored on all hosts in the IdP cluster. Kill -9 or a reboot fixes the issue. I did not see this happen after successful configuration.
Theses messages are created during the upgrade: Starting memcached: memcached_univention_saml. Starting SSL tunnels: /etc/stunnel/univention_saml.conf: [ ] Clients allowed=500 [.] stunnel 5.18 on x86_64-pc-linux-gnu platform [.] Compiled/running with OpenSSL 1.0.2d 9 Jul 2015 [.] Threading:PTHREAD Sockets:POLL,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP [ ] errno: (*__errno_location ()) [.] Reading configuration from file /etc/stunnel/univention_saml.conf [.] UTF-8 byte order mark not detected [.] FIPS mode disabled [ ] Compression disabled [ ] Snagged 64 random bytes from /root/.rnd [ ] Wrote 1024 new random bytes to /root/.rnd [ ] PRNG seeded successfully [ ] Initializing service [memcached] [ ] Loading certificate from file: [!] error queue: 140DC002: error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib [!] error queue: 20074002: error:20074002:BIO routines:FILE_CTRL:system lib [!] SSL_CTX_use_certificate_chain_file: 2001002: error:02001002:system library:fopen:No such file or directory [!] Service [memcached]: Failed to initialize SSL context failed You should check that you have specified the pid= in you configuration file done. /etc/idp-ldap-user.secret could not be read!
The error messages should now be ignored by 99check_log_files: r65051
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.