Hi,
You are receiving EVENT_RX_FAIL_GO_TO_SEARCH twice, but they are two separate instances.
Your log shows that you have a syncronized channel that is receiving (Message ID 0x4E). Then you receive 7 consecutive EVENT_RX_FAIL messages which causes your channel to loose synchronization and drop to search. After your search timeout has occurred, the channel is autmatically closed, so you receive a response no error to your channel closed message. Then, you send a reset command which puts the wheels in motion to re-open your channel.
Then, your channel finds a matching master, synchronizes with it for a short time, and the same scenario happens again. It receives 7 EVENT_RX_FAIL messages then subsequently drops to search, evident from the EVENT_RX_FAIL_GO_TO_SEARCH.
The logs you provided are perfectly normal. Because your channel dropped to search twice, you will receive an EVENT_RX_FAIL_GO_TO_SEARCH twice. If your intention is not to re-open the channel after it has been closed, I suggest taking a look at the code you are using and handling the event more appropriately.
Cheers,
Kassandra