How do I check the operation of the data centre? - page 11

New comment
 
Rebooted the terminal, did not change data centre settings (no autoconfiguration, the d/c address is prescribed) - does not want to work on real Alpari.



Now I will remove the d/c address and see.
 
Without the specified data centre address, the terminal works. Anyway, I don't know what's changed there, but it's made so that you can't switch between the demo data centre and the real server. I'll have to install a fifth terminal.
 
Something has gone wrong at Alpari, I just found out that there are two terminals with open orders which were supposed to close at 11-00 Moscow time. I looked at the logs of the Journal and there
The problems with the trade manager started
in sync.

2006.01.27 11:53:35 TradeDispatcher: trade context is busy
2006.01.27 11:53:35 TradeDispatcher: trade context is busy
2006.01.27 11:53:34 TradeDispatcher: trade context is busy
2006.01.27 11:53:33 TradeDispatcher: trade context is busy
2006.01.27 11:53:33 TradeDispatcher: trade context is busy
2006.01.27 11:53:33:33 TradeDispatcher: trade context is busy
2006.01.27 11:53:32 TradeDispatcher: trade context is busy
2006.01.27 11:53:32 TradeDispatcher: trade context is busy
2006.01.27 11:53:30 TradeDispatcher: trade context is busy
2006.01.27 11:53:30 TradeDispatcher: trade context is busy
2006.01.27 11:53:28 TradeDispatcher: trade context is busy
2006.01.27 11:53:28 TradeDispatcher: trade context is busy
2006.01.27 11:53:27 11:53:27 TradeDispatcher: trade context is busy
2006.01.27 11:53:27 TradeDispatcher: trade context is busy


The logs of the second terminal are the same.
Code of Expert Advisor was not changed from the beginning (the same Expert Advisor on 10 too many pairs).

