Support Board
Date/Time: Mon, 25 Nov 2024 04:41:01 +0000
ping futurestrading14.sierracharts.com
View Count: 330
| [2024-04-03 09:23:20] |
| User676363 - Posts: 72 |
|
Hello, Can somebody please help me to check the services for real time data? Below I have my tests, logs, etc. Basically getting a lot of timeout errors and finding some possible areas of the docs that we need to update. Maybe, instead of this script, there is a page showing the live status of the servers that also reports downtime and resolution issues if they occur? Would be helpful so that I do not post needlessly something that I should be able to solve alone. In this case, I get failures both from google's hosting and from my own hosting, so I am hoping that is a thorough check. Docs: Data/Trading Service Connection and Symbol Issues The article on ping at the bottom is no longer available. Also I can't find the settings mentioned in the text here: There is also the Global Settings >> Data/Trade Service Settings >> SC Server Settings >> Always use Port 443 for Real-Time Data setting. However, when using data compression, this port will not be used.
Test that is failing: ping futurestrading14.sierracharts.com --- ds22.sierracharts.com ping statistics --- 398 packets transmitted, 0 received, 100% packet loss, time 406508ms Python code (can be run using https://colab.new) import socket import time # Define the list of sites to test sites = [ "ds3.sierracharts.com", "ds4.sierracharts.com", "ds4-2.sierracharts.com", "ds12.sierracharts.com", "ds12-2.sierracharts.com", "ds13-2.sierracharts.com", "ds13-3.sierracharts.com", "ds13.sierracharts.com", "ds14.sierracharts.com", "ds21.sierracharts.com", "ds22.sierracharts.com", "ds23.sierracharts.com", "ds23-2.sierracharts.com", "ds24.sierracharts.com", "ds25.sierracharts.com", "ds26.sierracharts.com", "ds26-2.sierracharts.com", "ds27.sierracharts.com", "ds28.sierracharts.com", "ds28-2.sierracharts.com", "ds30.sierracharts.com", "ds30-2.sierracharts.com", "ds31.sierracharts.com", "ds31-2.sierracharts.com", "futurestrading1.sierracharts.com", "futurestrading2.sierracharts.com", "futurestrading3.sierracharts.com", "futurestrading4.sierracharts.com", "futurestrading10.sierracharts.com", "futurestrading11.sierracharts.com", "futurestrading12.sierracharts.com", "futurestrading13.sierracharts.com", "futurestrading14.sierracharts.com", "futurestrading15.sierracharts.com", "futurestrading16.sierracharts.com", "futurestrading17.sierracharts.com", "futurestrading18.sierracharts.com", "futurestrading19.sierracharts.com", "tradesimulation1.sierracharts.com", "tradesimulation2.sierracharts.com", "tradesimulation3.sierracharts.com", "tradesimulation4.sierracharts.com", "tradesimulation5.sierracharts.com", "lmaxtrade2.sierracharts.com", "lmaxtrade3.sierracharts.com", "lmaxhd.sierracharts.com", "lmaxrt.sierracharts.com", "lmaxrt2.sierracharts.com" ] def test_ping(site, port): try: start_time = time.time() # Attempt to connect to the site on the specified port socket.setdefaulttimeout(2) # Timeout in seconds socket.socket(socket.AF_INET, socket.SOCK_STREAM).connect((site, port)) end_time = time.time() return "Site is reachable", end_time - start_time except Exception as e: return f"Failed with exception: {str(e)}", None def main(): print("Starting site testing...") total_time = 0 port = 443 # Change this to the desired port for site in sites: print(f"Testing {site} on port {port}...") result, time_taken = test_ping(site, port) if time_taken is not None: print(f"Test result for {site}: {result}, Time taken: {time_taken:.2f} seconds") total_time += time_taken else: print(f"Test result for {site}: {result}") # Calculate and print average time if total_time > 0: average_time = total_time / len(sites) print(f"\nAverage time taken for all sites: {average_time:.2f} seconds") if __name__ == "__main__": main() Results: Average time taken for all sites: 0.05 seconds
Sites that timed out: ds21.sierracharts.com ds25.sierracharts.com ds30-2.sierracharts.com futurestrading1.sierracharts.com futurestrading11.sierracharts.com futurestrading13.sierracharts.com futurestrading15.sierracharts.com futurestrading17.sierracharts.com futurestrading18.sierracharts.com futurestrading19.sierracharts.com When I run from my system I get: Average time taken for all sites: 0.01 seconds
So, I should have no problems, but, I am experiencing this: 2024-04-03 05:09:53.643 | Teton CME Order Routing | Firm: Phillip Capital
2024-04-03 05:09:53.643 | Teton CME Order Routing | Connecting to the server futurestrading14.sierracharts.com. Port 11089 2024-04-03 05:09:53.645 | DTC Client socket (1) | Creating socket. Using TLS 1.2. 2024-04-03 05:09:53.646 | DTC Client socket (1) | New receive buffer size: 0 2024-04-03 05:09:53.646 | DTC Client socket (1) | Connecting to IP: 208.185.224.130. 2024-04-03 05:10:13.645 | Teton CME Order Routing | Timeout connecting to server. 2024-04-03 05:10:13.645 | Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. 2024-04-03 05:10:13.645 | Select 'File >> Disconnect' to prevent further connection attempts. 2024-04-03 05:10:13.655 | DTC Client socket (1) | CloseSocket call. 2024-04-03 05:10:13.655 | Teton CME Order Routing | Disconnected. 2024-04-03 05:10:13.655 | Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. 2024-04-03 05:10:13.656 | DTC Client socket (1) | Closed. A more basic test like this also fails: ping -c 4 futurestrading14.sierracharts.com PING ds22.sierracharts.com (208.185.224.130): 56 data bytes
Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 --- ds22.sierracharts.com ping statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss |
| [2024-04-03 13:48:57] |
| Sierra_Chart Engineering - Posts: 17169 |
|
The trading servers will not respond to a ping. We do not see a problem connecting to that server: 2024-04-03 09:37:41.972 | Unset | Teton CME Order Routing | Connecting to the server futurestrading14.sierracharts.com. Port 11089 2024-04-03 09:37:41.999 | Network | DTC Client socket (2) | Creating socket. Using TLS 1.2. 2024-04-03 09:37:41.999 | Network | DTC Client socket (2) | Send buffer size: 0 2024-04-03 09:37:41.999 | Network | DTC Client socket (2) | New receive buffer size: 0 2024-04-03 09:37:41.999 | Network | DTC Client socket (2) | Receive buffer size: 0 2024-04-03 09:37:41.999 | Network | DTC Client socket (2) | Connecting to IP: 208.185.224.130. 2024-04-03 09:37:42.003 | Unset | Teton CME Order Routing | Network connection to server complete. 2024-04-03 09:37:42.003 | Unset | Teton CME Order Routing | Starting socket receive thread. 2024-04-03 09:37:42.003 | Unset | Teton CME Order Routing | Sending encoding request to server: Binary VLS. Compression: none 2024-04-03 09:37:42.012 | Unset | Teton CME Order Routing | Setting DTC encoding to Binary VLS 2024-04-03 09:37:42.012 | Unset | Teton CME Order Routing | Sending logon request message. 2024-04-03 09:37:42.243 | Unset | Teton CME Order Routing | Received logon response. 2024-04-03 09:37:42.243 | Unset | Teton CME Order Routing | Server Name: SC DTC Server. 2024-04-03 09:37:42.243 | Unset | Teton CME Order Routing | Server protocol version: 8. Client protocol version: 8 2024-04-03 09:37:42.243 | Unset | Teton CME Order Routing | Connection error: No trade accounts assigned * Therefore, this would be caused by a firewall on your side or some other connectivity issue. Refer to this help topic: Data/Trading Service Connection and Symbol Issues: 1.2. Network Communication or Server Problem 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-04-03 13:49:47
|
| [2024-04-03 13:49:16] |
| User676363 - Posts: 72 |
|
I found the location of Always Use Port 443 For Real-Time Data. It is located under Global Settings > Sierra Chart Server Settings Sure will be nice if we can just search and find the commands. I don't care what menu they are in, I just want to have instant access to editing the params. Even a json or yaml file that I can edit by hand and save would be fantastic. Anyhow, that can be fixed in the docs here: Data/Trading Service Connection and Symbol Issues: Internet Ports However, I still have the same results and it doesn't use 443: 2024-04-03 09:47:29.095 | Teton CME Order Routing | Firm: Phillip Capital
2024-04-03 09:47:29.095 | Teton CME Order Routing | Connecting to the server futurestrading17.sierracharts.com. Port 11088 2024-04-03 09:47:29.105 | DTC Client socket (1) | Creating socket. Using TLS 1.2. 2024-04-03 09:47:29.107 | DTC Client socket (1) | New receive buffer size: 0 2024-04-03 09:47:29.107 | DTC Client socket (1) | Connecting to IP: 216.1.90.129. 2024-04-03 09:47:49.117 | Teton CME Order Routing | Timeout connecting to server. 2024-04-03 09:47:49.117 | Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. 2024-04-03 09:47:49.117 | Select 'File >> Disconnect' to prevent further connection attempts. 2024-04-03 09:47:49.133 | DTC Client socket (1) | CloseSocket call. 2024-04-03 09:47:49.134 | Teton CME Order Routing | Disconnected. 2024-04-03 09:47:49.134 | Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. 2024-04-03 09:47:49.136 | DTC Client socket (1) | Closed. |
| [2024-04-03 13:50:48] |
| Sierra_Chart Engineering - Posts: 17169 |
|
443 is not used for trading servers.
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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-04-03 15:43:23] |
| User676363 - Posts: 72 |
|
A reboot of my system was required to fix the issue. So, entirely my problem and caused by the operating system I guess. I'll leave the script and the notes in case they are helpful for somebody else. Thanks for the info about the 443. |
To post a message in this thread, you need to log in with your Sierra Chart account: