Remove MySQL Ubuntu 16.04 all solutions have failed

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












All solutions listed here for removing MySQL fails:



Uninstall MySQL from Ubuntu 16.04



and



Removing MariaDB Installs MySQL and vice-versa



These are my errors:



$ sudo apt-get purge mysql*
$ sudo apt-get autoremove
$ sudo apt-get autoclean
$ sudo apt-get dist-upgrade
$ sudo apt-get install mysql



$ apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
mysql-server-core-5.7
0 upgraded, 0 newly installed, 1 to remove and 131 not upgraded.
2 not fully installed or removed.
After this operation, 46.2 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 287191 files and directories currently installed.)
Removing mysql-server-core-5.7 (5.7.22-0ubuntu0.16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up mysql-common (5.7.22-0ubuntu0.16.04.1) ...
update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback doesn't exist
dpkg: error processing package mysql-common (--configure):
subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of mysql-client-5.7:
mysql-client-5.7 depends on mysql-common (>= 5.5); however:
Package mysql-common is not configured yet.

dpkg: error processing package mysql-client-5.7 (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.

Errors were encountered while processing:
mysql-common
mysql-client-5.7
E: Sub-process /usr/bin/dpkg returned an error code (1)






share|improve this question






















  • This isn't a BBCODE forum. Use StackExchange code formatting, select the text you want to code-format, then click the button that looks like this in your editing window:
    – Thomas Ward♦
    May 20 at 3:17











  • did you do this with mysql still running? If so...
    – Rinzwind
    May 20 at 7:47










  • mysql not running. Doesn't start on startup I always start with sudo systemctl start mysql
    – jeffschips
    May 20 at 12:55














up vote
0
down vote

favorite












All solutions listed here for removing MySQL fails:



Uninstall MySQL from Ubuntu 16.04



and



Removing MariaDB Installs MySQL and vice-versa



These are my errors:



$ sudo apt-get purge mysql*
$ sudo apt-get autoremove
$ sudo apt-get autoclean
$ sudo apt-get dist-upgrade
$ sudo apt-get install mysql



$ apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
mysql-server-core-5.7
0 upgraded, 0 newly installed, 1 to remove and 131 not upgraded.
2 not fully installed or removed.
After this operation, 46.2 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 287191 files and directories currently installed.)
Removing mysql-server-core-5.7 (5.7.22-0ubuntu0.16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up mysql-common (5.7.22-0ubuntu0.16.04.1) ...
update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback doesn't exist
dpkg: error processing package mysql-common (--configure):
subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of mysql-client-5.7:
mysql-client-5.7 depends on mysql-common (>= 5.5); however:
Package mysql-common is not configured yet.

dpkg: error processing package mysql-client-5.7 (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.

Errors were encountered while processing:
mysql-common
mysql-client-5.7
E: Sub-process /usr/bin/dpkg returned an error code (1)






share|improve this question






















  • This isn't a BBCODE forum. Use StackExchange code formatting, select the text you want to code-format, then click the button that looks like this in your editing window:
    – Thomas Ward♦
    May 20 at 3:17











  • did you do this with mysql still running? If so...
    – Rinzwind
    May 20 at 7:47










  • mysql not running. Doesn't start on startup I always start with sudo systemctl start mysql
    – jeffschips
    May 20 at 12:55












up vote
0
down vote

favorite









up vote
0
down vote

favorite











All solutions listed here for removing MySQL fails:



Uninstall MySQL from Ubuntu 16.04



and



Removing MariaDB Installs MySQL and vice-versa



These are my errors:



$ sudo apt-get purge mysql*
$ sudo apt-get autoremove
$ sudo apt-get autoclean
$ sudo apt-get dist-upgrade
$ sudo apt-get install mysql



$ apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
mysql-server-core-5.7
0 upgraded, 0 newly installed, 1 to remove and 131 not upgraded.
2 not fully installed or removed.
After this operation, 46.2 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 287191 files and directories currently installed.)
Removing mysql-server-core-5.7 (5.7.22-0ubuntu0.16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up mysql-common (5.7.22-0ubuntu0.16.04.1) ...
update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback doesn't exist
dpkg: error processing package mysql-common (--configure):
subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of mysql-client-5.7:
mysql-client-5.7 depends on mysql-common (>= 5.5); however:
Package mysql-common is not configured yet.

dpkg: error processing package mysql-client-5.7 (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.

Errors were encountered while processing:
mysql-common
mysql-client-5.7
E: Sub-process /usr/bin/dpkg returned an error code (1)






share|improve this question














All solutions listed here for removing MySQL fails:



Uninstall MySQL from Ubuntu 16.04



and



Removing MariaDB Installs MySQL and vice-versa



These are my errors:



$ sudo apt-get purge mysql*
$ sudo apt-get autoremove
$ sudo apt-get autoclean
$ sudo apt-get dist-upgrade
$ sudo apt-get install mysql



$ apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
mysql-server-core-5.7
0 upgraded, 0 newly installed, 1 to remove and 131 not upgraded.
2 not fully installed or removed.
After this operation, 46.2 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 287191 files and directories currently installed.)
Removing mysql-server-core-5.7 (5.7.22-0ubuntu0.16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up mysql-common (5.7.22-0ubuntu0.16.04.1) ...
update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback doesn't exist
dpkg: error processing package mysql-common (--configure):
subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of mysql-client-5.7:
mysql-client-5.7 depends on mysql-common (>= 5.5); however:
Package mysql-common is not configured yet.

dpkg: error processing package mysql-client-5.7 (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.

Errors were encountered while processing:
mysql-common
mysql-client-5.7
E: Sub-process /usr/bin/dpkg returned an error code (1)








share|improve this question













share|improve this question




share|improve this question








edited May 20 at 3:26









Thomas Ward♦

41k23112166




41k23112166










asked May 20 at 3:16









jeffschips

113




113











  • This isn't a BBCODE forum. Use StackExchange code formatting, select the text you want to code-format, then click the button that looks like this in your editing window:
    – Thomas Ward♦
    May 20 at 3:17











  • did you do this with mysql still running? If so...
    – Rinzwind
    May 20 at 7:47










  • mysql not running. Doesn't start on startup I always start with sudo systemctl start mysql
    – jeffschips
    May 20 at 12:55
















  • This isn't a BBCODE forum. Use StackExchange code formatting, select the text you want to code-format, then click the button that looks like this in your editing window:
    – Thomas Ward♦
    May 20 at 3:17











  • did you do this with mysql still running? If so...
    – Rinzwind
    May 20 at 7:47










  • mysql not running. Doesn't start on startup I always start with sudo systemctl start mysql
    – jeffschips
    May 20 at 12:55















This isn't a BBCODE forum. Use StackExchange code formatting, select the text you want to code-format, then click the button that looks like this in your editing window:
– Thomas Ward♦
May 20 at 3:17





This isn't a BBCODE forum. Use StackExchange code formatting, select the text you want to code-format, then click the button that looks like this in your editing window:
– Thomas Ward♦
May 20 at 3:17













did you do this with mysql still running? If so...
– Rinzwind
May 20 at 7:47




did you do this with mysql still running? If so...
– Rinzwind
May 20 at 7:47












mysql not running. Doesn't start on startup I always start with sudo systemctl start mysql
– jeffschips
May 20 at 12:55




mysql not running. Doesn't start on startup I always start with sudo systemctl start mysql
– jeffschips
May 20 at 12:55










2 Answers
2






active

oldest

votes

















up vote
0
down vote













It looks like there is an error while configuring mysql-common, and that causes a dependency problem that results in mysql-client-5.7 failing to be removed.



The configuration error is error: alternative path /etc/mysql/my.cnf.fallback doesn't exist, so naturally i'd try to create that path by running sudo touch /etc/mysql/my.cnf.fallback



After that running sudo dpkg-reconfigure mysql-common will reveal if the error is resolved, if it is, you can likely remove mysql now using sudo apt-get purge mysql*



If this did not help, please provide the output/errors of these commands so that me and others can determine the problem further.






share|improve this answer




















  • Thanks for your assistance. Here is the result of your suggestion, after touching /etc/mysql/my.cnf.fallback sudo dpkg-reconfigure mysql-common /usr/sbin/dpkg-reconfigure: mysql-common is broken or not fully installed
    – jeffschips
    May 20 at 12:48











  • This page askubuntu.com/editing-help#comment-formatting explains how to format comments, however, the suggestion to add to two spaces for a line break does not work. Are linebreaks not allowed in comments despite the advise from stackexchange stating in the markdown editing help age to add 2 spaces for a line break?
    – jeffschips
    May 20 at 13:32

















up vote
0
down vote













Solved:



There were two architecture libraries on my system for mysql.



libmysqlclient20:amd64
libmysqlclient20:i386



I removed the i386 and all is solved.






share|improve this answer




















    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',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    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%2f1038254%2fremove-mysql-ubuntu-16-04-all-solutions-have-failed%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    It looks like there is an error while configuring mysql-common, and that causes a dependency problem that results in mysql-client-5.7 failing to be removed.



    The configuration error is error: alternative path /etc/mysql/my.cnf.fallback doesn't exist, so naturally i'd try to create that path by running sudo touch /etc/mysql/my.cnf.fallback



    After that running sudo dpkg-reconfigure mysql-common will reveal if the error is resolved, if it is, you can likely remove mysql now using sudo apt-get purge mysql*



    If this did not help, please provide the output/errors of these commands so that me and others can determine the problem further.






    share|improve this answer




















    • Thanks for your assistance. Here is the result of your suggestion, after touching /etc/mysql/my.cnf.fallback sudo dpkg-reconfigure mysql-common /usr/sbin/dpkg-reconfigure: mysql-common is broken or not fully installed
      – jeffschips
      May 20 at 12:48











    • This page askubuntu.com/editing-help#comment-formatting explains how to format comments, however, the suggestion to add to two spaces for a line break does not work. Are linebreaks not allowed in comments despite the advise from stackexchange stating in the markdown editing help age to add 2 spaces for a line break?
      – jeffschips
      May 20 at 13:32














    up vote
    0
    down vote













    It looks like there is an error while configuring mysql-common, and that causes a dependency problem that results in mysql-client-5.7 failing to be removed.



    The configuration error is error: alternative path /etc/mysql/my.cnf.fallback doesn't exist, so naturally i'd try to create that path by running sudo touch /etc/mysql/my.cnf.fallback



    After that running sudo dpkg-reconfigure mysql-common will reveal if the error is resolved, if it is, you can likely remove mysql now using sudo apt-get purge mysql*



    If this did not help, please provide the output/errors of these commands so that me and others can determine the problem further.






    share|improve this answer




















    • Thanks for your assistance. Here is the result of your suggestion, after touching /etc/mysql/my.cnf.fallback sudo dpkg-reconfigure mysql-common /usr/sbin/dpkg-reconfigure: mysql-common is broken or not fully installed
      – jeffschips
      May 20 at 12:48











    • This page askubuntu.com/editing-help#comment-formatting explains how to format comments, however, the suggestion to add to two spaces for a line break does not work. Are linebreaks not allowed in comments despite the advise from stackexchange stating in the markdown editing help age to add 2 spaces for a line break?
      – jeffschips
      May 20 at 13:32












    up vote
    0
    down vote










    up vote
    0
    down vote









    It looks like there is an error while configuring mysql-common, and that causes a dependency problem that results in mysql-client-5.7 failing to be removed.



    The configuration error is error: alternative path /etc/mysql/my.cnf.fallback doesn't exist, so naturally i'd try to create that path by running sudo touch /etc/mysql/my.cnf.fallback



    After that running sudo dpkg-reconfigure mysql-common will reveal if the error is resolved, if it is, you can likely remove mysql now using sudo apt-get purge mysql*



    If this did not help, please provide the output/errors of these commands so that me and others can determine the problem further.






    share|improve this answer












    It looks like there is an error while configuring mysql-common, and that causes a dependency problem that results in mysql-client-5.7 failing to be removed.



    The configuration error is error: alternative path /etc/mysql/my.cnf.fallback doesn't exist, so naturally i'd try to create that path by running sudo touch /etc/mysql/my.cnf.fallback



    After that running sudo dpkg-reconfigure mysql-common will reveal if the error is resolved, if it is, you can likely remove mysql now using sudo apt-get purge mysql*



    If this did not help, please provide the output/errors of these commands so that me and others can determine the problem further.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered May 20 at 6:51









    x13

    1567




    1567











    • Thanks for your assistance. Here is the result of your suggestion, after touching /etc/mysql/my.cnf.fallback sudo dpkg-reconfigure mysql-common /usr/sbin/dpkg-reconfigure: mysql-common is broken or not fully installed
      – jeffschips
      May 20 at 12:48











    • This page askubuntu.com/editing-help#comment-formatting explains how to format comments, however, the suggestion to add to two spaces for a line break does not work. Are linebreaks not allowed in comments despite the advise from stackexchange stating in the markdown editing help age to add 2 spaces for a line break?
      – jeffschips
      May 20 at 13:32
















    • Thanks for your assistance. Here is the result of your suggestion, after touching /etc/mysql/my.cnf.fallback sudo dpkg-reconfigure mysql-common /usr/sbin/dpkg-reconfigure: mysql-common is broken or not fully installed
      – jeffschips
      May 20 at 12:48











    • This page askubuntu.com/editing-help#comment-formatting explains how to format comments, however, the suggestion to add to two spaces for a line break does not work. Are linebreaks not allowed in comments despite the advise from stackexchange stating in the markdown editing help age to add 2 spaces for a line break?
      – jeffschips
      May 20 at 13:32















    Thanks for your assistance. Here is the result of your suggestion, after touching /etc/mysql/my.cnf.fallback sudo dpkg-reconfigure mysql-common /usr/sbin/dpkg-reconfigure: mysql-common is broken or not fully installed
    – jeffschips
    May 20 at 12:48





    Thanks for your assistance. Here is the result of your suggestion, after touching /etc/mysql/my.cnf.fallback sudo dpkg-reconfigure mysql-common /usr/sbin/dpkg-reconfigure: mysql-common is broken or not fully installed
    – jeffschips
    May 20 at 12:48













    This page askubuntu.com/editing-help#comment-formatting explains how to format comments, however, the suggestion to add to two spaces for a line break does not work. Are linebreaks not allowed in comments despite the advise from stackexchange stating in the markdown editing help age to add 2 spaces for a line break?
    – jeffschips
    May 20 at 13:32




    This page askubuntu.com/editing-help#comment-formatting explains how to format comments, however, the suggestion to add to two spaces for a line break does not work. Are linebreaks not allowed in comments despite the advise from stackexchange stating in the markdown editing help age to add 2 spaces for a line break?
    – jeffschips
    May 20 at 13:32












    up vote
    0
    down vote













    Solved:



    There were two architecture libraries on my system for mysql.



    libmysqlclient20:amd64
    libmysqlclient20:i386



    I removed the i386 and all is solved.






    share|improve this answer
























      up vote
      0
      down vote













      Solved:



      There were two architecture libraries on my system for mysql.



      libmysqlclient20:amd64
      libmysqlclient20:i386



      I removed the i386 and all is solved.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        Solved:



        There were two architecture libraries on my system for mysql.



        libmysqlclient20:amd64
        libmysqlclient20:i386



        I removed the i386 and all is solved.






        share|improve this answer












        Solved:



        There were two architecture libraries on my system for mysql.



        libmysqlclient20:amd64
        libmysqlclient20:i386



        I removed the i386 and all is solved.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 22 at 1:22









        jeffschips

        113




        113






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1038254%2fremove-mysql-ubuntu-16-04-all-solutions-have-failed%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            Which professions warranted travel in Medieval times?

            How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

            Trouble downloading packages list due to a “Hash sum mismatch” error