Closing block:
void CheckAndClose() { int cnt = OrdersTotal(); for (int i=0; i < cnt; i++) { OrderSelect(i, SELECT_BY_POS, MODE_TRADES); if (OrderSymbol() != Symbol()) continue; if (OrderMagicNumber() != magic) continue; if (OrderType() == OP_BUY) { OrderClose(OrderTicket(), OrderLots(), Bid, 3); } else if (OrderType() == OP_SELL) { OrderClose(OrderTicket(), OrderLots(), Ask, 3); } }



I've noticed now that the closing is performed incorrectly - from the bottom upwards but it worked well before :)
This code may warn only that it will close with terminal swearing but it will close all the same but in a slightly messy way.

 
Attempt to close orders with script gave such error 146.

Rebooting terminal helped - all orders were closed:
2006.01.27 12:08:26 '105039': order #2965450 buy 0.10 EURUSD at 1.2213 sl: 1.2123 tp: 1.2229 closed at price 1.2209<br / translate="no"> 2006.01.27 12:08:26 '105039': request in process
2006.01.27 12:08:26 '105039': request was accepted by server
2006.01.27 12:08:26 '105039': close order #2965450 buy 0.10 EURUSD at 1.2213 sl: 0.0000 tp: 0.0000 at price 1.2209
2006.01.27 12:08:22 '105039': order #2965429 buy 0.10 USDCAD at 1.1506 sl: 1.1416 tp: 1.1522 closed at price 1.1485
2006.01.27 12:08:22 '105039': request in process
2006.01.27 12:08:22 '105039': request was accepted by server
2006.01.27 12:08:21 '105039': close order #2965429 buy 0.10 USDCAD at 1.1506 sl: 0.0000 tp: 0.0000 at price 1.1485
2006.01.27 12:08:20 '105039': order #2965397 buy 0.10 EURCAD at 1.4050 sl: 1.3960 tp: 1.4066 closed at price 1.4023
2006.01.27 12:08:20 '105039': request in process
2006.01.27 12:08:20 '105039': request was accepted by server
2006.01.27 12:08:20 TradeDispatcher: trade context is busy
2006.01.27 12:08:20 '105039': close order #2965397 buy 0.10 EURCAD at 1.4050 sl: 0.0000 tp: 0.0000 at price 1.4023
2006.01.27 12:08:14 '105039': order #2965411 sell 0.10 GBPCHF at 2.2591 sl: 2.2681 tp: 2.2575 closed at price 2.2612
2006.01.27 12:08:14 '105039': request in process
2006.01.27 12:08:14 '105039': request was accepted by server
2006.01.27 12:08:14 '105039': close order #2965411 sell 0.10 GBPCHF at 2.2591 sl: 0.0000 tp: 0.0000 at price 2.2612
2006.01.27 12:08:13 '105039': order #2965408 sell 0.10 USDCHF at 1.2692 sl: 1.2782 tp: 1.2676 closed at price 1.2707
2006.01.27 12:08:13 '105039': request in process
2006.01.27 12:08:13 '105039': request was accepted by server
2006.01.27 12:08:13 TradeDispatcher: trade context is busy
2006.01.27 12:08:13 '105039': close order #2965408 sell 0.10 USDCHF at 1.2692 sl: 0.0000 tp: 0.0000 at price 1.2707
2006.01.27 12:08:11 '105039': order #2965419 buy 0.10 EURAUD at 1.6255 sl: 1.6165 tp: 1.6271 closed at price 1.6218
2006.01.27 12:08:11 '105039': request in process
2006.01.27 12:08:11 '105039': request was accepted by server
2006.01.27 12:08:11 '105039': close order #2965419 buy 0.10 EURAUD at 1.6255 sl: 0.0000 tp: 0.0000 at price 1.6218
2006.01.27 12:08:11 TradeDispatcher: trade context is busy
2006.01.27 12:08:11 '105039': order #2965441 sell 0.10 EURGBP at 0.6859 sl: 0.6949 tp: 0.6843 closed at price 0.6865
2006.01.27 12:08:11 '105039': request in process
2006.01.27 12:08:11 '105039': request was accepted by server
2006.01.27 12:08:11 '105039': close order #2965441 sell 0.10 EURGBP at 0.6859 sl: 0.0000 tp: 0.0000 at price 0.6865
2006.01.27 12:08:11 '105039': login (4.00, #28710D84)
2006.01.27 12:08:10 TradeDispatcher: trade context is busy
2006.01.27 12:08:10 PM TradeDispatcher: trade context is busy
2006.01.27 12:08:01 '105039': login (4.00, #28710D84)
2006.01.27 12:07:57 LiveUpdate: new version 4.00 build 188 is available
2006.01.27 12:07:57 '105039': login (4.00, #28710D84)


and second

2006.01.27 12:10:06 '105040': order #2965428 buy 0.10 USDCAD at 1.1506 sl: 1.1416 tp: 1.1522 closed at price 1.1484
2006.01.27 12:10:06 '105040': request in process
2006.01.27 12:10:06 '105040': request was accepted by server
2006.01.27 12:10:06 '105040': close order #2965428 buy 0.10 USDCAD at 1.1506 sl: 0.0000 tp: 0.0000 at price 1.1484
2006.01.27 12:09:46 '105040': order #2965396 buy 0.10 EURCAD at 1.4050 sl: 1.3960 tp: 1.4066 closed at price 1.4022
2006.01.27 12:09:46 '105040': request in process
2006.01.27 12:09:46 '105040': request was accepted by server
2006.01.27 12:09:46 '105040': close order #2965396 buy 0.10 EURCAD at 1.4050 sl: 0.0000 tp: 0.0000 at price 1.4022
2006.01.27 12:09:36 '105040': order #2965440 sell 0.10 EURGBP at 0.6859 sl: 0.6949 tp: 0.6843 closed at price 0.6863
2006.01.27 12:09:36 '105040': request in process
2006.01.27 12:09:36 '105040': request was accepted by server
2006.01.27 12:09:36 '105040': close order #2965440 sell 0.10 EURGBP at 0.6859 sl: 0.0000 tp: 0.0000 at price 0.6863
2006.01.27 12:09:35 '105040': order #2965423 buy 0.10 AUDUSD at 0.7520 sl: 0.7430 tp: 0.7536 closed at price 0.7525
2006.01.27 12:09:35 '105040': request in process
2006.01.27 12:09:35 '105040': request was accepted by server
2006.01.27 12:09:35 '105040': close order #2965423 buy 0.10 AUDUSD at 0.7520 sl: 0.0000 tp: 0.0000 at price 0.7525
2006.01.27 12:09:26 '105040': order #2965410 sell 0.10 GBPCHF at 2.2591 sl: 2.2681 tp: 2.2575 closed at price 2.2616
2006.01.27 12:09:26 '105040': request in process
2006.01.27 12:09:26 '105040': request was accepted by server
2006.01.27 12:09:26 '105040': close order #2965410 sell 0.10 GBPCHF at 2.2591 sl: 0.0000 tp: 0.0000 at price 2.2616
2006.01.27 12:09:25 TradeDispatcher: trade context is busy
2006.01.27 12:09:25 '105040': order #2965407 sell 0.10 USDCHF at 1.2692 sl: 1.2782 tp: 1.2676 closed at price 1.2709
2006.01.27 12:09:24 '105040': request in process
2006.01.27 12:09:24 '105040': request was accepted by server
2006.01.27 12:09:24 TradeDispatcher: trade context is busy
2006.01.27 12:09:24 TradeDispatcher: trade context is busy
2006.01.27 12:09:24 '105040': close order #2965407 sell 0.10 USDCHF at 1.2692 sl: 0.0000 tp: 0.0000 at price 1.2709
2006.01.27 12:09:23 '105040': order #2965418 buy 0.10 EURAUD at 1.6255 sl: 1.6165 tp: 1.6271 closed at price 1.6217
2006.01.27 12:09:23 '105040': request in process
2006.01.27 12:09:23 '105040': request was accepted by server
2006.01.27 12:09:23 TradeDispatcher: trade context is busy
2006.01.27 12:09:23 '105040': close order #2965418 buy 0.10 EURAUD at 1.6255 sl: 0.0000 tp: 0.0000 at price 1.6217
2006.01.27 12:09:23 TradeDispatcher: trade context is busy
2006.01.27 12:09:00 '105040': order #2965449 buy 0.10 EURUSD at 1.2213 sl: 1.2123 tp: 1.2229 closed at price 1.2209
2006.01.27 12:09:00 '105040': request in process
2006.01.27 12:09:00 '105040': request was accepted by server
2006.01.27 12:08:59 '105040': close order #2965449 buy 0.10 EURUSD at 1.2213 sl: 0.0000 tp: 0.0000 at price 1.2209
2006.01.27 12:08:59 '105040': login (4.00, #28710D84)
2006.01.27 12:08:58 TradeDispatcher: trade context is busy
2006.01.27 12:08:58 PM TradeDispatcher: trade context is busy
2006.01.27 12:08:58 TradeDispatcher: trade context is busy
2006.01.27 12:08:58 TradeDispatcher: trade context is busy
2006.01.27 12:08:40 '105040': login (4.00, #28710D84)
2006.01.27 12:08:37 LiveUpdate: new version 4.00 build 188 is available
2006.01.27 12:08:36 '105040': login (4.00, #28710D84)


Build 186 of 14.12.2005 It looks like terminals themselves froze somehow. Will have to update .
 
Great!!!
Put a checkbox in the terminal (build 188 of 17.01.06) "Autoconfiguration Data Center" , the address of the data centre, of course, is not prescribed (build 295 of 19.01.06), closed and re-started the terminal... - and the connection icon turned blue-green, that is, the terminal itself found a private (not public) datacenter. Or has the datacenter been set as a public datacenter automatically (by itself)?!!
At least the first time I installed the datacenter as a private datacenter.
How can I check in which mode the datacenter is running (private or public)?
 
I decided to check with AtGuard to see who is connecting to where. Here's a new puzzle - 8 terminals are active (4 terminals open), 3 terminals connect to external address ...222 , two terminals to address ...32 and three terminals to internal address (as I understand it). Only 7 terminals.exe fit into picture


Checked datacenter pactivity - also a surprise. Six connections , all can be seen on the picture.


Can I get a little libretto?
 
The version with the miraculous conversion of the private data centre into a public data centre has not been confirmed - this morning (maybe overnight) this terminal has turned red-green again.
 
The data centre again does not allow the missing quotes to be bumped up.
No autoconfiguration, the data centre address is prescribed.
 
"I think there's something you're not telling me, Gerasim," said Mumu and continued rowing with her oars.
Without a connection to the data centre "Update" is also not going, but I saw a new message - "Read failed".



While preparing the post (5-10 minutes) it did update, strange as it may seem.
 
As I was preparing the post (5-10 minutes) it did update, which is strange.


Maybe Alpari did something wrong? I had a similar thing yesterday on Fibo-Forex, but I don't use a DC. My connection was disconnected and restored every few seconds. I could not see any diagnostic in the log. Then everything miraculously worked. On Alpari at the same time (no DC) there were practically no problems. Two connection interruptions probably do not count.
1...45678910111213141516
New comment
Reason: