Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-11244

main.ssl_timeout failed in buildbot

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.2(EOL)
    • N/A
    • Tests

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-xenial-amd64/builds/547/steps/test_5/logs/stdio

      main.ssl_timeout                         w1 [ fail ]
      		 
              Test ended at 2016-11-04 15:38:42
      		 
       
      		 
      CURRENT_TEST: main.ssl_timeout
      		 
      mysqltest: At line 10: query 'SELECT (VARIABLE_VALUE <> '') AS have_ssl FROM INFORMATION_SCHEMA.SESSION_STATUS WHERE VARIABLE_NAME='Ssl_cipher'' failed: 2013: Lost connection to MySQL server during query
      		 
       
      		 
      The result from queries just before the failure was:
      		 
      # connect with read timeout so SLEEP() should timeout
      		 
      connect  ssl_con,localhost,root,,,,,SSL read_timeout=5;
      		 
      # Check ssl turned on
      		 
      SELECT (VARIABLE_VALUE <> '') AS have_ssl FROM INFORMATION_SCHEMA.SESSION_STATUS WHERE VARIABLE_NAME='Ssl_cipher';
      		 
       
      		 
       - skipping '/dev/shm/var/1/log/main.ssl_timeout/'

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-7069 Fix buildbot failures in main server trees

          • Major - Major loss of function.
          • Stalled

          Activity

            Ascending order - Click to sort in descending order
            wlad Vladislav Vaintroub added a comment -

            this one is sporadic, but at the very least I'd like to have errors from the lowest level (ssl) to be properly propagated to the upper level. "Lost connection during query" has no details.

            There should be SSL error , or socket error there. If the socket was closed on the server side
            (as indicated by recv() returning 0), it should say "server closed the connection".

            mysqld did not crash here btw.

            wlad Vladislav Vaintroub added a comment - this one is sporadic, but at the very least I'd like to have errors from the lowest level (ssl) to be properly propagated to the upper level. "Lost connection during query" has no details. There should be SSL error , or socket error there. If the socket was closed on the server side (as indicated by recv() returning 0), it should say "server closed the connection". mysqld did not crash here btw.
            georg Georg Richter added a comment -

            We have at least two options to fix this:

            1) Using pvio->read/write instead of SSL_read/SSL_write by registering these function via BIO_method (that would allow also to communicate via non socket connections).

            2) Using non-blocking and checking error codes and timeout.

            georg Georg Richter added a comment - We have at least two options to fix this: 1) Using pvio->read/write instead of SSL_read/SSL_write by registering these function via BIO_method (that would allow also to communicate via non socket connections). 2) Using non-blocking and checking error codes and timeout.

            People

              georg Georg Richter
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.