Addressing Unsupported Characters within the MySQL Configuration File

There may come a situation where editing the MySQL Configuration file outside of editors such as nano, vim, or emacs may add additional unsupported characters. The issue may occur when you perform edits in non-conventional text editors such as a browser served text editor. For example, the MySQL Service may have attempted to start with the following error:

[Note] Server hostname (bind-address): '127.0.0.1<U+200B>'; port: 3306
[ERROR] Can't create IP socket: No such file or directory
[ERROR] Can't start server: cannot resolve hostname!
[ERROR] Aborting

If you find that a similar message occurs when you attempt to start the MySQL service, then we recommend the use of the command cat -A. Doing so will provide you with these characteristics:

~ cat -A /etc/my.cnf

[TRUNCATED OUTPUT]

bind-address=127.0.0.1M-bM-^@M-^K$

Viewing the files within vim or nano may also show you this problem character in a line similar to:

bind-address=127.0.0.1<200b>

To address the problem:

1. Navigate to the line of the configuration file. 

2. Remove the problem character. In the above example, remove "<200b>" from the configuration file.

3. Save your configuration file.

4. Attempt to start the service in question. In the above example, start the MySQL service using:

/scripts/restartsrv_mysql --start