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

New comment
 
Yeah... You have to be an enthusiast to use a DT. Found several gaps on all Alpari currency pairs today. At 21-15 and after zero hour server time. Didn't realise right away that there was no war overnight.



I started trying to update the missing quotes - it's clear that the data centre does not care about all of my pushes to "Update".
So the phrase "for cooperating traders" is a bit bold, though.
It is a little bit easier to work without DTz, at least it does not provide one more "weakest link", which is a black box and has no identification marks, except for three types of status messages
"Started", "Stopped" and "Unknown". The logs themselves don't provide any information to me, except that they try to log in sometimes and make a livapdate when it's no longer needed.
I can not imagine variants of using DTs except one - for each independent channel one DT for each broker and account type (demo and real). If you have two communication channels (cable internet and XDSL), two quotation providers and one real and one demo account - then you need 2x2x2 data centres.
 
Without a datacenter, I couldn't get the holes taped on one of the accounts either. No matter how many times I overloaded MT4 - it always takes 2 bars each. Alpari server. "Updating" comes from the same source, but the result is different. I can of course achieve synchronisation if I wish (by rebooting the comp, terminals, rewriting history from one folder to another), but not in an intuitive way.



Breaks:
 
Just in case, logs of two terminals running through dc:
one
2005.11.29 18:04:18 '105040': login (4.00, #2841B56A)<br / translate="no"> 2005.11.29 18:03:48 '105040': DataCenter connecting failed [6]
2005.11.29 18:03:45 '105040': login (4.00, #2841B56A)
2005.11.29 18:03:06 PM HistoryCenter: 14999 bars imported in 'GBPUSD15'
2005.11.29 18:02:36 '105040': login (4.00, #2841B56A)
2005.11.29 18:02:35 PM HistoryCenter: synchronize 'GBPUSD15'
2005.11.29 18:00:13 Custom indicator EZZ GBPUSD,M15: removed
2005.11.29 17:13:07 '105040': login (4.00, #2841B56A)
2005.11.29 17:11:41 '105040': DataCenter connecting failed [6]
2005.11.29 16:13:35 '105040': login (4.00, #2841B56A)
2005.11.29 16:13:33 '105040': login (4.00, #2841B56A)
2005.11.29 14:11:10 '105040': login (4.00, #2841B56A)
2005.11.29 14:10:20 '105040': DataCenter connecting failed [6]
2005.11.29 14:10:17 '105040': login (4.00, #2841B56A)


second
2005.11.29 18:04:21 '105039': login (4.00, #2841B56A)
2005.11.29 18:03:50 '105039': DataCenter connecting failed [6]
2005.11.29 18:03:30 '105039': login (4.00, #2841B56A)
2005.11.29 18:03:28 '105039': login (4.00, #2841B56A)
2005.11.29 17:13:07 '105039': login (4.00, #2841B56A)
2005.11.29 17:11:41 '105039': DataCenter connecting failed [6]
2005.11.29 16:13:38 '105039': login (4.00, #2841B56A)
2005.11.29 16:13:35 '105039': login (4.00, #2841B56A)
2005.11.29 16:13:26 '105039': login (4.00, #2841B56A)
2005.11.29 14:28:08 '105039': login (4.00, #2841B56A)
2005.11.29 14:28:06 '105039': login (4.00, #2841B56A)
2005.11.29 14:11:12 '105039': login (4.00, #2841B56A)
2005.11.29 14:10:22 '105039': DataCenter connecting failed [6]
2005.11.29 14:10:19 '105039': login (4.00, #2841B56A)
2005.11.29 14:09:22 '105039': connect failed [6]
2005.11.29 13:32:05 '105039': login (4.00, #2841B56A)
2005.11.29 13:32:02 '105039': login (4.00, #2841B56A)


on these terminals the Expert Advisors wake up only in the evening

The third log is from the terminal working directly:
2005.11.29 18:32:08 '117245': login (4.00, #2841B56A)
2005.11.29 18:03:45 '117245': login (4.00, #2841B56A)
2005.11.29 18:03:30 PM HistoryCenter: 2 bars imported in 'GBPUSD15'
2005.11.29 18:03:30 '117245': login (4.00, #2841B56A)
2005.11.29 18:03:05 PM HistoryCenter: synchronize 'GBPUSD15'
2005.11.29 18:02:23 PM HistoryCenter: synchronize 'GBPUSD15'
2005.11.29 18:00:59 HistoryCenter: 15034 bars imported into 'GBPUSD15'
2005.11.29 18:00:55 '117245': login (4.00, #2841B56A)
2005.11.29 18:00:51 HistoryCenter: synchronize 'GBPUSD15'
2005.11.29 17:39:11 Mail: 'NRTR v3' has been sent
2005.11.29 17:37:14 '117245': login (4.00, #2841B56A)
2005.11.29 16:16:21 Mail: 'NRTR v3' has been sent
2005.11.29 16:01:19 Mail: 'NRTR v3' has been sent
2005.11.29 15:31:36 Mail: 'NRTR v3' has been sent
2005.11.29 15:17:32 Mail: 'NRTR v3' has been sent




The origin of error 6 is unclear when working through DC, while there is no such error directly.
 
The DC attempts to connect to the server at reasonable intervals:
0 sec - the first time
10 sec - after 1 first failure
20 sec - after 18 failures
30 sec - after 24
The moment the DC itself fails to connect to the main server, it does not allow anyone to connect to it. Hence "DataCenter connecting failed [6]".
 
I came to the conclusion that there is a difference between the absence of quotes in the terminals on 21.11 and 29.11.05.
During the period between 18.11 and 21.11 the quotes were received and stored in the database, but the terminals could not receive them (the terminals could not access the data center until I manually pressed "Update" in one of the terminals - then the other two terminals automatically contacted the data centre). After restoring the connection between terminals and dc, everything started to work as if nothing had happened.
On 29.11 (i.e. yesterday) the datacenter failed to connect (either because there was no internet or some other reason) and all attempts to obtain new quotes through the datacenter failed. Moreover, in one of the terminals "hole" databases had a mark of "validity", as a result I was not able to update the databases directly. I had to just tear down the 15-minute databases for all currency pairs and pump them up manually to the maximum depth. I should make some kind of script for this case, it's tiring to do it manually.
 
He deleted something (build 285)
<br / translate="no"> 05:44:15 195.135.1.3: '105039' login [ver: 400.186]
05:44:22 195.135.1.3: '105040' login [ver: 400.186]
07:08:03 195.135.1.3: '105039' login [ver: 400.186]
07:08:04 195.135.1.3: '105040' login [ver: 400.186]
09:45:39 Datafeed: thread terminated
09:45:41 Exit: server deleted
09:45:41 Exit: data feeder deleted
09:45:41 Exit: LiveUpdate base deleted
09:45:41 Exit: news base deleted
09:45:41 Exit: ip base deleted
09:45:41 Exit: securities deleted
09:45:41 Exit: history center deleted
09:45:41 Exit: finished
09:45:41 Exit: finished
 
Something he deleted (build 285)<br / translate="no">

05:44:15 195.135.1.3: '105039' login [ver: 400.186]
05:44:22 195.135.1.3: '105040' login [ver: 400.186]
07:08:03 195.135.1.3: '105039' login [ver: 400.186]
07:08:04 195.135.1.3: '105040' login [ver: 400.186]
09:45:39 Datafeed: thread terminated
09:45:41 Exit: server deleted
09:45:41 Exit: data feeder deleted
09:45:41 Exit: LiveUpdate base deleted
09:45:41 Exit: news base deleted
09:45:41 Exit: ip base deleted
09:45:41 Exit: securities deleted
09:45:41 Exit: history center deleted
09:45:41 Exit: finished
09:45:41 Exit: finished

It's just a message to delete objects from memory.
 
Speaking of birds. Are the logs written in GMT time zone ?
Because I have Moscow time on my computer, logs are written by MTS-3 hours, Alpari servers go to MSC-2 hours.
 
Hooked a fourth terminal to the data centre. Flight is OK, need additional memory on computer, not enough:)
 
Added memory, now you can hang five more terminals, not enough monitors :)
1234567891011121314...16
New comment
Reason: