Processing chain data work unstable about ima HOT 8 CLOSED

https://github.com/skalenetwork/IMA/blob/develop/docs/SNB.md

from ima.

Not fixed: 1.3.5-beta.1
2023-02-12 05:07:25.001: SNB WORKER Full init compete for in-worker SNB server skale_observer_worker_server
2023-02-12 06:07:27.384: SNB WORKER Full init compete for in-worker SNB server skale_observer_worker_server
2023-02-12 09:08:16.794: SNB WORKER Full init compete for in-worker SNB server skale_observer_worker_server
2023-02-12 11:07:46.033: SNB WORKER Full init compete for in-worker SNB server skale_observer_worker_server
2023-02-12 12:07:49.828: SNB WORKER Full init compete for in-worker SNB server skale_observer_worker_server
2023-02-12 21:08:31.600: SNB WORKER Full init compete for in-worker SNB server skale_observer_worker_server
2023-02-13 08:09:41.705: SNB WORKER Full init compete for in-worker SNB server skale_observer_worker_server
2023-02-13 12:09:43.303: SNB WORKER Full init compete for in-worker SNB server skale_observer_worker_server

from ima.

See PR here #1463

from ima.

Add information when:

• request info(method, request ID, timestamp) for parallel SNB(didn't see request in logs)
• response in case if parallel SNB was successful or unsuccessful
• request info for single SNB request per each attempt
• response in case if single SNB was successful or unsuccessful

from ima.

Still reproducible:
IMA Agent: 2.0.0-beta.7
Can be related: https://github.com/skalenetwork/internal-support/issues/855

from ima.

Shortly: connected S-Chains are not visibe on some nodes

from ima.

IMA: 2.0.0-beta.10

from ima.

Verified: Not fixed
IMA Agent: 2.0.0-beta.10
Log below describe that only S2M transfer are working.
M2S, S2S not started on particular schain

sameProblemWithFrames.txt

from ima.