Python 3: ImportError “No Module named Setuptools”

If you receive this error please try the following command:

  sudo apt-get install python3-setuptools

For other versions like python2 run the following command:

  sudo apt-get install python-setuptools

module_stderr": "sudo: a password is required

 This error appears when we try to run an ansible script with a user that is not enabled for passwordless sudo. 

On this error we have two options with us:

1. Make the user run sudo without a password, for which open /etc/sudoers and put the following line for the user for which passwordless ssh is needed"

Then 

shashwat          ALL=(ALL:ALL) NOPASSWD: ALL

#Note: Add this line to the end of the file

Save and Exit and run the ansible script again.

2. option is to enable ansible to ask sudo password on command line. For which you need to pass parameter

--ask-become-pass or -K 

And this will ask for password on command line and ansible will run sucessfully.

Host is in bad health Cloudera Manager after reinstalling. ERROR Error, CM server guid updated, expected

It happened to me when i tried to clean up and reinstall the Cloudera-manager tot error in web UI "Host is in bad health Cloudera Manager", i checked the log where is found following error:

ERROR    Error, CM server guid updated, expected e0c62792-a6a4-4070-b725-3ec1c7265e8e, received 03dfe52e-5beb-4794-8178-f5107739a3d6

This happened due to some leftover files which confuses cloudera agent and CM for this we need to do following

delete this file on all the nodes where ever you have the agent running(It will show in the error message that agent failed on following hosts) and restart the agent service

/var/lib/cloudera-scm-agent/cm_guid

and try there may be some other reason, so i request you to look into log of agent, server whenever you get error during installation you will surely get the pointer of the probable reason behind the error.

MySQL Error: Error_code: 1032

Here's something about MySQL replication error. The exact error could be as below:

Could not execute Update_rows event on table DBName.tableName; Can't find record in 'tableName', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.01, end_log_pos 218

If SQL Thread on one of your slave stops with this error code, that just mean Master and this Slave are not in sync!! There must be an inconsistency. 

In our case, slave got an Update event form master, but that particular record was not available in the slave. (Of course, that was deleted on Master n Slave separately)
You would get this error only if the binlog_format is set to ROW_BASED or MIXED mode.

So, now check that particular binlog at that position where replication stopped with this error. 
When you convert the binlog with mysqlbinlog command, you may see some junk characters  where you were expecting some DMLs which caused the error(In our case its an Update statement).

So you can use below command to translate binlog completely:


mysqlbinlog --base64-output=DECODE-ROWS --verbose  mysql-bin.01 >mysql-bin.01.txt