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....
Related
I'm hoping someone can help me, i've been working on a website using wordpress for the past 3 months on my mac, only when i tried to access it this past weekend the mysql service won't run and i keep getting the error
ERROR: Failed to start "mysql": cannot start service: Process exited with status 3
Can anyone help me get my site up and running again?
This is the first tie using Wordpress so i'm not really sure what I'm doing.
Any help would be greatly appreciated
i've managed to run mysql in safe mode and this is the code it gives
Last login: Mon Jul 13 22:23:09 on ttys001
Lukes-iMac:~ lukejackson$/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/mysqld_safe ; exit;
/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/my_print_defaults: line 12: /Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/my_print_defaults.bin: cannot execute binary file
/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/my_print_defaults: line 12: /Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/my_print_defaults.bin: Undefined error: 0
/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/my_print_defaults: line 12: /Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/my_print_defaults.bin: cannot execute binary file
/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/my_print_defaults: line 12: /Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/my_print_defaults.bin: Undefined error: 0
/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/mysqld_safe: line 674: /opt/bitnami/mysql/data/Lukes-iMac.err: No such file or directory
Logging to '/opt/bitnami/mysql/data/Lukes-iMac.err'.2020-07-13T21:43:10.6NZ mysqld_safe Starting mysqld daemon with databases from /opt/bitnami/mysql/data/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/mysqld_safe: line 144: /opt/bitnami/mysql/data/Lukes-iMac.err: No such file or directory
/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/mysqld_safe: line 199: /opt/bitnami/mysql/data/Lukes-iMac.err: No such file or directory
/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/mysqld_safe: line 937: /opt/bitnami/mysql/data/Lukes-iMac.err: No such file or directory
2020-07-13T21:43:10.6NZ mysqld_safe mysqld from pid file /opt/bitnami/mysql/data/Lukes-iMac.pid ended
/Users/lukejackson/.bitnami/stackman/machines/wordpress/volumes/root/mysql/bin/mysqld_safe: line 144: /opt/bitnami/mysql/data/Lukes-iMac.err: No such file or directory
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]
Your local database server is failing to start up, and it's being started with enough layers between you and it that any reporting it's doing on why is being hidden. To attempt to start it while being able to see what it's complaining about, try the methodology here: start MySQL server from command line on Mac OS Lion
Bitnami Engineer here.
Thank you for using our solution. Please note that the OS X VM solution is a VM we build and configure with the application. You need to open the Console of the VM when running any command, can you try to open the console and run the start command?
sudo /opt/bitnami/ctlscript.sh start
You can use the ctlscript.sh file to stop the services and get the status as well. If the database can't be started, you can take a look at the database's log file (/opt/bitnami/mysql/data/mysqld.log) to get more information
sudo tail -n 30 /opt/bitnami/mysql/data/mysqld.log
I’m running WAMP64 on Windows 10 (development machine), with MySQL 5.7.19. I’ve installed the keyring_file plugin. MySQL starts, but the keyring_file is not found, so the following errors:
[ERROR] Plugin keyring_file reported: 'File
'C:/wamp64/bin/mysql/mysql5.7.19/lib/plugin/keyring_file.dll' not
found (Errcode: 13 - Permission denied)' [ERROR] Plugin keyring_file
reported: 'keyring_file initialization failure. Please check if the
keyring_file_data points to readable keyring file or keyring file can
be created in the specified location. The keyring_file will stay
unusable until correct path to the keyring file gets provided'
The file is on the specified path:
My.ini includes:
The variables loads:
The plugin appears to load:
And the mysql service has Local System permission:
I have tried uninstalling and re-installing the plugins, granting broader permissions on the keyring.dll file, and of course I have re-started the MySQL service after each test.
So my question is why am I getting Errcode 13, permission denied? What am I missing here? Thanks.
The issue is that you are specifing the .dll file for the keyring_file_data variable, not the location of a file to use for the keyring. It should be something like:
keyring_file_data=C:/some/path/to/keyring
https://dev.mysql.com/doc/refman/5.7/en/keyring-file-plugin.html
2019-03-19 01:43:26 22929 [Warning] Buffered warning: Could not increase number of max_open_files to more than 79992 (request: 4294967295)
2019-03-19 01:43:26 22929 [Warning] Buffered warning: Changed limits: table_open_cache: 39915 (requested 524288)
This is my problem in mysql when starting service this is from log. I did not yet google solution because FREEBSD OS
It seems like you have hit this FreeBSD bug, which was reported for package mysql57-server-5.7.12.
A workaround is to change the permissions of file /usr/local/etc/mysql/my.cnf to something like 646 (the key point is that others need write permissions).
You can also see this this FreeBSD forum thread for more information..
Just built MySQL from sources, on Windows, and trying to run:
mysqld --initialize
It seems that the process just freezes and never returns.
It created a data folder with a *.err file inside, with the following text:
2018-10-12T16:02:43.838418Z 0 [System] [MY-013169] [Server] E:\dev\mysql-server-8.0\bld\runtime_output_directory\Debug\mysqld.exe (mysqld 8.0.12-debug) initializing of server in progress as process 12584
But nothing happens... it's just stuck.
Any thoughts on what am I doing wrong?
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.