Hi All In our testing of new connman (version 1.29) we do see following error print sometimes (This is happening very rarely and I do not have any easy way to reproduce it at will):
"2015-07-17 01:35:20.000000 daemon.err connmand[321]: Invalid packet timestamp from time server" After this print we see that we are not able to communicate to connman at all. All the DBUS messages to connman are timing out. The only way to recover from this situation is to restart the connman. Looking into the code in ntp.c, this piece of code looks completely benign and I am not able to correlate this print with the failure that I see. But in all the three instances (over last one month) whenever we see this print. we find that connman is completely unresponsive. Has anyone else seen similar problem? Regards Naveen _______________________________________________ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
