Sérgio Lopes Marques

Hi Mohan, I have tested your patch in my scenario and it works. The invalid sync ctcx messages are not being registered anymore. Thanks

Hi Alex. This last patch also works in my setup. Many Thanks

Hi Alex, Thanks a lot for your help. I continue to reproduce the problem. I am using a system with an opensaf cluster that has 2 controllers and 4 of 20 possible payloads. Than with the help of a ruby script I am always rebooting randomly one of the controller boards, waiting for the just rebooted board to come up and then randomly rebooting again one of the controller boards and so on… After some dozens of reboots the problem appears. Thanks again and regards,

Hi Alex, Thanks a lot for your help. I continue to reproduce the problem. I am using a system with an opensaf cluster that has 2 controllers and 4 of 20 possible payloads. Than with the help of a ruby script I am always rebooting randomly one of the controller boards, waiting for the just rebooted board to come up and then randomly rebooting again one of the controller boards and so on… After some dozens of reboots the problem appears. Bellow you can find the logs. Thanks again and regards,

Hi Alex, It's working! Many thanks

Hi Alex, Thanks a lot for your help. I continue to reproduce the problem. I am using a system with an opensaf cluster that has 2 controllers and 4 of 20 possible payloads. Than with the help of a ruby script I am always rebooting randomly one of the controller boards, waiting for the just rebooted board to come up and then randomly rebooting again one of the controller boards and so on… After some dozens of reboots the problem appears. Bellow you can find the logs. Thanks again and regards, <143>1...

Many thanks for your help. You can find in attach the traces requested. Please don’t hesitate to contact me in case you need something more. Thanks again