[jira] [Resolved] (IMPALA-9084) DCHECK hit due to openssl issue

["Tim Armstrong (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-9084.
-----------------------------------
    Resolution: Cannot Reproduce

I don't think we have enough info to debug the failure.

> DCHECK hit due to openssl issue
> -------------------------------
>
>                 Key: IMPALA-9084
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9084
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 3.4.0
>            Reporter: Thomas Tauber-Marshall
>            Priority: Critical
>              Labels: broken-build, flaky
>
> Seen in a Jenkins build on centos6:
> {noformat}
> F1021 04:57:06.296216 14613 openssl_util.h:201] Check failed: ERR_peek_error() == 0 (637976643 vs. 0) Expected no pending OpenSSL errors on kudu::Status kudu::security::TlsContext::InitiateHandshake(kudu::security::TlsHandshakeType, kudu::security::TlsHandshake*) const entry, but had: error:2606C043:engine routines:ENGINE_FREE_UTIL:passed a null parameter:eng_lib.c:112 error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:390:id=dynamic error:2606C043:engine routines:ENGINE_FREE_UTIL:passed a null parameter:eng_lib.c:112 error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:390:id=rdrand
> {noformat}
> TestRuntimeFilters::test_basic_filters may have been the test that was running when it was hit.
> The error is the same as in IMPALA-7018, but the build included the fix from the JIRA



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org