Hi Suhang,
This would indicate seosd is not able to handle messages fast enough, seoswd did not receive heartbeat of seosd in the timeout period so it killed old seosd and started new seosd.
If this would continue and impact functionality of product I suggest to open a support case where it can be further investigated.