XAMPP: Starting MySQL…already running?












2















When I start XAMPP it shows this



Starting XAMPP for Linux 7.0.8-0...
XAMPP: Starting Apache...ok.
XAMPP: Starting MySQL...already running.
XAMPP: Starting ProFTPD...ok.


when i open localhost/phpmyadmin it shows this error:




phpMyAdmin tried to connect to the MySQL server, and the server
rejected the connection. You should check the host, username and
password in your configuration and make sure that they correspond to
the information given by the administrator of the MySQL server.




ps : it just was working fine , i just restarted my laptop then this



I tried to to stop any other mysql server but ...



/etc/init.d/mysql stop
bash: /etc/init.d/mysql: No such file or directory

service mysql stop
Failed to stop mysql.service: Unit mysql.service not loaded.

killall -KILL mysql mysqld_safe mysqld
mysql: no process found
mysqld_safe: no process found
mysqld: no process found









share|improve this question














bumped to the homepage by Community 8 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    2















    When I start XAMPP it shows this



    Starting XAMPP for Linux 7.0.8-0...
    XAMPP: Starting Apache...ok.
    XAMPP: Starting MySQL...already running.
    XAMPP: Starting ProFTPD...ok.


    when i open localhost/phpmyadmin it shows this error:




    phpMyAdmin tried to connect to the MySQL server, and the server
    rejected the connection. You should check the host, username and
    password in your configuration and make sure that they correspond to
    the information given by the administrator of the MySQL server.




    ps : it just was working fine , i just restarted my laptop then this



    I tried to to stop any other mysql server but ...



    /etc/init.d/mysql stop
    bash: /etc/init.d/mysql: No such file or directory

    service mysql stop
    Failed to stop mysql.service: Unit mysql.service not loaded.

    killall -KILL mysql mysqld_safe mysqld
    mysql: no process found
    mysqld_safe: no process found
    mysqld: no process found









    share|improve this question














    bumped to the homepage by Community 8 hours ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      2












      2








      2


      1






      When I start XAMPP it shows this



      Starting XAMPP for Linux 7.0.8-0...
      XAMPP: Starting Apache...ok.
      XAMPP: Starting MySQL...already running.
      XAMPP: Starting ProFTPD...ok.


      when i open localhost/phpmyadmin it shows this error:




      phpMyAdmin tried to connect to the MySQL server, and the server
      rejected the connection. You should check the host, username and
      password in your configuration and make sure that they correspond to
      the information given by the administrator of the MySQL server.




      ps : it just was working fine , i just restarted my laptop then this



      I tried to to stop any other mysql server but ...



      /etc/init.d/mysql stop
      bash: /etc/init.d/mysql: No such file or directory

      service mysql stop
      Failed to stop mysql.service: Unit mysql.service not loaded.

      killall -KILL mysql mysqld_safe mysqld
      mysql: no process found
      mysqld_safe: no process found
      mysqld: no process found









      share|improve this question














      When I start XAMPP it shows this



      Starting XAMPP for Linux 7.0.8-0...
      XAMPP: Starting Apache...ok.
      XAMPP: Starting MySQL...already running.
      XAMPP: Starting ProFTPD...ok.


      when i open localhost/phpmyadmin it shows this error:




      phpMyAdmin tried to connect to the MySQL server, and the server
      rejected the connection. You should check the host, username and
      password in your configuration and make sure that they correspond to
      the information given by the administrator of the MySQL server.




      ps : it just was working fine , i just restarted my laptop then this



      I tried to to stop any other mysql server but ...



      /etc/init.d/mysql stop
      bash: /etc/init.d/mysql: No such file or directory

      service mysql stop
      Failed to stop mysql.service: Unit mysql.service not loaded.

      killall -KILL mysql mysqld_safe mysqld
      mysql: no process found
      mysqld_safe: no process found
      mysqld: no process found






      server apache2 mysql phpmyadmin xampp






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 6 '16 at 6:39









      BahaaBahaa

      1112




      1112





      bumped to the homepage by Community 8 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 8 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          I think I had the same issue and I solved it this way.



          There is a Your_username.pid file and Your_username.err file in /opt/lampp/var/mysql/. Delete them and restart Xampp.



          It happens when you turn off your computer unsuccessfully or with an issue.






          share|improve this answer

































            0














            I had same issue, removed these files and problem solved.



            irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.pid
            irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.err
            irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.log





            share|improve this answer



















            • 2





              Blindly removing a PID file is not an good idea. Two instances of the same software can wreak havoc in a few cases - there's a reason locking is used. Do a cat /opt/lampp/var/mysql/ubuntu.pid, and check that the PID is not running before removing. If it's running, use kill to stop it.

              – vidarlo
              Oct 30 '17 at 6:00











            • @vidarlo Yes. I agree. In my case, I tried most ways to terminate MySQL but problem not solved. Its clear that above solution is not a best solution but it can be the last.

              – Reza
              Oct 30 '17 at 9:25











            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f821542%2fxampp-starting-mysql-already-running%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I think I had the same issue and I solved it this way.



            There is a Your_username.pid file and Your_username.err file in /opt/lampp/var/mysql/. Delete them and restart Xampp.



            It happens when you turn off your computer unsuccessfully or with an issue.






            share|improve this answer






























              0














              I think I had the same issue and I solved it this way.



              There is a Your_username.pid file and Your_username.err file in /opt/lampp/var/mysql/. Delete them and restart Xampp.



              It happens when you turn off your computer unsuccessfully or with an issue.






              share|improve this answer




























                0












                0








                0







                I think I had the same issue and I solved it this way.



                There is a Your_username.pid file and Your_username.err file in /opt/lampp/var/mysql/. Delete them and restart Xampp.



                It happens when you turn off your computer unsuccessfully or with an issue.






                share|improve this answer















                I think I had the same issue and I solved it this way.



                There is a Your_username.pid file and Your_username.err file in /opt/lampp/var/mysql/. Delete them and restart Xampp.



                It happens when you turn off your computer unsuccessfully or with an issue.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jul 9 '17 at 11:16









                David Foerster

                28.3k1365111




                28.3k1365111










                answered Jul 2 '17 at 8:09









                Babak KamaliBabak Kamali

                1




                1

























                    0














                    I had same issue, removed these files and problem solved.



                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.pid
                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.err
                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.log





                    share|improve this answer



















                    • 2





                      Blindly removing a PID file is not an good idea. Two instances of the same software can wreak havoc in a few cases - there's a reason locking is used. Do a cat /opt/lampp/var/mysql/ubuntu.pid, and check that the PID is not running before removing. If it's running, use kill to stop it.

                      – vidarlo
                      Oct 30 '17 at 6:00











                    • @vidarlo Yes. I agree. In my case, I tried most ways to terminate MySQL but problem not solved. Its clear that above solution is not a best solution but it can be the last.

                      – Reza
                      Oct 30 '17 at 9:25
















                    0














                    I had same issue, removed these files and problem solved.



                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.pid
                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.err
                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.log





                    share|improve this answer



















                    • 2





                      Blindly removing a PID file is not an good idea. Two instances of the same software can wreak havoc in a few cases - there's a reason locking is used. Do a cat /opt/lampp/var/mysql/ubuntu.pid, and check that the PID is not running before removing. If it's running, use kill to stop it.

                      – vidarlo
                      Oct 30 '17 at 6:00











                    • @vidarlo Yes. I agree. In my case, I tried most ways to terminate MySQL but problem not solved. Its clear that above solution is not a best solution but it can be the last.

                      – Reza
                      Oct 30 '17 at 9:25














                    0












                    0








                    0







                    I had same issue, removed these files and problem solved.



                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.pid
                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.err
                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.log





                    share|improve this answer













                    I had same issue, removed these files and problem solved.



                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.pid
                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.err
                    irdev@ubuntu:~$ sudo rm /opt/lampp/var/mysql/ubuntu.log






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Oct 30 '17 at 5:37









                    RezaReza

                    35




                    35








                    • 2





                      Blindly removing a PID file is not an good idea. Two instances of the same software can wreak havoc in a few cases - there's a reason locking is used. Do a cat /opt/lampp/var/mysql/ubuntu.pid, and check that the PID is not running before removing. If it's running, use kill to stop it.

                      – vidarlo
                      Oct 30 '17 at 6:00











                    • @vidarlo Yes. I agree. In my case, I tried most ways to terminate MySQL but problem not solved. Its clear that above solution is not a best solution but it can be the last.

                      – Reza
                      Oct 30 '17 at 9:25














                    • 2





                      Blindly removing a PID file is not an good idea. Two instances of the same software can wreak havoc in a few cases - there's a reason locking is used. Do a cat /opt/lampp/var/mysql/ubuntu.pid, and check that the PID is not running before removing. If it's running, use kill to stop it.

                      – vidarlo
                      Oct 30 '17 at 6:00











                    • @vidarlo Yes. I agree. In my case, I tried most ways to terminate MySQL but problem not solved. Its clear that above solution is not a best solution but it can be the last.

                      – Reza
                      Oct 30 '17 at 9:25








                    2




                    2





                    Blindly removing a PID file is not an good idea. Two instances of the same software can wreak havoc in a few cases - there's a reason locking is used. Do a cat /opt/lampp/var/mysql/ubuntu.pid, and check that the PID is not running before removing. If it's running, use kill to stop it.

                    – vidarlo
                    Oct 30 '17 at 6:00





                    Blindly removing a PID file is not an good idea. Two instances of the same software can wreak havoc in a few cases - there's a reason locking is used. Do a cat /opt/lampp/var/mysql/ubuntu.pid, and check that the PID is not running before removing. If it's running, use kill to stop it.

                    – vidarlo
                    Oct 30 '17 at 6:00













                    @vidarlo Yes. I agree. In my case, I tried most ways to terminate MySQL but problem not solved. Its clear that above solution is not a best solution but it can be the last.

                    – Reza
                    Oct 30 '17 at 9:25





                    @vidarlo Yes. I agree. In my case, I tried most ways to terminate MySQL but problem not solved. Its clear that above solution is not a best solution but it can be the last.

                    – Reza
                    Oct 30 '17 at 9:25


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f821542%2fxampp-starting-mysql-already-running%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How did Captain America manage to do this?

                    迪纳利

                    南乌拉尔铁路局