META TESTER 5 Cloud Network — Agents disconnected and unable to self reconnect - page 2

New comment
 
Fxrobustix #:
Now that the schedule values are clarified, I would stop editing common.ini manually and reproduce the problem once from a clean Agent Manager configuration. Compare the affected machine and the working laptop at the same time, recording build number, DNS resolution, outbound connection attempts and exact UTC timestamps. If the laptop connects while the workstation sends no outbound request, that points more to local agent state than the ISP. Can you post one fresh Manager log from startup until the first failed connection attempt?

Here's a fresh log from the workstation (build 6140, currently connected and working fine — 44/44 agents, receiving cloud passes normally):

CS      0       03:26:07.884    Startup MetaTester 5 build 6140, 21 Aug 2026
CS      0       03:26:07.884    Startup Windows 10 build 19042, 88 x Intel Xeon  E5-2699 v4 @ 2.20GHz, AVX2, 136 / 191 Gb memory, 150 / 464 Gb disk, UAC, admin, GMT+7
CS      0       03:26:07.892    Startup MQL5 account: XXXXXXXX, cloud network mode is on
CS      0       03:26:07.893    Startup initialization finished
CS      0       03:59:16.242    Startup MetaTester 5 build 6140, 21 Aug 2026
CS      0       03:59:16.243    Startup Windows 10 build 19042, 88 x Intel Xeon  E5-2699 v4 @ 2.20GHz, AVX2, 134 / 191 Gb memory, 164 / 464 Gb disk, UAC, admin, GMT+7
CS      0       03:59:16.253    Startup MQL5 account: XXXXXXXX, cloud network mode is on
CS      0       03:59:16.253    Startup initialization finished
CS      0       03:59:29.285    Startup MetaTester 5 build 6140, 21 Aug 2026
CS      0       03:59:29.286    Startup Windows 10 build 19042, 88 x Intel Xeon  E5-2699 v4 @ 2.20GHz, AVX2, 134 / 191 Gb memory, 164 / 464 Gb disk, UAC, admin, GMT+7
CS      0       03:59:29.295    Startup MQL5 account: XXXXXXXX, cloud network mode is on
CS      0       03:59:29.295    Startup initialization finished
CS      0       09:21:31.418    Startup MetaTester 5 build 6140, 21 Aug 2026
CS      0       09:21:31.419    Startup Windows 10 build 19042, 88 x Intel Xeon  E5-2699 v4 @ 2.20GHz, AVX2, 121 / 191 Gb memory, 195 / 464 Gb disk, UAC, admin, GMT+7
CS      0       09:21:31.427    Startup MQL5 account: XXXXXXXX, cloud network mode is on
CS      0       09:21:31.427    Startup initialization finished
CS      0       17:35:27.159    Startup MetaTester 5 build 6140, 21 Aug 2026
CS      0       17:35:27.160    Startup Windows 10 build 19042, 88 x Intel Xeon  E5-2699 v4 @ 2.20GHz, AVX2, 132 / 191 Gb memory, 211 / 464 Gb disk, UAC, admin, GMT+7
CS      0       17:35:27.169    Startup MQL5 account: XXXXXXXX, cloud network mode is on
CS      0       17:35:27.169    Startup initialization finished

Important context: the machine itself was never rebooted or manually restarted at any point during this window. It has been running continuously. So these 5 "Startup" entries are the manager process restarting on its own, not the OS restarting.

Two observations:

  1. No connection-state lines at all. Every entry stops at "initialization finished" — there is never a "Connecting", "Connected", "Registered", or "Failed" line logged afterward, even though the machine is actively connected and processing cloud passes right now. So the manager log by itself cannot be used to determine connection status — build 6140 apparently doesn't log the cloud handshake at all, which makes diagnosing silent failures much harder.
  2. Restart #2 → #3 is only 13 seconds apart (03:59:16 → 03:59:29), while the other gaps (33 min, 5h22, 8h14) are unexplained given that nothing on my end triggered them — no reboot, no manual relaunch, no Windows update that I'm aware of. Since the machine wasn't restarted, these look like the manager process itself crashing or being stopped and relaunched — possibly by a Windows service supervisor — without any error being logged.

Given point 1, would it be possible to get a build that logs the actual cloud connection attempt/result (TLS handshake, registration accepted/rejected, schedule acknowledged)? And regarding point 2 — is there a separate crash/event log for the manager process that would show why it restarted 5 times in one day with no user action?

 
the cloud server connection just stopped. 44 cores disconnected , but the laptop is still connected and make passes. So basically it is not only the ISP, or something very special about the ISP. Why the workstation dont run and its locked and laptop fully ok ?
tcp 443 indicate a normal ping at 45ms.
Not a single change of IP

here is the log of the workstation:


CS      0       17:35:27.169    Startup MQL5 account: xxxxxxx, cloud network mode is on
CS      0       17:35:27.169    Startup initialization finished
CS      0       18:09:10.545    Startup MetaTester 5 build 6140, 21 Aug 2026
CS      0       18:09:10.546    Startup Windows 10 build 19042, 88 x Intel Xeon  E5-2699 v4 @ 2.20GHz, AVX2, 114 / 191 Gb memory, 246 / 464 Gb disk, UAC, admin, GMT+7
CS      0       18:09:10.553    Startup MQL5 account: xxxxxxxx, cloud network mode is on
CS      0       18:09:10.553    Startup initialization finished
CS      0       19:22:35.323    Startup MetaTester 5 build 6140, 21 Aug 2026
CS      0       19:22:35.324    Startup Windows 10 build 19042, 88 x Intel Xeon  E5-2699 v4 @ 2.20GHz, AVX2, 92 / 191 Gb memory, 239 / 464 Gb disk, UAC, admin, GMT+7
CS      0       19:22:35.336    Startup MQL5 account: xxxxxx, cloud network mode is on
CS      0       19:22:35.336    Startup initialization finished
CS      0       22:30:38.203    Startup MetaTester 5 build 6140, 21 Aug 2026
CS      0       22:30:38.204    Startup Windows 10 build 19042, 88 x Intel Xeon  E5-2699 v4 @ 2.20GHz, AVX2, 176 / 191 Gb memory, 271 / 464 Gb disk, UAC, admin, GMT+7
CS      0       22:30:38.212    Startup MQL5 account: xxxxxxx, cloud network mode is on
CS      0       22:30:38.212    Startup initialization finished
12
New comment