Messages

1

Beginners & Help / Re: [TUT] How to running GUNBOT in Linux

« on: December 03, 2017, 01:19:53 PM »

Hi,
I have managed to run on nodejs
but i have nothing else on logs :

jerome@cresus:~/GUNBOT$ pm2 logs BTC_LSK
[TAILING] Tailing last 15 lines for [BTC_LSK] process (change the value with --lines option)
/home/jerome/.pm2/logs/BTC-LSK-error-2.log last 15 lines:
/home/jerome/.pm2/logs/BTC-LSK-out-2.log last 15 lines:
2|BTC_LSK  | Loading config...
2|BTC_LSK  | Loading exchange bittrex
2|BTC_LSK  | Loading config...
2|BTC_LSK  | Loading exchange bittrex
2|BTC_LSK  | Loading config...
2|BTC_LSK  | Loading exchange bittrex
2|BTC_LSK  | Loading config...
2|BTC_LSK  | Loading exchange bittrex



I was not sure gunbot was doing anything, now i'm confident gunbot is doing nothing !

Check your config files for any formatting errors (spaces, missing commas etc.-anything that is not in line with standard config file formatting)7

2

Technical Support & Development / Re: Gunbot buys like a charm but fails to ever sell anything

« on: November 26, 2017, 04:13:52 PM »

Thanks for the answer, I'm trying your settings as we speak to compare.

were you able to get the bot selling? I am having the same issues.

No, I reverted to v3.3.2 until Gunbot XT is made stable.

3

Technical Support & Development / Re: Gunbot buys like a charm but fails to ever sell anything

« on: November 18, 2017, 01:27:36 PM »

Thanks for the answer, I'm trying your settings as we speak to compare.

4

Beginners & Help / Re: Gunbot XT pairs cycling

« on: November 18, 2017, 01:11:54 PM »

ELECTRICTY WENT OUT AS WROTE AN ANSWER YESTERDAY. I was mad and din't write one back gain.
thing is, bot delay and interval ticker update are not directly related. bot delay is randomly timed, interval ticker update not, it has a fixed time. how I immagine this works is, bot delay triggers pair processing each new random*bot delay, which takes the data for processing from an array (period storage ticker), which has new data added every interval ticker update (25 seconds if set stock). I don't even think both bot delay and interval ticker update need to be sinchronized, because mainly we are looking at candles with a much larger period than both of them take to perform their task.

That's what I assumed after trying to find an answer. Basically, two separate processes, interval_ticker_update retrieves and stores the prices in its ticker history every n seconds, while Gunbot is constantly cycling pairs and comparing entry/exit strategies with the prices contained in ticker history. Thanks for your thoughts.

5

Technical Support & Development / Re: Gunbot buys like a charm but fails to ever sell anything

« on: November 17, 2017, 07:14:39 PM »

I have the same problem on BBStepgain, buys in a great spot, but never sells, even if the coin falls below bought value.

Still don't know what causes it.

6

Beginners & Help / Re: Gunbot XT pairs cycling

« on: November 17, 2017, 12:01:25 PM »

You know, those albatros have difficulties to fly ;-)
https://youtu.be/mN3zz6PcC0w?t=13

Flying is overrated, all the fish are in the sea anyway.

7

Beginners & Help / Re: Gunbot XT pairs cycling

« on: November 17, 2017, 12:01:01 PM »

You should really read the wiki. No, really, people have worked to make it available, it's rude to just ignore it.

BOT_DELAY 1 Values: numerical – represents a multiplier value used in the formula to delay the bot. Bot will delay processing a new pair for a random amount of milliseconds. Useful for when Poloniex complains about sending to many requests. Formula: random value between 200 an 400 ms * BOT_DELAY

interval_ticker_update 25000 Values: numerical – represents time in milliseconds. This parameter defines after how many milliseconds new prices are being pulled from the exchange for each pair (default value of 25000 = 25 seconds). Set this to a lower value if you want Gunbot to retrieve prices faster, for example while you’re interested in following shorter trends.This value is related to "period_storage_ticker”, since it defines how often new prices are being added to the array

Thanks for the answer.

I did read the wiki, a dozen times at least and it seems to me that the difference between BOT_DELAY and interval_ticker_update is explained in a way that is obvious only to someone who already understands the mechanics behind the communication between the bot and the exchange.

Don't get me wrong, I am a person who likes learning new stuff and I try to solve the problems I encounter by myself, whenever I can.  Now, for someone looking for increasing the time interval in which the bot communicates with the exchange, increasing interval_ticker_update seems like a completely reasonable solution.

After starting the bot, reading the output and noticing that the delay between retrieving the price from the exchange is 7 seconds, and not 25 seconds as is set in interval_ticker_update, I tried to fiddle with the value of interval_ticker_update, which did not yield any results.

So my problem here was that I was not able to understand the difference between Gunbot "processing a new pair" and Gunbot "pulling the prices from the exchange for each pair" solely from the explanations given in the Gunbot wiki.

I have to admit I still do not understand the difference.

E.g. I have two pairs running on Gunbot, and Gunbot pulls the price from the exchange for pair A, processes the pair and concludes there are no opportunities to trade. Seven seconds have passed and Gunbot moves on to pair B, pulls the price from the exchange, processes it and concludes there are no opportunities to trade. The cycle begins anew, Gunbot pulls the price from the exchange for pair A etc. (I am not sure if this is how the bot functions, just my assumption)

In total, cca 14 seconds have passed for the processing of two pairs, and the pair A is processed again after 21 seconds. How would the interval_ticker_update with a value of 25 seconds fit in this example? (I am aware the value can be changed, I just wish to understand how the bot works so I can control it more efficiently)

I bought Gunbot and I think it's an excellent tool if you understand how to use it, but I also have the feeling that the wiki is written by the programmers for the programmers (although the documentation is definitely better than for the previous versions). That is not a big problem as I'm sure there are people in the community who would take their time to help and write the wiki and make it more accessible to non-programmers, myself included. So if any admins/moderators are reading this, I'll gladly help in any way I can in making this project and its wiki be even better than it is now.

8

Beginners & Help / Gunbot XT pairs cycling

« on: November 15, 2017, 01:59:40 PM »

Hello,

I've just transitioned from Gunbot v3.3.2 to Gunbot v6.0.1

If I'm correct, Gunbot XT is cycling through my pairs every 5-6 seconds between each pair on Bittrex.

I'll add more instances of Gunbot XT on the same machine, which means more pairs.

Is it possible to control the cycling time between the pairs (as I wouldn't want to get banned)?

Does the interval_ticker_update control that? I've set it to 120000, but it still cycles through the pairs every 5-6 seconds.

9

Beginners & Help / Re: Gunbot v 3.3.2 not using the proper strategy

« on: November 07, 2017, 03:49:00 PM »

Also, it seems that Gunbot is ignoring my attempts to change the config files. A lot of the times it does not register the hot reconfig, and even when it does, it still does not change the settings e.g. it still continues to use STEPGAIN strategy for buying instead of BB strategy.

Need help please.

10

Beginners & Help / Re: Free TradingView Scripts for Tuning Strategies in Gunbot / GunbotXT

« on: November 07, 2017, 02:22:03 PM »

Thank you!

11

Beginners & Help / Gunbot v 3.3.2 not using the proper strategy

« on: November 07, 2017, 02:01:14 PM »

Hello,

I'm using Gunbot v 3.3.2 on Linux Debian.

I have noticed that if I input BB for the BUY_STRATEGY variable, I still get the following output in my logs:

###[ --2017/11/07 14:55:10--Bittrex--BTC_NAV  --  Gunbot v3.3 cycle #4607 --------------- ]
::::: collecting market data...
***************************************************
Low BB:0.00010759 - High BB:0.00011315
***************************************************
BB price to buy 0.00010898239880547414 -- GAIN price to buy 0.00010705990880000002
++++
LP 0.00010804  Bal.BTC 0.01763395  Bal.NAV 0(0)
No open orders
boughtPrice 0.000105
price  falls (-4)
PriceToBuy 1.0706 priceToSell 1.0710
LP 1.0804000 > prBuy 1.0705991  secMargin -0.0000010500000000000001  grows no
no altcoins: 0
price to buy: 0.00010705990880000002
last price is too high
Gunbot callback at 2017/11/07 14:55:13 cycle # 4607
Callback:
---------
price too high
need faster: no
need slower: no

next delay will be 120s


Notice that the "BB price to buy" is 0.00010898239880547414, while "GAIN price to buy" is 0.00010705990880000002.

A few lines after that, Gunbot says that "PriceToBuy" is 1.0706 meaning that it is specifically targeting GAIN price to buy, and not BB price to buy, even though I've selected BB as the buy strategy.

The bot has been working for 3 days prior to this log output.

Am I wrong in my interpretation or is this some kind of error? How can I fix it?

Thanks

12

Technical Support & Development / Gunbot v 3.3.2 error

« on: November 07, 2017, 01:49:53 PM »

Hello, I'm using Gunbot v 3.3.2 on Linux Debian. When i check the error logs i get this error, or series of errors:

Unhandled rejection StatusCodeError: 503 - "The service is unavailable."
    at new StatusCodeError (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/errors.js:32:15)
    at Request.plumbing.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:104:33)
    at Request.RP$callback [as _callback] (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at Request.self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:192:7)
    at Request.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)
    at IncomingMessage.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1091:12)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:186:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
(node:24264) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:17676) DeprecationWarning: Calling an asynchronous function without callback is deprecated.


Does anyone have any idea as to what this means?

13

Beginners & Help / Re: Gunbot 3.3.2 + PM2 help needed

« on: October 15, 2017, 10:13:25 PM »

2) Is it possible to add a process to .yaml file and to start it but without stopping already running processes and how is it done?

Thanks!

Found the answer here-

 http://pm2.keymetrics.io/docs/usage/application-declaration/

14

Beginners & Help / Re: Gunbot 3.3.2 + PM2 help needed

« on: October 15, 2017, 09:56:16 PM »

1) How to add process ID column to the table shown after

PM2 list

command is used?

Found the solution: the process is there but the terminal window was too narrow so I just maximized it and ran

pm2 list

command again.

15

Beginners & Help / Gunbot 3.3.2 + PM2 help needed

« on: October 15, 2017, 02:30:31 PM »

Hello,

I have two questions regarding PM2:

1) How to add process ID column to the table shown after

PM2 list

command is used?

2) Is it possible to add a process to .yaml file and to start it but without stopping already running processes and how is it done?

Thanks!

16

Beginners & Help / Re: [TUT] How to running GUNBOT in Linux

« on: October 15, 2017, 02:27:13 PM »

Yes, you should be able just to run. I did reinstall the system and there of course I had to start all over again. But with an upgrade, you should be able to continue normally.
However, I cannot figure out a way to keep the bot running after the terminal is closed. I googled and found "nohoop" command and "disown" but they still didn't help. Maybe because I run the boot as root? Any idea?

Isn't that the purpose of PM2? To keep the bot running in the background at all times?

17

Beginners & Help / Re: Gunbot log explanation

« on: October 15, 2017, 11:50:36 AM »

No, sincerely, but this seem to be a time-out?
If gunbot works fine, I wouldn't worry too much...

Gunbot works just fine, got some profit last night.

I won't worry about that then. Thanks!

18

Beginners & Help / Re: Gunbot log explanation

« on: October 14, 2017, 05:37:41 PM »

Thanks.

Ok, so I went to .pm2 folder and copy pasted the contents of BTC-XEL-error-1.log. These are the contents:

