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?
Related
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
I have been observing the build fail issue for this
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.springframework.cloud:spring-cloud-netflix-hystrix-stream:2.0.1.BUILD-SNAPSHOT (E:\springcloud\spring-cloud-netflix-master\spring-cloud-netflix-master\spring-cloud-netflix-hystrix-stream\pom.xml) has 1 error
[ERROR] Unresolveable build extension: Plugin org.springframework.cloud:spring-cloud-contract-maven-plugin:1.2.4.RELEASE or one of its dependencies could not be resolved: Failure to find org.springframework.cloud:spring-cloud-netflix-hystrix-contract:jar:2.0.1.BUILD-SNAPSHOT in https://repo.spring.io/libs-snapshot-local was cached in the local repository, resolution will not be reattempted until the update interval of spring-snapshots has elapsed or updates are forced -> [Help 2]
Please run ./scripts/build.sh to fix 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 a Jenkins Job that runs SonarRunner on a Maven project composed of several modules i'm using msql db for sonar. The build fails showing that
[ERROR] Unable to save measure for metric [pdf-data] on component [com.XX:xxx-parent]
[ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.3.1:sonar (default-cli) on project XXX-parent: Unable to save measure for metric [pdf-data] on component [com.XX:XXX-parent]:
[ERROR] ### Error updating database. Cause: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (3676748 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable.
[ERROR] ### The error may involve org.sonar.api.database.model.MeasureMapper.insertData-Inline
[ERROR] ### The error occurred while setting parameters
[ERROR] ### SQL: INSERT INTO measure_data (measure_id, snapshot_id, data) VALUES (?, ?, ?)
[ERROR] ### Cause: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (3676748 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.3.1:sonar (default-cli) on project XXX-parent: Unable to save measure for metric [pdf-data] on component [com.XXX:XXX-parent]
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
I encountered this error as well. The MySQL database that your SonarQube is using only allows LOB contents up to 1 MB by default and the content it is trying to save is larger than that as stated in the error message.
com.mysql.jdbc.PacketTooBigException: Packet for query is too large (3676748 > 1048576).
The solution is that you need to increase the max_allowed_packet setting for the MySQL instance the SonarQube is using.
You can change this value on the server by setting the max_allowed_packet' variable.
Instructions can be found here.
Start the server with the desired setting, i.e. mysqld --max_allowed_packet=16M for 16 MB max.
Or more permanently, modify the config file (my.cnf on Linux systems, possibly my.ini on Windows) by adding the setting under the [mysqld] section.
[mysqld]
max_allowed_packet=16M
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.