Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have problem ETIMEDOUT #149

Open
generator2003 opened this issue Apr 18, 2021 · 8 comments
Open

Have problem ETIMEDOUT #149

generator2003 opened this issue Apr 18, 2021 · 8 comments

Comments

@generator2003
Copy link

Hello i Have problem ETIMEDOUT
How i can solve this ?

`
oleg@SKY-NOTE:~/projects/trb/binance-triangle-arbitrage$ npm start

binance-triangle-arbitrage@6.2.0 start /home/oleg/projects/trb/binance-triangle-arbitrage
node src/main/Main.js

Checking configuration ...
Checking latency ...
Experiencing 505 ms of latency
Fetching exchange info ...
Found 1038/1405 currently trading tickers
Found 174 triangular trades
Checking market conditions ...
Opening 321 depth websockets for 321 tickers ...
Error: ETIMEDOUT
at Timeout. (/home/oleg/projects/trb/binance-triangle-arbitrage/node_modules/request/request.js:848:19)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7) {
code: 'ETIMEDOUT',
connect: true
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! binance-triangle-arbitrage@6.2.0 start: node src/main/Main.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the binance-triangle-arbitrage@6.2.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/oleg/.npm/_logs/2021-04-18T23_14_13_424Z-debug.log
`

@generator2003
Copy link
Author

generator2003 commented Apr 18, 2021

I use any values:
"WEBSOCKET": { "BUNDLE_SIZE": 10, "INITIALIZATION_INTERVAL": 10000 },

But i have this error.
How i can debug this ?
UPD I can run this i use "WHITELIST": ["BTC", "BNB", "ETH"]

My config

{
    "KEYS": {
        "API": "*",
        "SECRET": "*"
    },

    "INVESTMENT": {
        "BTC": {
            "MIN": 0.010,
            "MAX": 0.015,
            "STEP": 0.005
        }
    },

    "SCANNING": {
        "DEPTH": 50,
        "WHITELIST": []
    },

    "EXECUTION": {
        "ENABLED": false,
        "CAP": 1,
        "STRATEGY": "linear",
        "TEMPLATE": ["BUY", "SELL", "SELL"],
        "FEE": 0.075,
        "THRESHOLD": {
            "PROFIT": 0.00,
            "AGE": 25
        }
    },

    "HUD": {
        "ENABLED": true,
        "ROWS": 10,
        "REFRESH_RATE": 500
    },

    "LOG": {
        "LEVEL": "debug",
        "PRETTY_PRINT": true,
        "STATUS_UPDATE_INTERVAL": 2
    },

    "WEBSOCKET": {
        "BUNDLE_SIZE": 10,
        "INITIALIZATION_INTERVAL": 10000
    },

    "BINANCE_OPTIONS": {
        "useServerTime": true
    }

}

`

@ScuzzyHoulihan
Copy link

I'm having the same issue anyone have any luck resolving this?

@ScuzzyHoulihan
Copy link

I'm having the same issue anyone have any luck resolving this?

I was able to resolve my issue it was a firewall issue, was running on a VM and also had to increase my resources.

@mpaya5
Copy link

mpaya5 commented May 31, 2021

@ScuzzyHoulihan How did you solve it?

@Jagermeister56
Copy link

Not a problem when using BTC as the main coin.
Error when using USDT as the main coin.
This happens even with the firewall disabled.

@mpaya5
Copy link

mpaya5 commented Jun 15, 2021 via email

@imraanparker
Copy link

@yumewebs, can you share your config for USDT and the improvements you made to the bot?

@Quilist
Copy link

Quilist commented Jan 20, 2023

At the end I could solve it and I improved the bot, the code and the speed. Even the algorithm is better and is showing me positive opportunities each minute. The only problem (not related with the bot at all) is the glide of the market and sometimes the bot needs to take more than hour to do the three orders.

How?? Share your config pls

Repository owner deleted a comment from mkproject-admin Feb 21, 2024
Repository owner deleted a comment from amd119 Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants