Repository navigation
Gateway - Condor logs an wallet error when Gateway is unavailable on another server #215
Description
Area
Condor logs
What happened
This was noticed while using Condor with multiple Hummingbot API servers. Gateway was available on one server but was not running on another. When Condor requested the other server’s Gateway wallets, Hummingbot API correctly returned 503 Gateway service is not available, but Condor logged the expected condition as an error with a full traceback.
2026-08-20 15:15:11,794 - condor.web.routes.bots - INFO - Server 'local': found 0 bot(s)
2026-08-20 15:15:11,796 - condor.fetchers.market_data - INFO - Fetching historical candles: connector=hyperliquid_perpetual pair=HYPE-USD interval=5m start=1786950900 end=1787210111
2026-08-20 15:15:11,847 - condor.web.routes.settings - ERROR - Failed to list gateway wallets from 'ghostring (ovh)'
Traceback (most recent call last):
File "/home/eddga/hummingbot/condor/214/condor/web/routes/settings.py", line 431, in gateway_wallets
wallets = await client.accounts.list_gateway_wallets()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/eddga/hummingbot/condor/214/.venv/lib/python3.13/site-packages/hummingbot_api_client/routers/accounts.py", line 82, in list_gateway_wallets
return await self._get("/accounts/gateway/wallets")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/eddga/hummingbot/condor/214/.venv/lib/python3.13/site-packages/hummingbot_api_client/routers/base.py", line 33, in _get
raise aiohttp.ClientResponseError(
...<5 lines>...
)
aiohttp.client_exceptions.ClientResponseError: 503, message='Gateway service is not available', url='http://hehe-its-a-secret:8000/accounts/gateway/wallets'
The WebUI already treats this situation as “no wallets” or a muted Gateway-unavailable state. A server without
Gateway should be shown as unavailable without producing an error-level traceback during normal multi-server use.
Steps to reproduce
- Configure two accessible Hummingbot API servers in Condor.
- Start Gateway on server A and leave Gateway unavailable on server B.
- Select server B then check the condor logs.
- Or change the API server at the top then observe condor logs
- Observe an error and traceback for
GET /accounts/gateway/walletsreturning503 Gateway service is not available.
Environment
n/a
Logs
n/a
Activity