Known Replikwando Errors - Revision history

Broy: /* Repushing */ Added a case we recently investigated to the troubleshooting advice

2016-12-19T17:13:54Z

Repushing: Added a case we recently investigated to the troubleshooting advice

← Older revision		Revision as of 12:13, 19 December 2016
Line 89:		Line 89:
	== Bad Behavior ==		== Bad Behavior ==
	===Repushing===		===Repushing===
			====Replikwando looks like it's working, but only runs the same six "junk" queries over and over====
			* '''Cause'''
			Replikwando cannot open/read the binary log files.

			* '''Resolution'''
			Verify that the binary log files can be read by the user Replikwando is running under. This can be done via the mysqlbinlog program (which Replikwando uses for this purpose also).
			mysqlbinlog --base64-output=DECODE-ROWS -v <binary log file>

	====Repush finishes, but no record is left in the messages table, so it never resyncs====		====Repush finishes, but no record is left in the messages table, so it never resyncs====
	* '''Cause'''		* '''Cause'''

Jmckinstry: /* Bad Behavior */

2015-08-06T18:29:56Z

Bad Behavior

@@ Line 98: / Line 98: @@
 As of 1.8.0, the following error will show when this problem occurs: "Repush failed! No message sent to Heartbeat; Database will not sync to HTP!"
 ==== Tables and views push, but functions and procedures are missing ====
 * '''Cause'''
@@ Line 106: / Line 105: @@
 Replikwando must be given SELECT privs to mysql.proc.  This table shows functions and procedures associated with all databases on a server, but cannot be altered unless you for some reason give the Replikwando user UPDATE status.  Just don't do that :)
 ==== Replikwando2 (the gui version) 'works', but ReplikwandoService doesn't ====
 * '''Cause'''
@@ Line 163: / Line 179: @@
 You should now be able to have Replikwando successfully re-push the client's data with normal replication afterwards.
 ====Server is full of mysqlbinlog.exe instances====
@@ Line 183: / Line 191: @@
 *'''Potentially Resolved''' in 1.8.0.

Jmckinstry: /* Bad Behavior */

2015-08-06T18:28:27Z

Bad Behavior

@@ Line 88: / Line 88: @@
 == Bad Behavior ==
 ==== Tables and views push, but functions and procedures are missing ====
 * '''Cause'''

Jmckinstry: /* Server is full of mysqlbinlog.exe instances */

2015-08-06T18:20:20Z

Server is full of mysqlbinlog.exe instances

← Older revision		Revision as of 13:20, 6 August 2015
Line 170:		Line 170:
	**Do NOT kill an active mysqlbinlog.exe! Replikwando is actively receiving data from it, and things can go horribly wrong if you kill it!		**Do NOT kill an active mysqlbinlog.exe! Replikwando is actively receiving data from it, and things can go horribly wrong if you kill it!
	*A more permanent resolution is to use a different spawning method (we currently use ::CreateProcess). I believe (but may be wrong) that this issue occurs because ::CreateProcess returns COULDNT_CREATE_PROCESS or something like that, even though the process is made. It could also be an error in the handling of the closing of a windows-based thread, both of which should be investigated.		*A more permanent resolution is to use a different spawning method (we currently use ::CreateProcess). I believe (but may be wrong) that this issue occurs because ::CreateProcess returns COULDNT_CREATE_PROCESS or something like that, even though the process is made. It could also be an error in the handling of the closing of a windows-based thread, both of which should be investigated.

			*'''Potentially Resolved''' in 1.8.0.

	==== Replikwando runs and seems to work right, but dies during repushes ====		==== Replikwando runs and seems to work right, but dies during repushes ====

Jmckinstry: /* Replikwando2 successfully re-pushes, but then pushes tons of junk data */

2015-07-16T18:48:55Z

Replikwando2 successfully re-pushes, but then pushes tons of junk data

← Older revision		Revision as of 13:48, 16 July 2015
Line 117:		Line 117:

	==== Replikwando2 successfully re-pushes, but then pushes tons of junk data ====		==== Replikwando2 successfully re-pushes, but then pushes tons of junk data ====
			*'''Possible cause'''

			Replikwando is not using the correct mysqlbinlog.exe file.

			*'''Resolution'''

			*Change replication.ini's [fromserver].mysqlbinpath to be the same bin path that the MySQL instance is running
			**Windows: This query will tell you where to look for the right bin folder: <source lang = 'MySQL'>SHOW VARIABLES LIKE 'basedir';</source>
			**Linux: The Replikwando install creates a bin/mysql/mysqlbinlog.exe entry that you should point to

	*'''Possible cause'''		*'''Possible cause'''

Line 131:		Line 141:
	If you see any of the following, the binary log is corrupt:		If you see any of the following, the binary log is corrupt:
	*Binlog names are inconsistent ('mysqlbinlog-000001.bin', 'servername-000001.bin' in the same list)		*Binlog names are inconsistent ('mysqlbinlog-000001.bin', 'servername-000001.bin' in the same list)
	*Binlog names repeat (seeing 'mysqlbinlog-000001.bin','mysqlbinlog-000001.bin','mysqlbinlog-000001.bin' repeated over and over and the file sizes are identical.)		*Binlog names repeat (seeing 'mysqlbinlog-000001.bin','mysqlbinlog-000001.bin','mysqlbinlog-000001.bin' repeated over and over and the file sizes are identical)

	*First, make a backup of the client's entire ITrack database, in case something terrible happens.		*First, make a backup of the client's entire ITrack database, in case something terrible happens.

