Few days ago I have reinstalled my system and installed mariadb as default mysql server. And now i have noticed a problem - whenever I try to create a dump of any database - it is created without data. Inside of dump file most of tables does not have insert query with data and dump file is very small (below 1mb).
I have tried to create dump files in a few ways:
Phpmyadmin export
Command line mysqldump -u user -p databesaname > dumpfile.name
But result is the same. So is there a way to fix this without reinstalling mysql server? I dont want to lose all my databases.
Specifications:
Server: Localhost via UNIX socket
Server Type: MariaDB
Server version: 10.0.34-MariaDB-0ubuntu0.16.04.1 - Ubuntu 16.04
Apache/2.4.18 (Ubuntu)
Databesa client version : libmysql - mysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $
PHP version: 7.0.30-0ubuntu0.16.04.1
Related
When migrating a WordPress database to a new server it get the the error:
ERROR 1064 (42000) at line 194036: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'The dynamic response body size is over the limit, the response will be trunca' at line 413
I've tried both importing it in phpMyAdmin and also command line with the following command:
mysql -uroot -p******* sout_travel < yY8tB9M7SaUz2P.sql
I really don't know much about MySQL or MariaDB in this case. I'd appreciate if someone could shed a light...
Source Server Specs:
Server: Localhost via UNIX socket
Server type: MariaDB
Server connection: SSL is not being used Documentation
Server version: 10.1.44-MariaDB-0ubuntu0.18.04.1 - Ubuntu 18.04
Protocol version: 10
User: yY8tB9M7SaUz2P#localhost
Server charset: UTF-8 Unicode (utf8)
LiteSpeed
Database client version: libmysql - mysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $
PHP extension: mysqliDocumentation curlDocumentation mbstringDocumentation
PHP version: 7.0.33-13+bionic
Destination Server Specs:
Server: Localhost via UNIX socket
Server type: MariaDB
Server connection: SSL is not being used Documentation
Server version: 10.1.44-MariaDB-0ubuntu0.18.04.1 - Ubuntu 18.04
Protocol version: 10
User: root#localhost
Server charset: UTF-8 Unicode (utf8)
LiteSpeed
Database client version: libmysql - mysqlnd 5.0.12-dev - 20150407 - $Id: 3591daad22de08524295e1bd073aceeff11e6579 $
PHP extension: mysqli Documentation curl Documentation mbstring Documentation
PHP version: 7.2.30-1+bionic
Your SQL file (yY8tB9M7SaUz2P.sql) seems to be invalid. Open it with your favorite text editor and you'll probably find the text towards end of the file:
The dynamic response body size is over the limit, the response will be trunca
Sounds like the process that generates the .sql file for you is being interrupted and can't complete, thus leaving the file invalid. If I had to guess, and I have to, that's part of the error message explaining what's the issue generating the SQL file. Your problem isn't loading the SQL file, but generating it.
I use windows and I have previously installed mysql 5.5 for some legacy project, and now I want to use 5.7 for a new one, so I installed 5.7 in another directory, on another port and having different data directory, my problem is when i launch mysql from cmd like:
W:\MySQL57\bin> mysql -u root -p
It results in this:
W:\MySQL57\bin>mysql -u root -p
Enter password: *****
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.5.54-log MySQL Community Server (GPL)
And I am definitely sure that MySQL57 is directory for 5.7 MySQL, so what's wrong with mysql command line tool and how can i fix it to be able to use both mysqls in cmd?
The mysql command you are using is probably the 5.7 version, you can check this with :
W:\MySQL57\bin>mysql -v
But this is just the client !
The problem is your server version, you may have 2 versions running (5.5 and 5.7), and as you haven't specified the port you are using the default one which is used by the first server (5.5).
Try to find the port for the second version (3307 ?) or kill the 5.5 server when you are connecting to the 5.7.
You are calling the default mysql set in Environment Variable. If you want to use a specific mysql, you need to provide the path too
W:\MySQL57\bin>"W:\MySQL57\bin\mysql" -u root -p
In case of mysql not working, you can call mysqld.
If you want mysql 5.7 to be default, just change it from Environment Variable https://dev.mysql.com/doc/mysql-windows-excerpt/5.7/en/mysql-installation-windows-path.html
Server type: MariaDB
Server version: 10.1.19-MariaDB - MariaDB Server
Apache/2.4.6 (Red Hat Enterprise Linux) PHP/7.0.10
Database client version: libmysql - mysqlnd 5.0.12-dev - 20150407 - $Id: 241ae00989d1995ffcbbf63d579943635faf9972 $
All queries in phpMyAdmin work fine except for any DELETE query, I know they are correct because they work if I run them in a ssh terminal mysql client. But phpMyAdmin only shows "Loading...".
Anyone got a solution for this?
Best Regards
Cisco
After upgrade of apache version (5.6.12) to the latest mysql returns duplicate errors importing dump files.
The simple question is that how to export the mysql dump file that works in all php mysql and mysql.
Importing File to : Server version: 5.5.27 - MySQL Community Server (GPL).
Exporting File From : Server version: 5.5.44-37.3-log - Percona Server (GPL).
No Matter what your Server version is you can use
mysql shell
The command
mysql -uroot -ppass DATABASE_NAME < /your/path/to/dump.sql
I upgraded my installation of MySQL on my Mac OS X 10.8.3 using homebrew
brew install mysql
Everything seemed to go smoothly, but...not really, as it turns out.
I cannot add a new user (neither through the command line nor through phpmyadmin. I always get the error
Error in processing request: #2006 MySQL server has gone away
I can create new databases without a problem, and I can install, for example Joomla 3.1.1 with no problems.
However, when I try to install a new extension into my Joomla installation, I get errors. For example, I get the following error when I try to install a component from NoNumber:
1062 Duplicate entry '1' for key 'PRIMARY' SQL=INSERT INTO `u5z87_extensions` (`name`,`type`,`element`,`folder`,`client_id`,`enabled`,`access`) VALUES ('plg_system_nnframework','plugin','nnframework','system','0','1','1')
Same thing for many other extensions.
I tried to start mysql with
mysql.server start --log-warnings=2
and it started with no problem
Starting MySQL
SUCCESS!
I looked up issues where error #2006 were being reported and how to solve them, and they referred to modifying /etc/my.cnf but there is no /etc/my.cnf configuration file on my system, and there wasn't one in the previous installation of MySQL 5.5.29 (also installed with homebrew) and I had no problems.
I ran brew doctor and the output is below
$ brew doctor
Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.
Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
/usr/local/opt/php54/bin/php-config
The output from brew --config is also below:
$ brew --config
HOMEBREW_VERSION: 0.9.4
ORIGIN: https://github.com/mxcl/homebrew
HEAD: 86ce842c700a47abdc354e80cc3b0b3938ab2132
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
CPU: 8-core 64-bit nehalem
OS X: 10.8.3-x86_64
Xcode: 4.6.2
CLT: 4.6.0.0.1.1365549073
LLVM-GCC: build 2336
Clang: 4.2 build 425
X11: 2.7.4 => /opt/X11
System Ruby: 1.8.7-358
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /Users/alisamii/.rvm/rubies/ruby-1.9.3-p374/bin/ruby
Exploring a little further, I tried to revert to my previous install of MySQL using
brew switch mysql 5.5.29
This resulted in the following output:
$ brew switch mysql 5.5.29
Cleaning /usr/local/Cellar/mysql/5.5.29
Cleaning /usr/local/Cellar/mysql/5.6.10
135 links created for /usr/local/Cellar/mysql/5.5.29
I then accessed mysql from the command line and ran status:
mysql> status
--------------
mysql Ver 14.14 Distrib 5.5.29, for osx10.8 (i386) using readline 5.1
Connection id: 13
Current database:
Current user: alisamii#localhost
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server version: 5.6.10 Source distribution
Protocol version: 10
Connection: Localhost via UNIX socket
Server characterset: utf8
Db characterset: utf8
Client characterset: utf8
Conn. characterset: utf8
UNIX socket: /tmp/mysql.sock
Uptime: 1 hour 56 min 24 sec
As you can see above, it reports mysql Ver 14.14 Distrib 5.5.29, for osx10.8 (i386) using readline 5.1
But, it also says Server version: 5.6.10 Source distribution
So something isn't syncing up.
Furthermore, when I show databases, I get the following output:
mysql> show databases
-> ;
+--------------------+
| Database |
+--------------------+
| information_schema |
+--------------------+
1 row in set (0.00 sec)
But I know I have more than just an information_schema database.
So, somehow, it seems to me that mysql is not connecting to the right server, as phpmyadmin reports the same server information that mysql's status command reports: Software version: 5.6.10 - Source distribution.
At this point, I am completely lost, and would really need some help.
OK, so partially resolved the issue.
At the recommendation of https://stackoverflow.com/users/201789/tehshrike I read the pages related to mysql_update and followed the recommendations there.
Upgrading MySQL does not upgrade the information_schema, and so some things don't work. This command helps fix some of those issues.
Now, I can add new users and the #2006 - MySQL server has gone away error is no longer an issue.
However, I am still getting the #1062 errors when trying to install extensions in Joomla, for example. Still exploring solutions to that. Will update this answer with details when solved.