Hi -Rana-, I don't think your attachments made it through. That's just as well: there are limits to how much we can help you to that extent over a community forum anyway. We can offer general guidance and feedback on highly specific issues, but general troubleshooting is best performed by our support organization, so they can work with you over time and as new issues crop up. Otherwise, in general, I would check that the Director instance is able to consistently reach the CM instance over the network, specifically over SSH. Check over any network / firewall rules that may interrupt the connectivity, especially if the instances are in separate networks or subnetworks.
... View more
You appear to be using the username "scm" as an administrative user on the MySQL instance. The "scm" user must have permission to create and delete databases on the server. Normally, one would use the default MySQL "root" user, which already should have all of the necessary permissions. - The string starting with "scm_" and ending with a random string is the generated name of the Cloudera Manager server database. - The string "uxnlmrno" is the username for the user that shall be used to access the new database. Apparently, in your configuration file, you do not specify a usernamePrefix for the database. It is optional. Director is running a script on the CM instance to perform the database work. (The script uses CM code, so it needs to run where CM is installed). It is trying to reach the database server at the full hostname ending in ".internal", and it seems that the connectivity there is working. You can double-check by running a MySQL client from the CM instance itself. You say you can create and drop databases from the MySQL console. Does that use the "scm" user or, perhaps, the "root" user?
... View more