Troubleshooting

Online section / Guides / User Guide / Appendix / Troubleshooting contact | download | sitemap
 

This section describes some hints to solve common problems which may occur during deployment of the MyARM agent.

Tracing initialisation and configuration

It is possible to enable a tracing mechanism which helps you to identify the deployment problem you might have. This can be enables using the MYARM_TRACE environment variable. For detailed description of the options you can enable (See Appendix Environment) .

MyARM manager does not work with SQLite database

SQLite database is a file based SQL database engine which sometimes has problems of concurrent access especially under Windows. If you encounter the problem that the MyARM manager seems to working have a look into the log files. There might be error messages about locking problems. Make sure that no instrumented application is running while you want to analyse measurement data.

Some transactions are missing

MyARM uses an internal queue to decouple the measurement of transactions and the writing to the data sink (database). The queue is limited to a configured number of queue entries. If more measurement data per time unit is generated than it can be written to the data sink the queue gets more and more filled up to its limits. If the limits of the queue are reached the measured data are dropped and the log message with is emitted to notify about the lost data.

The queue size (agent.armdata.buffer.number) and the size of each queue entry (basic.armdata.buffer.size) can be configured (See Configuring Agent) .

MySQL database creation failed

To minimise the efforts to setup all necessary databases and tables for the MyARM agent to use a MySQL server to store ARM data the program myarminitdb is provided. If the MySQL server is not setup correctly it is possible that the myarminitdb fails to create the needed databases and tables. Be sure that you have the right permissions for creating databases and tables.

someuser@localhost: mysql -u root
GRANT ALL PRIVILEGES ON *.* TO 'someuser'@'localhost';

Note you need root privileges to change privileges of databases.