Hi Arun,
Thanks for re-posting the log. I see a strange error, and can't quite explain what I see. it appears that Gemini was in some bad state during the first part of the log: while there were communication errors, the retry logic produced unexpected results, as Gemini refused to synchronize UDP communications with the driver after a number of requests. There were a number of attempts to restart the communication, but after each one, Gemini sent replies indicating errors to the driver, which resulted in yet another attempt to restart communications. This repeated many times.
After the last time (did you turn off Gemini by any chance?) it looks like communication was established properly, and no errors appeared in the log after this.?
This is strange behavior, and something I've not seen before. Does this happen often? If you get Gemini into this state again, see if turning it off and on again will resolve the errors.?
As it is, it may have been a communication error that caused the initial condition, but the recovery logic didn't seem to be able to get the communications back on track, despite multiple attempts until the last try. At that point, everything worked perfectly.
Regards,
? ? ? -Paul
Paul Kanevsky