Jmckinstry: /* Bad Behavior */

2015-07-06T21:23:27Z

Bad Behavior

← Older revision		Revision as of 16:23, 6 July 2015
Line 109:		Line 109:
	* Files became corrupted after Replikwando2 got started		* Files became corrupted after Replikwando2 got started
	* Magical kernel-level call interception		* Magical kernel-level call interception
			* Firewall exceptions exist for one executable or the other

	* '''Resolution'''		* '''Resolution'''
	*Make sure the user account being used to run ReplikwandoService has access to all necessary files		* Make sure the user account being used to run ReplikwandoService has access to all necessary files
	* Turn off antivirus (or, even better, add Replikwandoservice to the whitelist for the AV)		* Turn off antivirus (or, even better, add Replikwandoservice to the whitelist for the AV)
			* Make sure there are entries in any running firewall program

	==== Replikwando2 successfully re-pushes, but then pushes tons of junk data ====		==== Replikwando2 successfully re-pushes, but then pushes tons of junk data ====
Line 166:		Line 168:
	*'''Resolution'''		*'''Resolution'''
	*Update <replikwando_install_folder>/bin/mysqlbinlog.exe with a newer version		*Update <replikwando_install_folder>/bin/mysqlbinlog.exe with a newer version

	~~==== Service and GUI versions do different things ====~~
	*'''Possible Cause'''
	*Service and GUI are running under different credentials or firewall/antivirus rules
	*Service and GUI are different versions

	*'''Resolution'''
	*Make sure versions are the same, then stop the service and run the GUI as Administrator.
	**If it works correctly, the issue is probably executable permissions
	**If it does not work as expected, the issue is probably a hardware/software firewall or local antivirus

Jmckinstry: /* Bad Behavior */

2015-07-06T21:21:40Z

Bad Behavior

← Older revision		Revision as of 16:21, 6 July 2015
Line 166:		Line 166:
	*'''Resolution'''		*'''Resolution'''
	*Update <replikwando_install_folder>/bin/mysqlbinlog.exe with a newer version		*Update <replikwando_install_folder>/bin/mysqlbinlog.exe with a newer version

			==== Service and GUI versions do different things ====
			*'''Possible Cause'''
			*Service and GUI are running under different credentials or firewall/antivirus rules
			*Service and GUI are different versions

			*'''Resolution'''
			*Make sure versions are the same, then stop the service and run the GUI as Administrator.
			**If it works correctly, the issue is probably executable permissions
			**If it does not work as expected, the issue is probably a hardware/software firewall or local antivirus

Jmckinstry: /* Replikwando runs and seems to work right, but dies during repushes */

2013-07-02T20:58:31Z

Replikwando runs and seems to work right, but dies during repushes

← Older revision		Revision as of 15:58, 2 July 2013
Line 162:		Line 162:
	*'''Possible Cause'''		*'''Possible Cause'''
	*MySQL Server version is higher than <replikwando_install_folder>/bin/mysqlbinlog.exe (ie: server is 5.6, mysqlbinlog.exe is 5.5)		*MySQL Server version is higher than <replikwando_install_folder>/bin/mysqlbinlog.exe (ie: server is 5.6, mysqlbinlog.exe is 5.5)
			**The ToConnection log will show that queries are getting mangled during the repush.

	*'''Resolution'''		*'''Resolution'''
	*Update <replikwando_install_folder>/bin/mysqlbinlog.exe with a newer version		*Update <replikwando_install_folder>/bin/mysqlbinlog.exe with a newer version

Jmckinstry: /* Bad Behavior */

2013-07-02T20:56:11Z

Bad Behavior

← Older revision		Revision as of 15:56, 2 July 2013
Line 158:		Line 158:
	**Do NOT kill an active mysqlbinlog.exe! Replikwando is actively receiving data from it, and things can go horribly wrong if you kill it!		**Do NOT kill an active mysqlbinlog.exe! Replikwando is actively receiving data from it, and things can go horribly wrong if you kill it!
	*A more permanent resolution is to use a different spawning method (we currently use ::CreateProcess). I believe (but may be wrong) that this issue occurs because ::CreateProcess returns COULDNT_CREATE_PROCESS or something like that, even though the process is made. It could also be an error in the handling of the closing of a windows-based thread, both of which should be investigated.		*A more permanent resolution is to use a different spawning method (we currently use ::CreateProcess). I believe (but may be wrong) that this issue occurs because ::CreateProcess returns COULDNT_CREATE_PROCESS or something like that, even though the process is made. It could also be an error in the handling of the closing of a windows-based thread, both of which should be investigated.

			==== Replikwando runs and seems to work right, but dies during repushes ====
			*'''Possible Cause'''
			*MySQL Server version is higher than <replikwando_install_folder>/bin/mysqlbinlog.exe (ie: server is 5.6, mysqlbinlog.exe is 5.5)

			*'''Resolution'''
			*Update <replikwando_install_folder>/bin/mysqlbinlog.exe with a newer version

Nenjin: /* Cannot find file: */

2013-02-26T17:46:54Z

Cannot find file:

← Older revision		Revision as of 12:46, 26 February 2013
Line 61:		Line 61:
	This message appears when Replikwando cannot locate the data file. Replication.ini is probably pointing to the wrong location.		This message appears when Replikwando cannot locate the data file. Replication.ini is probably pointing to the wrong location.

	*'''Resolution''''		*'''Resolution'''
	Open the company's SQLYOG and run this query:		Open the company's SQLYOG and run this query:
	<source lang = 'MySQL'>		<source lang = 'MySQL'>