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

Mysql would not start (service hangs on startup due to missing ini file)

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 5.5.39, 10.0.12, 10.1.0
    • 5.5(EOL), 10.1(EOL)
    • None
    • windows 2012 R2 datacenter

    Description

      In Windows the service gets stuck in "Starting", as shown in the services applet. It started fine the first time, then I changed my.cnf so data would be stored in a different drive, stopped the service, copied the data directory to the new drive, set the permissions on the new destination so "everybody" would have full rights, then the service started, I loaded a 40 GB of data just fine. Then I stopped the service, and it never started again. I rebooted and it still did not start. I can give you access to the box. It is a development box accessible via remote desktop.
      Note: there are no messages in the windows application log.

      Attachments

        Activity

          Could you provide any more information? Like, error logs, error messages, anything?

          serg Sergei Golubchik added a comment - Could you provide any more information? Like, error logs, error messages, anything?

          Hi,

          You can send me connection info either via email or in a private message on IRC, or any other way suitable for you.

          elenst Elena Stepanova added a comment - Hi, You can send me connection info either via email or in a private message on IRC, or any other way suitable for you.

          my skype is philip_38

          On Tue, Aug 5, 2014 at 1:07 PM, Elena Stepanova (JIRA)

          philip_38 Philip orleans added a comment - my skype is philip_38 On Tue, Aug 5, 2014 at 1:07 PM, Elena Stepanova (JIRA)

          Investigation has shown that the server did not start because my.ini file did not exist in the location configured for the Windows service. Creating the required path fixed the issue.

          However, it is still a bug because the service shouldn't hang, it should fail with a proper error message (as a normal standalone server does if it's started with a non-existing --defaults-file).

          elenst Elena Stepanova added a comment - Investigation has shown that the server did not start because my.ini file did not exist in the location configured for the Windows service. Creating the required path fixed the issue. However, it is still a bug because the service shouldn't hang, it should fail with a proper error message (as a normal standalone server does if it's started with a non-existing --defaults-file).

          People

            Unassigned Unassigned
            philip_38 Philip orleans
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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