Troubleshooting

Troubleshooting

Error: SQLITE_BUSY: database is locked

The reason is to save and read data from the database at the same time. The construction of SQLite does not allow other connections during the writing to DB. To prevent this, use two different DB files, one for import (write), the other for Backtest (read). Note: enabled candleWriter in paperTrader or trader mode also saves data in the database and error can occurs. The database used for instance can be defined in the Gekko or BacktestTool configuration file by changing the dataDirectory or version value in config.sqlite.

Example: 
config.sqlite = {
  path: 'plugins/sqlite',
  dataDirectory: 'DUPA',
  version: 6.9,
  dependencies: []
}

For Binance exchange instance will use database file: gekko/DUPA/binance_6.9.db

Error: TULIP indicators could not be loaded

This error comes from gekko. You haven't installed optional modules. To install use command: npm install tulind talib. If you do not want to install these modules you can get rid of this error commenting on the following two lines in file: gekko/plugins/tradingAdvisor/baseTradingMethod.js

1. log.warn('TALIB indicators could not be loaded, they will be unavailable.');
2. log.warn('TULIP indicators could not be loaded, they will be unavailable.');

Error: Failed to load indicator STC

This error comes from the gekko. It means that the STC indicator can not be loaded due to an error in indicator source code. You can try to fix the indicator code in the file gekko/strategies/indicators/STC.js or remove it from this folder, and the error will not appear.

Different backtests results than in Gekko UI

The settings for fee, slippage, currency and asset amount have different values than those you use in the UI. You can change them in the file backtest-config.pl or gekko/config/plugins/paperTrader.toml.