MySQL MHA binlog setting check failed - mysql

i try to config MHA 0.56 for mysql 5.7, everything is done. when i run masterha_check_repl, i get the following message:
executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/data/mysql --output_file=/data/mysql
Failed to save binary log: Set --start_file=<starting_binlog_filename> or --binlog_prefix=<binlog_file_prefix>
Binlog setting check failed!
I modified MasterMonitor.pm added
--binlog_prefix=mysql-bin
into the command , but it doesn't work, still gave me above error message.
I have no idea on how to deal with it..

Try setting binlog_prefix in my.cnf rather than via command line.

I made a mistake when I copied other's app1.cnf explanation into my app1.cnf.
The #comment after parameters in the same line should be removed.

Related

Error executing task write() argument must be str, not bytes | MySQL Workbench

After a clean install of Windows 10 when I started to use MySQL workbench I have this error when I try to dump a database.
I could not find anything about it anywhere, the only thing I find are problems with phyton, but nothing related with Workbench.
Output after dumping a database:
08:29:00 Dumping foo(all tables)
Error executing task write() argument must be str, not bytes
08:29:01 Export of b'C:\\Users\\erick\\Documents\\dumps\\Dump20210121 (2).sql' has finished
And the output file is in blank, some ideas?
You can disable (uncheck) the option create schema. It is annoying but it works.
If you have the latest MySQL Workbench (8.0.23), just uninstall and install MySQL Workbench 8.0.20. That worked for me.
Another workaround to this issue is to edit wb_admin_export.py.
In dump_to_folder (line 1679) replace
self.out_pipe = open(path,"w")
with
self.out_pipe = open(path,"wb")
In dump_to_file (line 1957) replace
self.out_pipe = open(self.path,"w")
with
self.out_pipe = open(self.path,"wb")
If you a using version 8.0.23, update to 8.0.25 or above.... it will fix this issue

PentahoSystem.ERROR_0014

After doing all the set up for mysql repository for pentaho bi-server 6.1. Here is what I got when I restart the server:
" The following errors were detected
One or more system listeners failed. These are set in the systemListeners.xml.
org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.engine.services.connection.datasource.dbcp.DynamicallyPooledDatasourceSystemListener
Please see the server console for more details on each error detected.
In systemListener.xml file you need to comment the following lines:
<!--<bean id="pooledDataSourceSystemListener" class="org.pentaho.platform.engine.services.connection.datasource.dbcp.PooledDatasourceSystemListener" />-->
<!--bean id="dynamicallyPooledDataSourceSystemListener" class="org.pentaho.platform.engine.services.connection.datasource.dbcp.DynamicallyPooledDatasourceSystemListener" />

MySQL console error unknown option '--root'

When I try to access mysql in the command line get the following error:
mysql: unknown option '--root'
Mysql is installed via brew, version 5.6.27, OSX El Capitan with SIP turned off.
This is an old thread however, it can help someone. I came up with the same issue then later I have discovered that there was a wrong entry in .my.cnf file in my home folder. You probably have a wrong entry on your
/root/.my.cnf or .my.cnf
file on your home directory.
Renaming the file will help you solve the issue.
I had such error (but with message "mysql: unknown option --mysqld]") when forgot opening '[' symbol in /etc/mysql/my.cnf, It was looking like:
mysqld] #<-- forgot opening [
innodb-file-format=barracuda
innodb-file-per-table=1
...
Check this! (thanks to Siru, found in a moment!)

mysql: ERROR: Option 'debug=d:t:o,/var/log/list.log' used, but is disabled

In my app I get
mysql: ERROR: Option 'debug=d:t:o,/var/log/list.log' used, but is disabled
how can I enable --debug in mysql?
If possible without changing my.conf.
I found the following solution
Instead of
mysql --debug .......
I do
mysql ............... <<EOF 2>>/var/log/list.log
its saving errors and warnings to the file

pentaho integration with mysql-5.X

When I was trying to replace the hsqldb with the mysql-5.X I get the following error with quartz error failed to initialize:-
Pentaho Initialization Exception
The following errors were detected
One or more system listeners failed. These are set in the systemListeners.xml.
PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.scheduler.QuartzSystemListener
Please see the server console for more details on each error detected.
Did you run the quartz scripts which setup the quartz db? they are provided in the solution repository.
Otherwise pastebin the full log, it's impossible to tell without more info. suspect somewhere you'll either have a authentication issue, or no mysql driver in your classpath.
For a clear guide on how to do this, follow here:
http://www.prashantraju.com/2010/12/pentaho-3-7-with-mysql-postgresql-oracle-and-sql-server/
I also received the error message
PentahoSystem.ERROR_0014 – Error while trying to execute startup sequence for org.pentaho.platform.scheduler.QuartzSystemListener
when trying to bring up the service. I found this solution after searching a few different threads:
Remove commented out portion of these properties (or copy and paste from here, and modify as necessary) in quartz.properties (located in pentaho-solutions/system/quartz):
org.quartz.dataSource.quartz.driver = com.mysql.jdbc.Driver
org.quartz.dataSource.quartz.URL = jdbc:mysql://localhost:3306/quartz
org.quartz.dataSource.quartz.user = pentaho_user
org.quartz.dataSource.quartz.password = password
org.quartz.dataSource.quartz.maxConnections = 5
org.quartz.dataSource.quartz.validationQuery= select 1
Also comment out the JNDI Url:
#org.quartz.dataSource.myDS.jndiURL = Quartz