Support Board
Date/Time: Sun, 24 Nov 2024 06:45:24 +0000
remote build not working
View Count: 355
| [2024-05-17 10:27:36] |
| User255315 - Posts: 133 |
|
Hi SC, The remote build feature doesnt seem to be working ..... HTTPS connection ID:1 to build.sierrachart.com:443 for request ID:1 (3) | Connecting to IP: 38.142.170.157. | 2024-05-17 09:32:06.600 HTTPS connection ID:1 to build.sierrachart.com:443 for request ID:1 (3) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2024-05-17 09:32:27.623 * The above message is from the message log. |
| [2024-05-17 14:52:26] |
| Sierra_Chart Engineering - Posts: 17154 |
|
We are not seeing any connection problem at this time. Try again.
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-05-30 10:44:41] |
| User255315 - Posts: 133 |
|
hi SC, when we try to ping the sierra server we see very inconsistent latency times, and sometimes we are getting time out messages as well, we have asked our network team to look in to this, in the meantime could you please let us know if its a problem with our network or do you see any issues with your servers Thanks |
| [2024-05-30 11:07:45] |
| User255315 - Posts: 133 |
|
HTTPS connection ID:1 to build.sierrachart.com:443 for request ID:1 (7) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2024-05-30 10:57:47.040 * DTC Client socket (8) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2024-05-30 10:57:47.040 * Denali Data Feed | Server has requested a logoff. Reason: No heartbeat messages received for 61.4 seconds. Stopping connection. | 2024-05-30 10:58:05.068 these are some of the messages i see on the message log, looks most likely an issue with our network, just wanted to check with you guys as well Thanks |
| [2024-05-30 12:22:56] |
| Sierra_Chart Engineering - Posts: 17154 |
|
This is not an issue on your side, our Internet provider Cogent has de-peered with Tata. Most likely this is the problem. Tata is an Indian ISP. We expect to have a replacement ISP operational this evening. We apologize for the issue. This is a temporary server you can use for the time being.: ds21.sierracharts.com Enter the server address, in this field: Sierra Chart Server Settings: CME Exchange Data Feed Server Address and Port Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) (CME Exchange Data Feed Server Address and Port Override) Make sure you are running an up-to-date version of Sierra Chart. Instructions: Software Download: Fast Update This only applies to CME data. Not to other exchanges. It also does not apply to historical data either. Just real-time data. We are going to try to put out a new release within the hour for support for historical data also from this address. 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-05-30 12:30:34] |
| User255315 - Posts: 133 |
|
Hi SC, thank you so much for your update, appreciate it. |
| [2024-05-30 12:34:43] |
| Sierra_Chart Engineering - Posts: 17154 |
|
Can you also provide us a trace route (tracert) and a ping from the command line, to this server: ds28.sierracharts.com Cogent is asking for this. We don't think they are going to resolve this. We are implementing support for a new ISP this evening at least we hope it is this evening. We just want to have the information so at least we have a case we have started with Cogent regarding this. 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-05-30 13:11:56] |
| User255315 - Posts: 133 |
|
Hi SC, please find below the requested details, Tracing route to ds28.sierracharts.com [38.103.112.187] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.132.25.10 2 1 ms 1 ms <1 ms 10.132.5.1 3 30 ms 14 ms 14 ms 16.46.26a9.ip4.static.sl-reverse.com [169.38.70.22] 4 15 ms 15 ms 27 ms 169.254.151.242 5 15 ms 15 ms 15 ms ae11.dar02.che01.networklayer.com [169.38.118.132] 6 45 ms 15 ms 15 ms ae9.cbs01.sr01.che01.networklayer.com [169.53.17.191] 7 14 ms 15 ms 15 ms bb.11.35a9.ip4.static.sl-reverse.com [169.53.17.187] 8 27 ms 19 ms 26 ms 125.16.7.65 9 * * * Request timed out. 10 * * * Request timed out. 11 465 ms 547 ms 499 ms be3360.ccr42.lax01.atlas.cogentco.com [154.54.25.149] 12 * 508 ms * be3177.ccr22.sjc01.atlas.cogentco.com [154.54.40.146] 13 479 ms * 523 ms be3179.ccr22.sfo01.atlas.cogentco.com [154.54.43.149] 14 491 ms 453 ms 507 ms be3110.ccr32.slc01.atlas.cogentco.com [154.54.44.142] 15 530 ms 540 ms 549 ms be3038.ccr22.den01.atlas.cogentco.com [154.54.42.98] 16 512 ms * 551 ms be3036.ccr22.mci01.atlas.cogentco.com [154.54.31.90] 17 407 ms 400 ms 396 ms be2832.ccr42.ord01.atlas.cogentco.com [154.54.44.170] 18 414 ms 400 ms 380 ms be2766.ccr41.ord03.atlas.cogentco.com [154.54.46.178] 19 272 ms 271 ms 273 ms be2051.agr61.ord03.atlas.cogentco.com [154.54.84.50] 20 580 ms * * 38.103.112.187 21 540 ms 577 ms 569 ms 38.103.112.187 Trace complete. Pinging ds28.sierracharts.com [38.103.112.187] with 32 bytes of data: Reply from 38.103.112.187: bytes=32 time=617ms TTL=44 Reply from 38.103.112.187: bytes=32 time=623ms TTL=44 Reply from 38.103.112.187: bytes=32 time=566ms TTL=44 Request timed out. Ping statistics for 38.103.112.187: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 566ms, Maximum = 623ms, Average = 602ms |
| [2024-05-30 14:06:29] |
| Sierra_Chart Engineering - Posts: 17154 |
|
That really is very terrible latency. Update to the current version which is 2643. Instructions: Software Download: Fast Update Set this setting: Sierra Chart Server Settings: CME Exchange Data Feed Server Address and Port Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) to ds21.sierracharts.com There is a new setting in this new version that we added named: "CME Exchange Data Feed Historical Server Address Override" also set that to: ds21.sierracharts.com. This is an interim solution until we add two additional ISPs which we expect will be completed by morning. Follow up with again, for what you need to do at that time or you can stay with the settings for a week or so but they should only be used temporarily. 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-05-30 15:14:56] |
| User255315 - Posts: 133 |
|
sure will do it now.
|
| [2024-06-17 13:11:27] |
| Sierra_Chart Engineering - Posts: 17154 |
|
At the end of the week, there will be a change to DS21.sierracharts.com to allow it only for our own internal use. For this setting: Sierra Chart Server Settings: CME Exchange Data Feed Server Address and Port Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) Use one of the following servers: ds32.sierracharts.com ds32-2.sierracharts.com ds25.sierracharts.com ds25-2.sierracharts.com For this setting: Sierra Chart Server Settings: CME Exchange Data Feed Historical Server Address Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) Set it to ds32.sierracharts.com And then you will need to reconnect with File >> Reconnect. The Internet connectivity with these servers will be fine. The routing goes over Tata communications in Ashburn Virginia and then from there on the packets go to India eastward. 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-06-17 13:11:43
|
To post a message in this thread, you need to log in with your Sierra Chart account: