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:
..\License Statistics\log\mysql.log ..\License Statistics\mysql_x86\data{color}hostname.err (for 32-bit database) ..\License Statistics\mysql_x64\data{color}hostname.err (for 64-bit database)
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.
Unable to write database error
When running License Statistics, you may see something similar to the following in the License Statistics log:[2007-08-20 15:47:09] Ready for querying...
[2007-08-20 15:47:09] Starting monitor of @btpssrv017!
[2007-09-13 23:02:00] FAIL: Unable to write database for vendor adskflex!
This error is usually caused by a 3rd party application, such as antivirus or backup software, locking the database files. In some cases, this problem can occur if all files and directories are not unzipped into the License Statistics directory.
Try the following steps to troubleshoot the problem, checking after each step to see whether the problem is resolved and proceeding to the next step if necessary:
- Check that all files and directories contained in the License Statistics zip file were extracted into the License Statistics directory. Some zip utilities may not unpack empty directories, so especially check that the directories XML, DB, LOG and HTML exist in your License Statistics directory.
- Temporarily disable any antivirus or backup software and check to see whether it resolves the problem.
- If the problem is not resolved, disable any other software that could potentially do file locking on the database files.
- If the problem still is not resolved, use a process monitor to observe any file locking that is occurring to identify what is locking the files.