<p></p>
<p>I think I figured out why all these issues are popping up all of a sudden.</p>
<p>A couple of months ago, Xenial's libmysqlclient 5.7.28-0ubuntu0.16.04.2 made the following change:</p>
<pre><code>  * debian/rules: removed -DWITH_SSL=bundled, option no longer works.
  * debian/control: add libssl-dev to Build-Depends.
</code></pre>
<p>Before that, the <code>WITH_SSL=bundled</code> option was the default, and "bundled" didn't actually use OpenSSL but yaSSL (see <a href="https://mysqlserverteam.com/mysql-is-openssl-only-now/" rel="nofollow">https://mysqlserverteam.com/mysql-is-openssl-only-now/</a>)!</p>
<p>So in the past, the db_mysql module would use YaSSL and the tls module would use OpenSSL and everyone was happy. But now suddenly both modules use OpenSSL (1.0.2, in Xenial) and there's a conflict with how both of them handle locking callbacks.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/2395#issuecomment-666255604">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABO7UZOBEDNI65JSLTUVN5TR6E4BRANCNFSM4OS7FHTQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/ABO7UZNWIIHLQ6LCTA25JJDR6E4BRA5CNFSM4OS7FHT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE63EB5A.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/kamailio/kamailio/issues/2395#issuecomment-666255604",
"url": "https://github.com/kamailio/kamailio/issues/2395#issuecomment-666255604",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>