Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.4.24
    • N/A
    • None
    • Windows 11 Home using Xampp server 3.3.0

    Description

      Everything appeared to be working fine, until I started receiving the following error.
      This is a new installation of Xampp server on Windows 11 home.

      Attached are the results of the mysql error log.

      This is the the message received from the Xampp control panel:

      2:00:11 PM [mysql] Status change detected: stopped
      2:00:11 PM [mysql] Error: MySQL shutdown unexpectedly.
      2:00:11 PM [mysql] This may be due to a blocked port, missing dependencies,
      2:00:11 PM [mysql] improper privileges, a crash, or a shutdown by another method.
      2:00:11 PM [mysql] Press the Logs button to view error logs and check
      2:00:11 PM [mysql] the Windows Event Viewer for more clues
      2:00:11 PM [mysql] If you need more help, copy and post this
      2:00:11 PM [mysql] entire log window on the forums

      Attachments

        Issue Links

          Activity

            danblack Daniel Black added a comment -

            The log file is showing a crash recovery. Do you have logs of the original crash?

            How was your demo2 database created? Was it running the same mariadb version when it was installed?

            danblack Daniel Black added a comment - The log file is showing a crash recovery. Do you have logs of the original crash? How was your demo2 database created? Was it running the same mariadb version when it was installed?

            To get proper stack traces, .pdb files would be needed. I’ve heard that unlike the packages that MariaDB distributes for Microsoft Windows, XAMPP does not include them.

            marko Marko Mäkelä added a comment - To get proper stack traces, .pdb files would be needed. I’ve heard that unlike the packages that MariaDB distributes for Microsoft Windows, XAMPP does not include them.
            Eran Aran Ariel added a comment - - edited

            Hi Daniel, yes I have the logs of the original crash and apologies for the delay in reply. I created the demos database manually in phpmyadmin and the table was created using a script that I have just now uploaded. I reccovered by reinstalling xampp. Attaced iis the errror log

            Eran Aran Ariel added a comment - - edited Hi Daniel, yes I have the logs of the original crash and apologies for the delay in reply. I created the demos database manually in phpmyadmin and the table was created using a script that I have just now uploaded. I reccovered by reinstalling xampp. Attaced iis the errror log
            Eran Aran Ariel added a comment - - edited

            Thank you Marko ... got it

            Eran Aran Ariel added a comment - - edited Thank you Marko ... got it
            danblack Daniel Black added a comment -

            Your uploaded mysql_error.log appears to be the same as the original mysqld got exception 0x80000003.txt. Do you have the original one of the crash before the startup in crash recovery mode?

            I tried your sql file on 10.4.25+16cebed54065ad9e18953aa86d48f6007d53c2d3 and 10.4.24 linux containers and they both loaded successfully.

            10.4.25+16cebed54065ad9e18953aa86d48f6007d53c2d3

            $ podman run --rm --env MARIADB_ROOT_PASSWORD=bob --env MARIADB_DATABASE=test --env MARIADB_USER=test --env MARIADB_PASSWORD=test -v /tmp/d:/docker-entrypoint-initdb.d:z quay.io/mariadb-foundation/mariadb-devel:10.4
            2022-05-11 03:51:36+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.4.25+maria~focal started.
             
            2022-05-11 03:51:52+00:00 [Note] [Entrypoint]: Giving user test access to schema test
             
            2022-05-11 03:51:52+00:00 [Note] [Entrypoint]: /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/test.sql
             
            2022-05-11 03:51:53+00:00 [Note] [Entrypoint]: Stopping temporary server
            

            So this could either be a windows specific bug or something hardware related. Can you check the event viewer to see if there's anything specific there. This is such a basic sql test I cannot force aspects of it that would not be tested in CI.

            danblack Daniel Black added a comment - Your uploaded mysql_error.log appears to be the same as the original mysqld got exception 0x80000003.txt. Do you have the original one of the crash before the startup in crash recovery mode? I tried your sql file on 10.4.25+16cebed54065ad9e18953aa86d48f6007d53c2d3 and 10.4.24 linux containers and they both loaded successfully. 10.4.25+16cebed54065ad9e18953aa86d48f6007d53c2d3 $ podman run --rm --env MARIADB_ROOT_PASSWORD=bob --env MARIADB_DATABASE=test --env MARIADB_USER=test --env MARIADB_PASSWORD=test -v /tmp/d:/docker-entrypoint-initdb.d:z quay.io/mariadb-foundation/mariadb-devel:10.4 2022-05-11 03:51:36+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.4.25+maria~focal started.   2022-05-11 03:51:52+00:00 [Note] [Entrypoint]: Giving user test access to schema test   2022-05-11 03:51:52+00:00 [Note] [Entrypoint]: /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/test.sql   2022-05-11 03:51:53+00:00 [Note] [Entrypoint]: Stopping temporary server So this could either be a windows specific bug or something hardware related. Can you check the event viewer to see if there's anything specific there. This is such a basic sql test I cannot force aspects of it that would not be tested in CI.

            People

              Unassigned Unassigned
              Eran Aran Ariel
              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.