Support Board
Date/Time: Mon, 20 Jan 2025 13:58:39 +0000
Post From: Rithmic Data Connection Failure
| [2018-06-06 23:52:04] |
| |
|
Message sent to Rithmic now: Does the issue relate to the environment variables and not to the login parameters when it came to using your backup network?
When I look at what changed in June 2016, among these lines of code: "MML_DMN_SRVR_ADDR=ritpz01001.01.rithmic.com:65000~ritpz01000.01.rithmic.com:65000~ritpz01001.01.rithmic.net:65000~ritpz01000.01.rithmic.net:65000~ritpz01001.01.theomne.net:65000~ritpz01000.01.theomne.net:65000~ritpz01001.01.theomne.com:65000~ritpz01000.01.theomne.com:65000" , "MML_DOMAIN_NAME=rithmic_prod_01_dmz_domain" , "MML_LIC_SRVR_ADDR=ritpz01000.01.rithmic.com:56000~ritpz01001.01.rithmic.com:56000~ritpz01000.01.rithmic.net:56000~ritpz01001.01.rithmic.net:56000~ritpz01000.01.theomne.net:56000~ritpz01001.01.theomne.net:56000~ritpz01000.01.theomne.com:56000~ritpz01001.01.theomne.com:56000" , "MML_LOC_BROK_ADDR=ritpz01000.01.rithmic.com:64100" , "MML_LOGGER_ADDR=ritpz01000.01.rithmic.com:45454~ritpz01000.01.rithmic.net:45454~ritpz01000.01.theomne.com:45454~ritpz01000.01.theomne.net:45454" , "MML_LOG_TYPE=log_net" The only thing that changed, was the LOGGER line. The other lines remained the same and then with the change that we made today, this is the only line that changed but it effectively really did not because the domain names are the same: "MML_LOGGER_ADDR=ritpz01000.01.rithmic.com:45454~ritpz01000.01.rithmic.net:45454~ritpz01000.01.theomne.net:45454~ritpz01000.01.theomne.com:45454" 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 |