New answers tagged mysql
0
you can try this:
sudo apt remove --purge --auto-remove mysql-server
0
Try the following steps to add the MySQL repository to your list and install MySQL 8.0. I have not tested this, but according to the docs it should work (unless I made a typing mistake).
Install the MySQL GPG Public key to your APT keyring: (also see this post)
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys 5072E1F5
Add the MySQL Xenial Repo to ...
0
the problem is xampp has created a blank password for the root MySQL database.
If you leave the password field empty you should be good to go.
0
This guidance is helpful:
How to delete broken packages in ubuntu
sudo dpkg --remove --force-remove-reinstreq mariadb-server mariadb-server-10.3 mariadb-client-10.3
sudo apt-get update
sudo reboot
sudo apt-get upgrade
sudo apt install mariadb-server
0
after some google searching it turns out that what I needed to do to resolve this issue was the following
sudo apt-get install libmysqlclient-dev
Now my Perl based mysql scripts seem to be working just fine.
1
The MySQL JDBC driver default behavior apparently changed when updating the OS.
The previous driver turned off transaction auto commits for Java batch updates - manually adding/running setAutoCommit(false) on the data connection dropped the run time back to normal (apparently it was running atomic transactions for 1000 some inserts).
This is a good example ...
0
I found out libmysql-java is changed to another package with Ubuntu 20.04. Once I installed the new package, everything worked fine.
0
I faced same error due to problem in my upgrade from ubuntu 18.04 to Ubuntu 20.04. What I did is get MariaDB instead also make sure when you do purge MySQL and if asked to remove databases in the directory, click on "No". It would not delete the databases so you will have your old databases and no data loss.
I used these commands:
sudo apt-get ...
0
As @mariaczi found out, the problem is, that there isn't enough RAM for MySQL to start.
I tried to add swap space, but without success. Maybe this is not possible on my virtual server.
I finally ended up with adding the following to /etc/my.cnf:
[mysqld]
innodb_buffer_pool_size=100M
After that, I restarted the server and I was able to use MySQL.
0
With heavy adoption of systemd as system manager and init system for debian based distributions like ubuntu , we can now use systemctl commands to prevent a service from automatically starting at boot.
for example :
sudo systemctl disable apache2
To start using it when required , you can use:
sudo systemctl start apache2
To stop using it, you can use:
...
0
There is a problem clearly stated (I copied the relevant parts):
mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2 - No such file or directory)
[ERROR] Failed to access directory for --secure-file-priv.
Please make sure that directory exists and is accessible by MySQL Server. Supplied value : /va
Aborting
Please take a look at https://wiki....
0
This is what I did, in ubuntu terminal i located mysql by typing in
which mysqld
For which I got an output
/usr/sbin/mysql
Further mysql was inside lampp as well, i located it by
mysql -u root -p -h 127.0.0.1 -e "select @@socket"
For which I got an output
/opt/lampp/var/mysql/mysql.sock
Then i typed in
sudo -i
and pressed enter to open as root,...
0
There is thing thig called as dependency. When you install a software, it might depend on some other extra package to provide some system calls or some service. When you remove this software, and the extra packages are no longer needed by any software, then it is safe to remove these packages also.
In your case, when it says following packages were ...
0
The line in etc/apt/sources.list.d/trusty.list that is generating the component misspelt in sources.list error message is for a trusty repository and you are using bionic (18.04). Remove the line in /etc/apt/sources.list.d/mysql.list the contains the string http://repo.mysql.com/apt/ubuntu trusty by preceding it with a # character in order to turn it into a ...
0
This is not really a answer to your question, but I had similar problem with mysql-server after upgrade of my Ubuntu server (18.04 -> 20.04).
2020-10-03T16:07:22.635008Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21-0ubuntu0.20.04.4) (Ubuntu).
2020-10-03T16:07:23.415771Z 0 [Warning] [MY-011068] [Server] The syntax '...
Top 50 recent answers are included
