I am getting this error while installing MySQL 5.6.10. I have other versions of MySQL (5.1 and 4.1) installed and there seems to be a conflict in the my.cnf.
Removing /etc/my.cnf is not an option.
[amitra#dev4.lab user.amitra]$ sudo /usr/local/mysql5610/scripts/mysql_install_db --basedir=/usr/local/mysql5610/ --datadir=/var/home/amitra/mysql5610/user.amitra
Installing MySQL system tables...2013-08-07 00:03:44 0 [ERROR] /usr/local/mysql5610//bin/mysqld: ambiguous option '--log=/var/lib/mysql/mysql.log' (log-bin, log_slave_updates)
2013-08-07 00:03:44 0 [ERROR] Aborting
2013-08-07 00:03:44 0 [Note] Binlog end
================
"log=/var/lib/mysql/mysql.log" is defined in the /etc/my.cnf and cant be removed. (Cant be changed as globally used)
I also tried to install using --defaults-file=/usr/local/mysql5610/my.cnf but that didn't work.
http://dev.mysql.com/doc/refman/5.6/en/server-options.html#option_mysqld_log
The --log option was removed in MySQL 5.6.1 (along with the log system variable). Instead, use the --general_log option to enable the general query log and the --general_log_file=file_name option to set the general query log file name.
In fact, the log option has been deprecated since MySQL 5.1.29 (circa October 2008).
You don't have to remove your my.cnf, but you cannot use the log option anymore. You must change it according to the instructions above, and it will work on all your other instances of MySQL 5.1 and greater.
Related
I am installing Galera 4 on top of MySQL 8 on Debian but can't make it work. Once I start first node with bootstrap command:
mysqld_bootstrap
it starts with the following options:
/usr/sbin/mysqld $$'$\'$\\\'--wsrep-new-cluster --wsrep-on\\\'\'' --wsrep_start_position=00000000-0000-0000-0000-000000000000:-1
Problem is there is no pid file created and even though it appears to be running and I can't connect to the database.
There is nothing going to the log file either so I think it is ommiting the config files.
I have tried running config validator:
mysqld --validate_config
but it hangs on futex (checked with strace). In both cases it is not possible to kill mysqld normally and -9 option has to be used.
LXC is used to run this instance with following kernel:
Linux node01 4.15.18-26-pve #1 SMP PVE 4.15.18-54 (Sat, 15 Feb 2020 15:34:24 +0100) x86_64 GNU/Linux
The answer was pretty obvious after some investigation. No rsync used to sync the cluster was installed on the nodes so they can't sync together.
I'm triing to install the MySQL enterprise plugin openssl_udf. I need it for generating RSA keys and RSA encryption. I got the openssl_udf.dll from Oracle and tried the following codes with failures.
INSTALL PLUGIN openssl_udf SONAME 'openssl_udf.dll'
Failure:
Error Code: 1126. Can't open shared library 'C:\Program Files\MySQL\MySQL Server 5.7\lib\plugin\openssl_udf.dll'
And:
CREATE FUNCTION asymmetric_decrypt RETURNS STRING
SONAME 'openssl_udf.dll';
Failure:
Error Code: 1126. Can't open shared library 'openssl_udf.dll' (errno: 193 )
Does someone know how to use it?
Sources:
https://dev.mysql.com/doc/refman/5.7/en/install-plugin.html
http://dev.mysql.com/doc/refman/5.7/en/enterprise-encryption-installation.html
So it was simple after all.
After deinstalling MySQL Server (Community) the first time, I didn't delete ALL MySQL files and folders manually, so that the Enterprise installer must have installed the Community distribution again. After deinstalling and removing all files and than reinstalling, everything works fine.
Installed innotop 1.10.0 on centos7 mysqlversion is 5.7.12. When i run innotop in centos server and option T selected it gives me the use of unintiaized value error how do i fix it.
WThread Waiting Query WWait BThread BRowsMod BAge BWait BStatus
Blocking QueryUse of uninitialized value in list assignment at /usr/bin/innotop line 5818.
yum update innotop solved the issue.
I'm using the MySql Server which comes with Cygwin. No matter whether I start it like this:
mysqld --tmpdir=/cygdrive/c/temp start
or like this:
mysqld start --tmpdir=/cygdrive/c/temp
I always get the error message
151104 15:50:48 [Note] mysqld (mysqld 5.5.45) starting as process 8784 ...
151104 15:50:48 [Warning] Can't create test file /var/lib/mysql/CMTCL033974.lower-test
151104 15:50:48 [Warning] Can't create test file /var/lib/mysql/CMTCL033974.lower-test
It looks as if the --tmpdir option would be ignored.
BTW, the directory /cygdrive/c/temp exists and is writeable.
It seems to be easy: --tmpdir does not affect the location of these files. They always have to be under /var/lib, so I manually created /var/lib/mysql, and the error message disappeared.
However, mysqld now complains about the start parameter, but this is an unrelated issue, where I will open a separate thread for it, if I can't figure it out by myself....
I have MariaDB installed (as part of Fedora installation) on Fedora 21. ODBC is also installed. BUT, when I go to test the ODBC configuration (or when Asterisk attempts to use ODBC) I get an error in free():invalid pointer.
odbcinst.ini
[MySQL]
Description=ODBC for MySQL
Driver=/usr/lib64/libmyodbc5.so
Setup=/usr/lib64/libodbcmyS.so
FileUsage=1
UsageCount=2
odbc.ini
[asterisk]
Description=MySQL connection to 'asterisk' database
Driver=MySQL
Database=asteriskdb
Server=localhost
UserName=<theusername>
Password=<thepassword>
Port=3306
Socket=/var/lib/mysql/mysql.sock
Connecting to the database using mysql works perfectly fine using these credentials. But doing:
echo "select 1"|isql -v asterisk theusername thepassword
results in this:
*** Error in `isql': free(): invalid pointer: 0x00000000011c4e58 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7850e)[0x7fdd0ef7850e]
/lib64/libc.so.6(cfree+0x5b5)[0x7fdd0ef84165]
/usr/lib64/libmyodbc5.so(MySQLGetPrivateProfileStringW+0x132)[0x7fdd083381c2]
/usr/lib64/libmyodbc5.so(ds_lookup+0x5d)[0x7fdd08336c3d]
/usr/lib64/libmyodbc5.so(MySQLConnect+0xbe)[0x7fdd08316a1e]
/lib64/libodbc.so.2(SQLConnect+0x9e5)[0x7fdd0fb41745]
isql[0x402908]
/lib64/libc.so.6(__libc_start_main+0xf0)[0x7fdd0ef1ffe0]
isql[0x402c31]
======= Memory map: ========
I can provide the rest of the core dump if it will help anyone.
Any suggestions for what is causing this and how to prevent it? I need ODBC working.
I had the same problem on my F21 86_64.
The resolution for me was to install a newer version (logged in as root):
1 remove actual odbc-version (5.2.2 if I remember well)
yum remove mysql-connector-odbc
2 Searching the newest version of mysql-connector-odbc-5.3.4-1.x86_64.rpm) at:
http://dev.mysql.com/get/Downloads/Connector-ODBC/5.3/mysql-connector-odbc-5.3.4-1.x86_64.rpm (you need to subscribe)
yum localinstall --nogpgcheck mysql-connector-odbc-5.3.4-1.x86_64.rpm
3 symbolic link creation because unixODBC points still to
/usr/lib64/libmyodbc5.so instead of /usr/lib64/libmyodbc5w.so
ln -s /usr/lib64/libmyodbc5w.so /usr/lib64/libmyodbc5.so
4 if needed don't forget to modify (in ~/.odbc.ini)
.....
Driver64=/usr/lib64/libmyodbc5w.so
....
Hope this helps
Roman