Support Board
Date/Time: Sat, 23 Nov 2024 19:30:41 +0000
Bitcoin Trading Order not executed: Orders Info request failed result":"error","error":"Identifi
View Count: 3944
| [2013-07-13 12:39:59] |
| User59357 - Posts: 15 |
|
Hello Support Team, all of a sudden I got the error message below: Orders Info request failed | 2013-07-13 14:33:12 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-13 14:33:12 Orders Info request failed | 2013-07-13 14:33:28 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-13 14:33:28 Orders Info request failed | 2013-07-13 14:33:42 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-13 14:33:42 Orders Info request failed | 2013-07-13 14:33:58 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-13 14:33:58 Orders Info request failed | 2013-07-13 14:34:12 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-13 14:34:12 The automatic Bitcoin order was not executed: Auto-Trading: BTCUSD 30 min #1 | Parabolic BTC Trading | SellEntry reversal order processed. Quantity: 73028 | Bar Start Time: 2013-07-13 16:00:00 | 2013-07-13 16:15:16 Trade Order Error - MtGox order update (Rejected) - Identification required to access private API. Internal Order ID: 108. Symbol: BTCUSD | 2013-07-13 16:15:16 Auto-Trading: BTCUSD 30 min #1 | Parabolic BTC Trading | SellEntry reversal order processed. Quantity: 73028 | Bar Start Time: 2013-07-13 23:00:00 | 2013-07-13 23:29:52 Trade Order Error - MtGox order update (Rejected) - Identification required to access private API. Internal Order ID: 110. Symbol: BTCUSD | 2013-07-13 23:29:52 Manual trading is working with the same passkey, the system was also able to go long automatically. It seems so it is sometimes working and sometimes not. What might be the reason? How can I fix this? I would like to be sure orders will be executed properly in the future. Thank you in advance! Date Time Of Last Edit: 2013-07-13 21:36:38
|
| [2013-07-14 23:07:46] |
| |
|
As we have documented here: http://www.sierrachart.com/index.php?l=doc/Bitcoin.php#MTGoxTrading The interface that MTGox and other Bitcoin exchanges provide for trading is substandard so they are not entirely reliable. Here is a quote: We want to make a comment about Bitcoin trading in general. Sierra Chart is a very reliable high-performance trading platform. The types of trading interfaces provided by Bitcoin exchanges at the time of this writing, are substandard. They are far from the capabilities, structure, and data organization required for reliable and trouble-free trading. This does not mean that the integration to MTGox is unreliable, it is as best as we can make it, but it is nowhere near the kind of quality that would be obtained when using a FIX connection and performing trading through major exchanges like the CME or NYSE.
We encourage Bitcoin exchanges to adopt GSP in order to provide the necessary interface required by Sierra Chart for reliable integration. Sierra Chart will not be adding support for trading with any other Bitcoin exchanges, unless they make substantial improvements with their functionality or adopt GSP (General Data and Trading Service Protocol) or make some kind of effort to work with us. We will check on what this might be from and see what we can do. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2013-07-15 04:03:27] |
| |
|
That bitcoin message would imply the Tonce value is invalid (this is a unique timestamp that has to increase). We form the value based on the recommended algorithm that MtGox provides (basically just the current time in microseconds, and we make sure that each value is larger than last one sent). This is all common code, so there should be no difference between manual and auto trading code. We suspect it is an issue on the MtGox side.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2013-07-15 06:34:11
|
| [2013-07-15 05:32:50] |
| User59357 - Posts: 15 |
|
Hello, thank you very much for looking into this issue. For now it is working again. Maybe I should consider to get in touch with Mt.Gox as well about this topic. It would be helpful if we could reach more stability here. Kind regards |
| [2013-07-15 06:33:19] |
| |
|
Please tell MTGox: Could you please explain why this error was returned when requesting the open orders:
: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" Sierra Chart engineering has said: That bitcoin message would imply the Tonce value is invalid (this is a unique timestamp that has to increase). We form the value based on the recommended algorithm that MtGox provides (basically just the current time in microseconds, and we make sure that each value is larger than last one sent). Sierra Chart has said you should use GSP for trading: http://www.sierrachart.com/index.php?l=doc/doc_GeneralDataTradeServiceProtocol.php I would really like it if you do this. You really should. Sierra Chart is a great program. Sierra Chart also said: Sierra Chart is a very reliable high-performance trading platform. The types of trading interfaces provided by Bitcoin exchanges at the time of this writing, are substandard. They are far from the capabilities, structure, and data organization required for reliable and trouble-free trading. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2013-07-15 08:41:25] |
| User59357 - Posts: 15 |
|
Hi, I will take care of this. As soon as I have a response from Mt.Gox I will let you know, by posting the result into the Support Board. I like the potential of Sierra Chart as well. I will definitely look deeper into study programming also for automatically trading of other markets e.g. CFD's. Have a nice day :-) Kind regards Date Time Of Last Edit: 2013-07-15 08:42:20
|
| [2013-07-15 09:05:22] |
| |
|
OK thank you.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2013-07-24 18:25:42] |
| User59357 - Posts: 15 |
|
Hello Support Team, as agreed I took care about the issue. I have contacted the MtGox support on this. The outcome is that there is no issue on the side of MtGox, but the issue is still persistent via Sierra Chart. Unfortunately I am not able to categorize automated Bitcoin Trading via Sierra Chart as stable by now. Please find the conversation with the MtGox below: Ticket #103707: Trading Order not executed: Orders Info request failed result... Your request (#103707) has been updated. To review the status of the request and add additional comments, follow the link below: http://support.mtgox.com/tickets/103707 Ravi Support, Jul 24 21:32 (JST): Hello Thomas, We did a small research here and is there a way that you could confirm if the Sierra Chart platform is not calling the api from multiple threads. You may check with their technical team and let us know on the same. Best regards, Mt.Gox Team https://www.mtgox.com [Attention: Please protect your account using OTP to ensure that your funds are safe and secure. Failing to do so makes your information vulnerable to hackers. Please visit https://mtgox.com/security] **** Thomas, Jul 17 01:02 (JST): Hello Support Team, I am using Sierra Chart because I would like to use mathematical chart analyzing methods / technical indicators. Bot trading is not really interesting to me, also the MtGOx fees are quite expensive for high frequent trading.. By the way, it has just stopped working today again: ALL NORMAL: Real-time data for symbol BTCUSD is temporarily unavailable. | 2013-07-16 12:49:53 Real-time data for symbol BTCUSD has been restored. | 2013-07-16 12:51:08 HD Request # 189 - Downloading Intraday chart data for BTCUSD to the file BTCUSD.scid. Service: scsrv | 2013-07-16 12:51:08 HD Request # 189 - Starting date and time: 2013-07-16 12:46:15 | 2013-07-16 12:51:08 HD Request # 189 - Using server: btc.sierracharts.com port 10049 | 2013-07-16 12:51:08 The network socket is connected. | 2013-07-16 12:51:08 HD Request # 189 - Requesting up to 93 days of Intraday data. | 2013-07-16 12:51:08 HD Request # 189 - Decompressing data. | 2013-07-16 12:51:09 HD Request # 189 - Receiving Intraday data for BTCUSD starting at 2013-07-16 12:46:15 | 2013-07-16 12:51:09 HD Request # 189 - Timestamp of first Intraday data file record written: 2013-07-16 12:46:15 | 2013-07-16 12:51:09 Socket closed. No error. | 2013-07-16 12:51:09 HD Request # 189 - Received 2 records from 2013-07-16 12:46:15 to 2013-07-16 12:49:58 (3.7 minutes) and wrote 2 records for BTCUSD | 2013-07-16 12:51:09 HD Request # 189 - Intraday download COMPLETE for BTCUSD | 2013-07-16 12:51:09 Real-time intraday chart data file updates started for BTCUSD | 2013-07-16 12:51:09 HERE THE ERROR COMES ALL OF A SUDDEN AGAIN: Orders Info request failed | 2013-07-16 13:02:35 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-16 13:02:35 Orders Info request failed | 2013-07-16 13:02:50 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-16 13:02:50 Orders Info request failed | 2013-07-16 13:03:35 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-16 13:03:35 Position Info request failed | 2013-07-16 13:04:30 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-16 13:04:30 Orders Info request failed | 2013-07-16 13:05:05 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-16 13:05:05 Orders Info request failed | 2013-07-16 13:05:50 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-16 13:05:50 Orders Info request failed | 2013-07-16 13:06:35 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-16 13:06:35 Thank you for looking into this issue. With kind regards. **** Ravi Support, Jul 16 21:16 (JST): Hello Thomas, Honestly there were no issues reported on the API keys so far or the most recent. Kindly be noted that we are no way related to Sierra Trading and they have built their own platform to felicitate the MTGox trades happening within their platform. May i ask you, any special reasons you are using Sierra Trading? you could very well be a part of our trading platform and enjoy trading. We cannot guarantee or offer any security if any 3rd party platforms are used. As far as "Bot Trading" or automatic trading is concerned, we would recommend that the providers need to ensure all which is mentioned through our API documentation - what ever may be the platform they build. Hope this clears and let me know if you have any questions. Best regards, Mt.Gox Team https://www.mtgox.com [Attention: Please protect your account using OTP to ensure that your funds are safe and secure. Failing to do so makes your information vulnerable to hackers. Please visit https://mtgox.com/security] **** Thomas, Jul 16 05:25 (JST): Hello Mt.Gox Team, I was using the API Key / Secret already for automatic trading. All of a sudden it stopped working without any changes on my side. After a while I have created a new API Key / Secret and it was working again, but relatively unstable (some orders where executed and some not). Since yesterday it is working stable again. Maybe you are probably aware of technical issues regarding the API / Automatic Trading via Sierra Chart? I would like to be sure that the service is working stable, especially when it comes to automatic trading with bigger positions in the future. Thank you in advance for looking into this topic. With Kind Regards Thomas **** Ravi Support, Jul 16 00:42 (JST): Hello Thomas, Thanks for the patience, I have reviewed the guide offered from your trading company, http://www.sierrachart.com/index.php?l=doc/Bitcoin.php As mentioned in the setup, for the trade activities you would require to use API Key / Secret. This would need to generated from your Mtgox account. By any chance have you tried using fresh new keys? Also is the error message you started receiving recently or this is the case from the day you started using Sierra Chart. Kindly let me know and we would be glad to work along with you. Best regards, Mt.Gox Team https://www.mtgox.com [Attention: Please protect your account using OTP to ensure that your funds are safe and secure. Failing to do so makes your information vulnerable to hackers. Please visit https://mtgox.com/security] Sharon Support, Jul 15 19:25 (JST): Hello Thomas, Thank you for your email. We will have a check on this issue and keep you updated as earliest. Best regards, Mt.Gox Team https://www.mtgox.com [Attention: Please protect your account using OTP to ensure that your funds are safe and secure. Failing to do so makes your information vulnerable to hackers. Please visit https://mtgox.com/security] Thomas, Jul 15 18:23 (JST): Hello MT.GOX Support Team, I am using Sierra Chart for automatic BitCoin trading. From time to time I get the error message below: Orders Info request failed | 2013-07-13 14:33:12 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" 2013-07-13 14:33:12 Orders Info request failed | 2013-07-13 14:33:28 Trade Order Error - MtGox order update (Rejected) - Identification required to access private API. Internal Order ID: 108. Symbol: BTCUSD | 2013-07-13 16:15:16 Which has led into orders not being executed. I also got in touch with Sierra Chart for further troubleshooting: Could you please explain why this error was returned when requesting the open orders: : {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" Sierra Chart engineering has said: That bitcoin message would imply the Tonce value is invalid (this is a unique timestamp that has to increase). We form the value based on the recommended algorithm that MtGox provides (basically just the current time in microseconds, and we make sure that each value is larger than last one sent). Sierra Chart has said you should use GSP for trading: http://www.sierrachart.com/index.php?l=doc/doc_GeneralDataTradeServiceProtocol.php I would really like it if you do this. Sierra Chart also said: Sierra Chart is a very reliable high-performance trading platform. The types of trading interfaces provided by Bitcoin exchanges at the time of this writing, are substandard. They are far from the capabilities, structure, and data organization required for reliable and trouble-free trading. Could you please look into this issue? It would be quite helpful if we could reach more stability in automatic trading. Thank you in advance! Date Time Of Last Edit: 2013-07-26 06:25:34
|
| [2013-07-25 02:48:01] |
| |
|
The answer to this is definitely no: We did a small research here and is there a way that you could confirm if the Sierra Chart platform is not calling the api from multiple threads. You may check with their technical team and let us know on the same. We need to know with a greater amount of detail why the tonce is considered invalid. It is always guaranteed to be a unique value. "Identification required to access private API","token":"login_error_invalid_tonce"
We did make some changes with how we set tonce . This will be out in the next release, version 1000, today or tomorrow. The changes to it, do not seem as though they would help though. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2013-07-26 06:38:18] |
| User59357 - Posts: 15 |
|
Hello Sierra Support, I would appreachite it very much if you could look into your application as well. I am looking forward to the next release of Sierra Chart. With kind regards, T. |
| [2013-07-26 06:43:05] |
| |
|
Just let you know version 1000 will not be out until later today. As we said, MTGox and other Bitcoin exchanges, have to go a long way to improve trading interfaces they provide. They are far from the required standards needed. While supporting the GSP protocol may be too big of a step for them right now, there are some reasonable small changes they can make. We are open to providing that information if they are willing to listen. -Basically they need to support a TCP/IP socket for trading that continues to remain open for the duration of the trading session. -Over the socket they need to send automatic updates for an order This would include when an order is filled, modified, or canceled. -They need to maintain an order list that holds not only open orders, but also orders that have recently been canceled and filled as well. -They need to use very well structured consistent data structures to communicate order data , Order actions, order fills, and positions. If they adopt GSP, then this protocol supports all of this and more. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2013-07-26 06:48:56
|
| [2013-07-26 07:01:38] |
| |
|
We have reviewed the documentation here about the parameter that they are indicating is not correct: https://en.bitcoin.it/wiki/MtGox/API/HTTP#tonce_and_nonce We have a much better idea of what the problem is now. There was definitely a bug found in Sierra Chart which could cause a problem and it is resolved in version 1000. You also need to make sure your computer's clock is set very accurately. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2013-07-31 19:32:09] |
| User59357 - Posts: 15 |
|
Hello Sierra Chart Team, thank you for looking into the problem. I just would like to let you know that the issue is still persistent. Or lets say Sierra Chart is unstable. Sometimes is working, sometimes I got the login issue. Last time was quite annoying, because my trading system has detected the price breakout at 94.- USD but the trade was not executed so I missed quite a trade. I set the trade manually at 104.- USD and my trading system sold automatically at 108.- USD. This trade was fortunately executed as it should. Log-file wise it looks like this: So there are quite some errors in it. Real-time intraday chart data file updates started for BTCUSD | 2013-07-31 10:22:16 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:41:54 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:41:54 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:42:09 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:42:09 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:42:24 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:42:24 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:42:39 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:42:39 Real-time data for symbol BTCUSD is temporarily unavailable. | 2013-07-31 10:42:50 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:42:54 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:42:54 Get Orders Info not done because request is already outstanding | 2013-07-31 10:43:24 Orders Info request failed | 2013-07-31 10:43:24 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-31 10:43:24 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:43:39 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:43:39 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:43:54 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:43:54 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:44:09 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:44:10 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:44:24 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:44:24 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:44:39 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:44:39 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:44:55 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:44:55 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:45:09 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:45:09 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:45:24 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:45:24 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:45:39 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:45:39 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:45:55 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:45:55 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:46:10 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:46:10 Real-time data for symbol BTCUSD has been restored. | 2013-07-31 10:46:24 HD Request # 13 - Downloading Intraday chart data for BTCUSD to the file BTCUSD.scid. Service: scsrv | 2013-07-31 10:46:24 HD Request # 13 - Starting date and time: 2013-07-31 10:40:07 | 2013-07-31 10:46:24 HD Request # 13 - Using server: btc.sierracharts.com port 10049 | 2013-07-31 10:46:24 The network socket is connected. | 2013-07-31 10:46:24 HD Request # 13 - Requesting up to 93 days of Intraday data. | 2013-07-31 10:46:24 HD Request # 13 - Decompressing data. | 2013-07-31 10:46:24 Socket closed. No error. | 2013-07-31 10:46:24 HD Request # 13 - Received 0 records and wrote 0 records for BTCUSD | 2013-07-31 10:46:24 HD Request # 13 - Intraday download COMPLETE for BTCUSD | 2013-07-31 10:46:24 Real-time intraday chart data file updates started for BTCUSD | 2013-07-31 10:46:25 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:46:25 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:46:25 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:46:39 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:46:39 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:46:54 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:46:54 Real-time data for symbol BTCUSD is temporarily unavailable. | 2013-07-31 10:47:00 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:47:10 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:47:10 Get Orders Info not done because request is already outstanding | 2013-07-31 10:47:39 Orders Info request failed | 2013-07-31 10:47:42 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-31 10:47:42 Get Orders Info not done because request is already outstanding | 2013-07-31 10:48:09 Orders Info request failed | 2013-07-31 10:48:14 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-31 10:48:14 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:48:24 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:48:24 Get Orders Info not done because request is already outstanding | 2013-07-31 10:48:54 Orders Info request failed | 2013-07-31 10:48:57 Server data line: {"result":"error","error":"Identification required to access private API","token":"login_error_invalid_tonce"}" | 2013-07-31 10:48:57 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:49:35 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:49:35 JSON Parse Error: Expect either an object or array at root | 2013-07-31 10:50:09 Server data line: <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.4.0</center> </body> </html> " | 2013-07-31 10:50:09 Real-time data for symbol BTCUSD has been restored. | 2013-07-31 10:51:11 HD Request # 15 - Downloading Intraday chart data for BTCUSD to the file BTCUSD.scid. Service: scsrv | 2013-07-31 10:51:11 HD Request # 15 - Starting date and time: 2013-07-31 10:40:07 | 2013-07-31 10:51:11 HD Request # 15 - Using server: btc.sierracharts.com port 10049 | 2013-07-31 10:51:11 The network socket is connected. | 2013-07-31 10:51:11 HD Request # 15 - Requesting up to 93 days of Intraday data. | 2013-07-31 10:51:11 HD Request # 15 - Decompressing data. | 2013-07-31 10:51:11 Socket closed. No error. | 2013-07-31 10:51:11 HD Request # 15 - Received 0 records and wrote 0 records for BTCUSD | 2013-07-31 10:51:11 HD Request # 15 - Intraday download COMPLETE for BTCUSD | 2013-07-31 10:51:11 Real-time intraday chart data file updates started for BTCUSD | 2013-07-31 10:51:11 Real-time data for symbol BTCUSD is temporarily unavailable. | 2013-07-31 10:51:19 Real-time data for symbol BTCUSD has been restored. | 2013-07-31 10:51:30 HD Request # 17 - Downloading Intraday chart data for BTCUSD to the file BTCUSD.scid. Service: scsrv | 2013-07-31 10:51:30 HD Request # 17 - Starting date and time: 2013-07-31 10:40:07 | 2013-07-31 10:51:30 HD Request # 17 - Using server: btc.sierracharts.com port 10049 | 2013-07-31 10:51:30 The network socket is connected. | 2013-07-31 10:51:30 HD Request # 17 - Requesting up to 93 days of Intraday data. | 2013-07-31 10:51:30 HD Request # 17 - Decompressing data. | 2013-07-31 10:51:30 Socket closed. No error. | 2013-07-31 10:51:30 HD Request # 17 - Received 0 records and wrote 0 records for BTCUSD | 2013-07-31 10:51:30 HD Request # 17 - Intraday download COMPLETE for BTCUSD | 2013-07-31 10:51:30 Real-time intraday chart data file updates started for BTCUSD | 2013-07-31 10:51:31 Get Orders Info not done because request is already outstanding | 2013-07-31 17:15:06 Thank you in advance for looking into the problem. P.s. I have also informed Mt.Gox on the latest status. With kind regards, Thomas Date Time Of Last Edit: 2013-07-31 19:36:16
|
| [2013-07-31 19:59:37] |
| |
|
Why do you say this: Or lets say Sierra Chart is unstable.
Sierra Chart is very solid well engineered software. As we have said many times, the MTGox API is very substandard. They have a lot of work to do to improve it. All we see from the provided Message Log, is server problems on the MTGox side. For example, the MTGox server has repeatedly said "502 Bad Gateway". That is a MTGox server problem. As long as your computer's clock is set accurately to within 10 seconds, all issues will be on the MTGox side. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2013-07-31 20:01:23] |
| |
|
The only issue we need to look into, to confirm that we are handling the requests and responses properly is this: Get Orders Info not done because request is already outstanding
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2013-07-31 20:16:49] |
| User59357 - Posts: 15 |
|
Hello Sierra Chart Support, my apologies, not Sierra Chart the application itself is unstable. The login issue towards Mt.Gox makes it "unstable / unreliable" from an automatic Bitcoin trading point of view. It might work much better towards other Brokers / Providers / Markets, but automatic Bitcoin trading appears to me quite experimental. Which is fine until a certain point. It could well be that the issue is on the side of Mt.Gox, even if they say it is not. My Computer Clock is fine, so there are no time differences which might lead into the login issue. I will wait for the answer of Mt.Gox, I will let you know. I hope it helps. With kind regards, Thomas |
| [2013-07-31 20:55:22] |
| |
|
Thank you for the clarification. We are more than happy to work with MTGox for recommendations on what they need to do to improve their interface. We could add support for trading on another bitcoin exchange, but we just are very leery of spending more time on that with other higher priorities and the fact that they all provide substandard interfaces. Our priorities must be to our main user base. We have done a complete code review relating to HTTP requests to the MTGox system. There have been some changes made to improve the retry logic related to error handling. Although we did not see any issues which involve the particular problems you encountered in the log. We confirm those must be on the MTGox side. About 2 years ago MTGox contacted us, and we had a call with them and the CEO was in that call. They wanted us to add support for their market data and trading. It was something we did not spend too much time on at the time because we were very busy and we did not have enough time to study the protocol and for another business reason ( the bitcoin market was very small and did not have the very best reputation). One thing they did express to us is that they wanted to have very reliable trading integration. If we had worked on it at the time, what we would have very quickly discovered and communicated to them, was that their trading interface is not nearly at a level which will support reliable trading integration. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2013-07-31 21:01:36
|
To post a message in this thread, you need to log in with your Sierra Chart account: