Embedded MySQL server troubleshooting
During the License Statistics evaluation, you may have License Statistics temporarily running on a machine that does not meet the minimum system requirements. In such cases where there is not enough memory on the machine hosting the License Statistics installation, the MySQL server may not start properly the first time you start License Statistics, which will produce warnings similar to the following in the xflicstat.log file:
[2012-12-12 08:00:01] WARNING: Waiting for mysqld process to start which takes more time than usual...
You can check whether insufficient memory is the problem by looking at the MySQL server log file, which can be found in one of the following directories:
- mysql.log in License Statistics log folder
- mysql_error.log and/or hostname.err under data folder in mysql_x86 directory (or mysql_x64 or mysql for License Statistics v4.19.1 and newer).
where hostname is the hostname of the machine where License Statistics is installed.
If you see messages similar to the following in the MySQL server log, there is an issue with the host memory:
120503 15:27:16 InnoDB: Initializing buffer pool, size = 1.5G InnoDB: VirtualAlloc(1631846400 bytes) failed; Windows error 8
To resolve this issue, you can try lowering the memory requirement in the config.ini file by changing the innodb_buffer_pool_size setting to the desired value; for example, to 1024M or as low as 512M, depending on available resources.
This setting may be changed only for testing purposes (for example, during evaluation). The proper solution is to install License Statistics on a machine that meets system requirements. Note that lowering the innodb_buffer_pool_size setting may decrease the performance of License Statistics, causing it to run slower.
Lost connection to MySQL server during query
When using License Statistics with an external MySQL database, you may see the following error message:
Lost connection to MySQL server during query.
The above message indicates that your MySQL server settings should be adjusted. To resolve this issue, follow the configuration instructions described in Using an external MySQL database. You can also find more information about this problem in the MySQL reference manual.
"Specified key was too long; max key length is 767 bytes" error
When using License Statistics, you may see the following error message in the License Statistics log file:
Specified key was too long; max key length is 767 bytes.
This problem may be related to the fact that the MySQL database by default uses the UTF-8 character set and collation.
To resolve this issue, you should upgrade License Statistics that uses an embedded MySQL database to License Statistics using an external MySQL database. If this does not resolve the problem, you can try upgrading License Statistics from an external to embedded database.