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

Comman mysql.exe on Windows 10 without internet comnnection does not work properly

Details

    Description

      Given:
      Windows 10 withot internet connection, becouse closed in externel firewall (only lan connection possible).
      MariaDB version 11.4.3.

      Error:
      In terminal executed command "mysql -u root -p" throws one error (screenshot.jpg).
      MariaDB 10.11.6 did not have this problem. Was used on same pc before using MariaDB 11.4.3. No preinstalled MariaDB, system was reseted before every installation from a backuped image.

      Logsection (from file testpcname.err):

      2024-11-11 10:42:10 0 [Note] Starting MariaDB 11.4.3-MariaDB source revision 5ab81ffe0097a22a774957df28c5223cf0201de3 server_uid c/P00bHqcfSzxHFB5BpVOCWWLNI= as process 4112
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Number of transaction pools: 1
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Initializing buffer pool, total size = 3.999GiB, chunk size = 63.984MiB
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Completed initialization of buffer pool
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: End of log at LSN=47629
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Opened 3 undo tablespaces
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: log sequence number 47629; transaction id 14
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Loading buffer pool(s) from C:\Program Files\MariaDB 11.4\data\ib_buffer_pool
      		 
      2024-11-11 10:42:10 0 [Note] Plugin 'FEEDBACK' is disabled.
      		 
      2024-11-11 10:42:10 0 [Note] mysqld.exe: SSPI: using principal name 'localhost', mech 'Negotiate'
      		 
      2024-11-11 10:42:10 0 [Note] InnoDB: Buffer pool(s) load completed at 241111 10:42:10
      		 
      2024-11-11 10:42:11 0 [Note] Server socket created on IP: '::'.
      		 
      2024-11-11 10:42:11 0 [Note] Server socket created on IP: '0.0.0.0'.
      		 
      2024-11-11 10:42:11 0 [Note] mysqld.exe: Event Scheduler: Loaded 0 events
      		 
      2024-11-11 10:42:11 0 [Note] C:\Program Files\MariaDB 11.4\bin\mysqld.exe: ready for connections.
      		 
      Version: '11.4.3-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
      		 
      2024-11-11 10:50:26 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: 'localhost' (Got an error reading communication packets)
      		 
      2024-11-11 10:50:26 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: 'localhost' (This connection closed normally without authentication)

      Workarounds:

      • If this command was once executed when the pc had a internet connection, then the command works also when the internet connection is closed in a external firewall (only lan connection possible).
      • Remove DNS entrie in the ethernet setings (there was no entries in hosts file).

      Attachments

        Activity

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

          Hi affreigmbh. I could not reproduce it on Windows 11 I got, although I got rid of network using more conventional "pull the plug" technique.

          That said, I suspect client does something stupid, for example it tries to validate server self-signed certificate, and for the purpose of validation it would try to do FQDN name matching or something like that.

          May I suggest you try the latest 11.4.4, it is available since several days, a lot of client-side certificate verification was fixed there, and give feedback if it fixes it or you.

          Alternatively, you can try adding "--ssl=0" to the command line, and see if it works.

          wlad Vladislav Vaintroub added a comment - Hi affreigmbh . I could not reproduce it on Windows 11 I got, although I got rid of network using more conventional "pull the plug" technique. That said, I suspect client does something stupid, for example it tries to validate server self-signed certificate, and for the purpose of validation it would try to do FQDN name matching or something like that. May I suggest you try the latest 11.4.4, it is available since several days, a lot of client-side certificate verification was fixed there, and give feedback if it fixes it or you. Alternatively, you can try adding "--ssl=0" to the command line, and see if it works.
          affreigmbh A. F. added a comment - - edited

          Hi Vladislav Vaintroub.

          I did some other tests.
          With the parameter "--ssl=0" the command ("mysql.exe --ssl=0 -u root -p") works fine.
          Took this time another pc (virtual pc from snapshot installed 2 jears ago, "blank" Windows 10).
          Result (without "--ssl=0") was the same with MariaDB 11.4.4.

          2024-11-12  9:31:06 0 [Note] C:\Program Files\MariaDB 11.4\bin\mysqld.exe: ready for connections.
          		 
          Version: '11.4.4-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
          		 
          2024-11-12  9:39:00 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: 'localhost' (Got an error reading communication packets)
          		 
          2024-11-12  9:39:00 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: 'localhost' (This connection closed normally without authentication)

          As i updated the system completely (did reset it before the update from the snapshot) and then installed MariaDB 11.4.4 mysql.exe worked fine.
          If the pc was completely cut from net (pull virtual cable) mysql.exe worked fine.

          If i see it correctly it hapens realy rarely under specific circumstances (any change and mysql.exe works fine):
          1. Not updated Windows 10
          2. LAN connection available but no internet connection available (external firewall)
          3. DNS entrie set in the ethernet settings
          4. MariaDB 11.4.3 / 11.4.4
          5. "--ssl=0" parameter not used

          It turnd out that this workflow is happening in our case becouse the ssl is now per default enabled (was in the past disabled).

          We can work in the firma with the workarounds (ssl parameter, updated Windows).
          Tnank you for your support.

          affreigmbh A. F. added a comment - - edited Hi Vladislav Vaintroub. I did some other tests. With the parameter "--ssl=0" the command ("mysql.exe --ssl=0 -u root -p") works fine. Took this time another pc (virtual pc from snapshot installed 2 jears ago, "blank" Windows 10). Result (without "--ssl=0") was the same with MariaDB 11.4.4. 2024-11-12 9:31:06 0 [Note] C:\Program Files\MariaDB 11.4\bin\mysqld.exe: ready for connections. Version: '11.4.4-MariaDB' socket: '' port: 3306 mariadb.org binary distribution 2024-11-12 9:39:00 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: 'localhost' (Got an error reading communication packets) 2024-11-12 9:39:00 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: 'localhost' (This connection closed normally without authentication) As i updated the system completely (did reset it before the update from the snapshot) and then installed MariaDB 11.4.4 mysql.exe worked fine. If the pc was completely cut from net (pull virtual cable) mysql.exe worked fine. If i see it correctly it hapens realy rarely under specific circumstances (any change and mysql.exe works fine): 1. Not updated Windows 10 2. LAN connection available but no internet connection available (external firewall) 3. DNS entrie set in the ethernet settings 4. MariaDB 11.4.3 / 11.4.4 5. "--ssl=0" parameter not used It turnd out that this workflow is happening in our case becouse the ssl is now per default enabled (was in the past disabled). We can work in the firma with the workarounds (ssl parameter, updated Windows). Tnank you for your support.
          wlad Vladislav Vaintroub added a comment -

          Ok, thanks for the feedback!
          I'll close it for now. If this works on up-to-date Windows out of the box, it is already good news, On older Windows , --ssl=0 would be the workaround.

          wlad Vladislav Vaintroub added a comment - Ok, thanks for the feedback! I'll close it for now. If this works on up-to-date Windows out of the box, it is already good news, On older Windows , --ssl=0 would be the workaround.
          wlad Vladislav Vaintroub added a comment -

          Closing as "not a bug", as it does not seem to be our bug. According to feedback, using up-to-date patches OS does not exhibit the behavior

          wlad Vladislav Vaintroub added a comment - Closing as "not a bug", as it does not seem to be our bug. According to feedback, using up-to-date patches OS does not exhibit the behavior

          People

            wlad Vladislav Vaintroub
            affreigmbh A. F.
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.