Closed jecxjo closed 9 years ago
That looks very much like a bug in SleekXMPP itself. Considering the error gets thrown in sleekxmpp.xmlstream.xmlstream
, I doubt it is caused by anything Err does specifically.
I would recommend trying to reproduce this with this SleekXMPP bot example and filing a bug against SleekXMPP directly if it exhibits the same problem.
Created the SleekXMPP bot example and it works just fine. Looking at the output I receive the cert in the SleekXMPP example but in Errbot I get a connection failure.
That is most interesting. This is what Err does to start up the XMPP back-end, so most likely, it's something we do here that causes the difference.
I wonder if it might be the setting of ca_certs specifically.
Are you currently setting a custom XMPP_CA_CERT_FILE? What happens if you use "/etc/ssl/certs/ca-certificates.crt"
or None
here?
If neither of that makes a difference, does patching Err by commenting out this line make a difference?
Sorry, it was use error. I apparently had quotes around None
so it was looking for a file. No bug.
Attempting to connect to a local Prosody server running on a Raspberry Pi (ARM), Errbot fails to connect using TLS 1.0 and sleekxmpp retports a
Socket Error #2: No such file or directory
. I've tested this on both the XMPP Server's system as well as a separate system and both report back the same error. When I run it on x86_64 it works fine. Might be a bug in Python3.4, sleekxmpp running on ARM?Debug output with personal stuff removed: