1
Technical Support & Development / Re: Log blank
« on: June 18, 2017, 09:30:46 PM »
Hello, i keep having the same problem. 
Can someone please help?
Can someone please help?
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Technical Support & Development / Re: jsongui crash
« on: June 16, 2017, 02:19:48 PM »
I had the same issues, always when starting a pair.
3
Technical Support & Development / Re: Log blank
« on: June 15, 2017, 11:53:32 AM »
Ok, just posted it where you recommended me to do it.
See: https://gunthy.org/index.php?topic=353.30
Awaiting reply.
See: https://gunthy.org/index.php?topic=353.30
Awaiting reply.
4
Technical Support & Development / Re: Bugs/Issues tracker v3.3.2
« on: June 15, 2017, 11:51:49 AM »
I have been running around 20 pairs the last couple of days and the "info/console log" on the bottom is totally black, there are no movements registered.
I tried restarting those pairs and the Gunbot started working perfectly on those pairs, it started to buy when the price was low but then the price got up and the Gunbot did not sell.
When I got home I checked the Gunbot and the log at the top showed everything as normal but at the bottom the info log was totally black; no movements registered.
I waited another day but it still did not sell and I had to sell it manually at a small loss..
On the other pairs it runs normally, every 120 sec checking for the price and analyzing the data.
But I am getting these problems on about 30-40% of the pairs that I´m running...
Please help.
For more err.txt files see: https://gunthy.org/index.php?topic=455.0
UPDATE 18/06/17: Keep having the same problem. Can someone please help?
I tried restarting those pairs and the Gunbot started working perfectly on those pairs, it started to buy when the price was low but then the price got up and the Gunbot did not sell.
When I got home I checked the Gunbot and the log at the top showed everything as normal but at the bottom the info log was totally black; no movements registered.
I waited another day but it still did not sell and I had to sell it manually at a small loss..
On the other pairs it runs normally, every 120 sec checking for the price and analyzing the data.
But I am getting these problems on about 30-40% of the pairs that I´m running...
Please help.
For more err.txt files see: https://gunthy.org/index.php?topic=455.0
UPDATE 18/06/17: Keep having the same problem.
Can someone please help?
5
Technical Support & Development / Re: Bugs/Issues tracker v3.3.2
« on: June 15, 2017, 11:48:35 AM »
I keep getting this error, please help; see image in attachment.
9
Technical Support & Development / Log blank
« on: June 15, 2017, 12:45:18 AM »
I have been running around 20 pairs the last couple of days and the "info/console log" on the bottom is totally black, there are no movements registered.
I tried restarting those pairs and the Gunbot started working perfectly on those pairs, it started to buy when the price was low but then the price got up and the Gunbot did not sell.
When I got home I checked the Gunbot and the log at the top showed everything as normal but at the bottom the info log was totally black; no movements registered.
I waited another day but it still did not sell and I had to sell it manually at a small loss..
On the other pairs it runs normally, every 120 sec checking for the price and analyzing the data.
But I am getting these problems on about 30-40% of the pairs that I´m running...
I tried restarting those pairs and the Gunbot started working perfectly on those pairs, it started to buy when the price was low but then the price got up and the Gunbot did not sell.
When I got home I checked the Gunbot and the log at the top showed everything as normal but at the bottom the info log was totally black; no movements registered.
I waited another day but it still did not sell and I had to sell it manually at a small loss..
On the other pairs it runs normally, every 120 sec checking for the price and analyzing the data.
But I am getting these problems on about 30-40% of the pairs that I´m running...
Pages: [1]