Control: reopen -1 "Debian Bug Tracking System" <ow...@bugs.debian.org> writes:
> This is an automatic notification regarding your Bug report > which was filed against the glusterfs-client package: > > Am 18.11.2023 um 17:37 schrieb Xan Charbonnet: >> I recently upgraded the backup machine to bookworm. Suddenly I was unable to >> mount the cluster. The key error in the logs was: >> >> E [socket.c:4405:ssl_setup_connection_params] 0-glusterfs: could not load our >> cert at /usr/lib/ssl/glusterfs.pem >> [snip] > > But if you look in /usr/lib/ssl => > > $ ls -l /usr/lib/ssl/ insgesamt 4 lrwxrwxrwx 1 root root 34 23. Okt > 19:52 cert.pem -> /etc/ssl/certs/ca-certificates.crt lrwxrwxrwx 1 root > root 14 13. Mär 2012 certs -> /etc/ssl/certs drwxr-xr-x 2 root root 4096 > 25. Okt 06:25 misc lrwxrwxrwx 1 root root 20 23. Okt 19:52 openssl.cnf > -> /etc/ssl/openssl.cnf lrwxrwxrwx 1 root root 16 13. Mär 2012 private > -> /etc/ssl/private > > So if you use the subdirectories the paths are correct (in /etc) That's all very well, but glusterd is not looking in a subdirectory of /usr/lib/ssl it is looking for /usr/lib/ssl/glusterfs.pem, as pointed out above. FYI, upstreams docs [1] show gluster looking in /etc/ssl, not in a subdirectory. https://docs.gluster.org/en/latest/Administrator-Guide/SSL/
