Chrome startup error on synthetic tests

[Rob_Doce]

Hi there,

I'm running more than 10 synthetic monitors from two different locations, and almost all executions start failing everyday at the same time during several hours and stop failing at the same time. The error message is always the same: 20002 - Chrome startup error. In the execution log there is a warning message that seems to be the log related to this error: 

2022-10-24 06:01:30,947+0000 [VID:7311995685289371236] [WARN] [TAB-MANAGER] New tab could not be prepared (Error: Timeout reached, debugger is likely to stuck)

I've updated both AG to version RHEL 8.6 version and chromium to ver. 103. 

A curious fact is that during the weekend it does not give a single error. Attached is a graph of error distribution for the last 7 days.

 

Does anybody experint this kind of error before? I'm getting mad...

Cheers

Rob D.

[HannahM]

HI Rob, if you haven't already done so, can you create a Support ticket for us to check the full logs for these machines. Thanks