(node:13497) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:13620) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:13733) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
Unhandled rejection RequestError: Error: ESOCKETTIMEDOUT
    at new RequestError (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)
    at ClientRequest.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:822:16)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:86:13)
    at ClientRequest.emit (events.js:186:7)
    at TLSSocket.emitTimeout (_http_client.js:679:10)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:86:13)
    at TLSSocket.emit (events.js:186:7)
    at TLSSocket.Socket._onTimeout (net.js:342:
    at ontimeout (timers.js:365:14)
    at tryOnTimeout (timers.js:237:5)
    at Timer.listOnTimeout (timers.js:207:5)
Unhandled rejection RequestError: Error: ESOCKETTIMEDOUT
    at new RequestError (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)
    at ClientRequest.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:822:16)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:86:13)
    at ClientRequest.emit (events.js:186:7)
    at TLSSocket.emitTimeout (_http_client.js:679:10)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:86:13)
    at TLSSocket.emit (events.js:186:7)
    at TLSSocket.Socket._onTimeout (net.js:342:
    at ontimeout (timers.js:365:14)
    at tryOnTimeout (timers.js:237:5)
    at Timer.listOnTimeout (timers.js:207:5)
Unhandled rejection RequestError: Error: ESOCKETTIMEDOUT
    at new RequestError (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)
    at ClientRequest.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:822:16)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:86:13)
    at ClientRequest.emit (events.js:186:7)
    at TLSSocket.emitTimeout (_http_client.js:679:10)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:86:13)
    at TLSSocket.emit (events.js:186:7)
    at TLSSocket.Socket._onTimeout (net.js:342:
    at ontimeout (timers.js:365:14)
    at tryOnTimeout (timers.js:237:5)
    at Timer.listOnTimeout (timers.js:207:5)
Unhandled rejection RequestError: Error: ESOCKETTIMEDOUT
    at new RequestError (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)
    at ClientRequest.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:822:16)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:86:13)
    at ClientRequest.emit (events.js:186:7)
    at TLSSocket.emitTimeout (_http_client.js:679:10)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:86:13)
    at TLSSocket.emit (events.js:186:7)
    at TLSSocket.Socket._onTimeout (net.js:342:
    at ontimeout (timers.js:365:14)
    at tryOnTimeout (timers.js:237:5)
    at Timer.listOnTimeout (timers.js:207:5)
(node:20308) DeprecationWarning: Calling an asynchronous function without callback is deprecated.

Should I copy/paste some other logs?

Thanks for the help!

19

Beginners & Help / Gunbot log explanation

« on: October 13, 2017, 07:35:37 PM »

Hello,

I'm using Gunbot 3.3.2 with PM2 and as much as I can tell, Gunbot is working fine.

However, when I issue the command to check Gunbot logs, I receive the following output:

1|BTC_XEL  |     at self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
1|BTC_XEL  |     at emitOne (events.js:96:13)
1|BTC_XEL  |     at Request.emit (events.js:189:7)
1|BTC_XEL  |     at ClientRequest.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:822:16)
1|BTC_XEL  |     at Object.onceWrapper (events.js:291:19)
1|BTC_XEL  |     at emitNone (events.js:86:13)
1|BTC_XEL  |     at ClientRequest.emit (events.js:186:7)
1|BTC_XEL  |     at TLSSocket.emitTimeout (_http_client.js:679:10)
1|BTC_XEL  |     at Object.onceWrapper (events.js:291:19)
1|BTC_XEL  |     at emitNone (events.js:86:13)
1|BTC_XEL  |     at TLSSocket.emit (events.js:186:7)
1|BTC_XEL  |     at TLSSocket.Socket._onTimeout (net.js:342:
1|BTC_XEL  |     at ontimeout (timers.js:365:14)
1|BTC_XEL  |     at tryOnTimeout (timers.js:237:5)
1|BTC_XEL  |     at Timer.listOnTimeout (timers.js:207:5)

1|BTC_XEL  | PriceToBuy 0.5574 priceToSell 0.5714
1|BTC_XEL  | LP 0.5714000 > prBuy 0.5574006  secMargin -5.841259999999996e-7  grows no
1|BTC_XEL  | no altcoins: null
1|BTC_XEL  | price to buy: 0.000055740064
1|BTC_XEL  | last price is too high
1|BTC_XEL  | Gunbot callback at 2017/10/13 20:27:52 cycle # 1100
1|BTC_XEL  | Callback:
1|BTC_XEL  | ---------
1|BTC_XEL  | price too high
1|BTC_XEL  | need faster: yes
1|BTC_XEL  | need slower: no
1|BTC_XEL  |
1|BTC_XEL  | next delay will be 60s
1|BTC_XEL  |
1|BTC_XEL  |

I panicked a bit when I saw "/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/".

Can anyone explain lines 1 and 4 with regards to user Enrico and xBot?

Thank you!

20

Beginners & Help / Re: Error starting Gunbot 3.3.2. in Linux Mint 18.2

« on: September 21, 2017, 05:49:22 PM »

Hello,

trying to set-up Gunbot 3.3.2 in Linux Mint 18.2 but when i run this command in the terminal:

./gunthy-linuxx64 BTC_XRP

I get this output:

Bot crashed at 2017/09/21 15:47:52
Reason: Failed to load config!!!
Parameter: undefined-BTC_XRP-config.js
Original error: { Error: Cannot find module '/home/albatros/Programi/gunbot/undefined-BTC_XRP-config.js'
    at Module._resolveFilename (module.js:470:15)
    at Function.Module._resolveFilename (evalmachine.<anonymous>:0:0)
    at Function.Module._load (module.js:418:25)
    at Module.require (module.js:498:17)
    at Module.require (evalmachine.<anonymous>:0:0)
    at require (internal/module.js:20:19)
    at loadConfig (evalmachine.<anonymous>:0:0)
    at new Bot (evalmachine.<anonymous>:0:0)
    at Object.console./snapshot/Users/Enrico/Desktop/xBot_v2.9.3/index.js.dev (evalmachine.<anonymous>:0:0)
    at Module._compile (evalmachine.<anonymous>:0:0)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (evalmachine.<anonymous>:0:0)
    at run (bootstrap_node.js:426:7)
    at startup (bootstrap_node.js:147:9)
    at bootstrap_node.js:541:3 code: 'MODULE_NOT_FOUND' }

Any help would be appreciated!

Ok, I managed to get it working. I am new to Linux so any advice and/or corrections are appreciated.

The problem was that the 3.3.2 version has different naming conventions (I think). First I renamed the .config file for my BTC_XRP pair to 'BTC_XRP-config.js' so I presume that was part of the problem. Second, I was trying to run Gunbot with the following command: gunthy-linuxx64 BTC_XRP and I presume that was the second part of the problem.

So, I did the following:

1. I renamed the .config file to: 'bittrex-BTC_XRP-config.js' and edited it appropriately (entered my API key, set the trading strategy etc.)

2. The executable for my OS (Linux Mint 18.2 64-bit) is named 'gunthy-linuxx64'. So, to run it from the Linux terminal, I had to type './gunthy-linuxx64 BTC_XRP bittrex
'. I found this part of the answer in one of the tutorials on how to run Gunbot on Linux. Sorry, can't seem to find the post anymore.

So that's what started my Gunbot and got it working from the terminal.

Anyone correct me if I'm wrong!