Gateway - Error when running multiple bots

[Steapanisk]

Describe the bug

I launch 3-4 arbitrage bots with one or more gateways. And I immediately get an error

2025-03-06 22:48:00 | error | Failed to get Jupiter quote: {"message":"Response returned an error code","stack":"ResponseError: Response returned an error code\n at DefaultApi.<anonymous> (/home/st/1bot/gateway/node_modules/.pnpm/@[email protected]/node_modules/@jup-ag/api/dist/index.js:296:13)\n at Gener ator.next (<anonymous>)\n at fulfilled (/home/st/1bot/gateway/node_modules/.pnpm/@[email protected]/node_modules/@jup-ag/api/dist/index.js:40:24)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"} 2025-03-06 22:48:00 | error | Error in price function: {"message":"NO_ROUTE_FOUND: SAND-USDC","stack":"Error: NO_ROUTE_FOUND: SAND-USDC\n at getTradeInfo (/home/st/1bot/gateway/dist/src/connectors/jupiter/jupiter.controllers.js:37:19)\n at process.processTicksAndRejections (node:internal/process/task_queu es:95:5)\n at async price (/home/st/1bot/gateway/dist/src/connectors/jupiter/jupiter.controllers.js:67:24)\n at async Object.<anonymous> (/home/st/1bot/gateway/dist/src/connectors/jupiter/jupiter.routes.js:23:16)"}

Steps to reproduce

1. gateway enable
2. turn on 3-4 hummingbots. strategies start --script v2_with_controllers.py --conf conf_v2_with_controllers_1.yml start --script v2_with_controllers.py --conf conf_v2_with_controllers_2.yml start --script v2_with_controllers.py --conf conf_v2_with_controllers_3.yml start --script v2_with_controllers.py --conf conf_v2_with_controllers_4.yml
3. errors appear in the gateway console

Release version

2.4.0

Type of installation

Source

Attach required files

[rapcmia]

hi @Steapanisk i tried to run 3 bots from source build with same setup all running on jupiter_solana_mainnet-beta but not able to reproduce this error.

• I assume you updated your setup to the latest version from 2.3, had you tried to do a fresh install?
• Can you let me know what installation (source / docker) did you use?

Here's my gateway log file (please excuse the 429 errors due to free tier node) logs_gateway_app.log.2025-03-07.log

[Steapanisk]

@rapcmia I use quicknode.com connector. Tried to change to syndica.io. Same result. Clean new installation. master branch. The problem is reproducible for me both in source and in docker. Tried to increase tick_size to 30 seconds, didn't help. If there are two controllers, it works without problems.

Coins that i use DOGEGOV https://dexscreener.com/solana/7estvpaxjgbfgtzghtmkefjxqyjnskfytakk23cznrlf SUI https://dexscreener.com/solana/4wqtdsexvjda6m6udjnerxjn67dsap7fdotdnhvynsts UNI https://dexscreener.com/solana/8j5fa8wbgadsv8aupgtqdh9hm5azusf2ijvskkoacxci SAND https://dexscreener.com/solana/3cmppx8kkzera2umtlcdxmfjma82eltamasyvmdanlxi

the controllers look like this: id: AwyCbvNNQsx8V85QvU1z2Ta94nJqRcTbHdWcJAFcyD1g controller_name: arbitrage_controller controller_type: generic total_amount_quote: 10 manual_kill_switch: null candles_config: [] exchange_pair_1: connector_name: gate_io trading_pair: DOGEGOV-USDT exchange_pair_2: connector_name: jupiter_solana_mainnet-beta trading_pair: DOGEGOV-USDC min_profitability: 0.01 delay_between_executors: 10 max_executors_imbalance: 2 rate_connector: binance quote_conversion_asset: USDT

logs_gateway_app.log.2025-03-07.log

[Steapanisk]

@rapcmia localized the problem. Launched the bot on two computers at the same time and got the same problem. Tried changing nodeURL providers - did not help. From which I concluded that I was blocked by the wallet. Created a second wallet and the problem went away. That is, I can not connect more than 2 bots to one Solana wallet.

[Steapanisk]

oh no. The problem still remains. I don't even know what to try.

[fengtality]

From the error logs, this is because Jupiter can't find the SAND-USDC route. In new version of Gateway, you can use gateway token to add a token, and then you can check that Jupiter has the route with gateway swap