Package: smokeping
Version: 2.6.8-2
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
configuring a slave while having the master on ssl
starting the slave states : (invoke-rc.d smokeping start)
WARNING Master said 500 Can't connect to XXXx.com:443 (certificate verify
failed)
ERROR: we did not get config from the master. Maybe we are not configured as a
slave for any of the targets on the master ?
so, it fails to start. no evident way to fix it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I started adding the cert to /etc/ssl/certs
+ hash link : for i in *pem *crt;do ln -sv $i `openssl x509 -hash -noout -in
$i`.0;done
* What was the outcome of this action?
no change.
digged in source code, man LWP::UserAgent, man IO::Socket::SSL,
found out about PERL_LWP_SSL_CA_PATH.
set export PERL_LWP_SSL_CA_PATH=/etc/ssl/certs/ in /etc/default/smokeping
(should be default)
after that it worked
* What outcome did you expect instead?
either works or suggest some remediation.
*** End of the template - remove these lines ***
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (449, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
