Very simply, every 1 second Ignition runs a task that checks the time. It expects it to be more or less one second since the last time. If not, it prints this. It annoys and confuses many people, but is still an extremely useful tool for detecting problems, since timing is important to many aspects of Ignition, especially networking components.
This message is showing that what should have been a 1 second gap is actually 13.5 seconds. There are essentially 3 things that could be happening:
[ul][li]The system is overloaded and everything is running slowly.[/li]
[li]This was a one time pause/delay, or at least not regular. Something like a big garbage collection event.[/li]
[li]The clock on the machine was synchronized and was pushed forward[/li][/ul]
Given what you’ve said about the system, I don’t think it’s the first two in this case. A total memory allowance of 2gb wouldn’t be big enough to case a delay in cleanup, I think. And it doesn’t sound like the system is generally overwhelmed.
That would leave the idea that the clock is generally running slowly, and then the system is synchronizing and changing it. The best support for this idea would be to look at how often this message is happening, and how similar the reported differences are.
How often is this message occurring? Can you maybe post the most recent wrapper.log file, or at least look at the last few messages and post the details? If this turns out to be the case, you can confirm it by turning off the clock synchronization temporarily, but then I think the best solution is to actually speed it up (synchronize more frequently) so that the difference doesn’t grow to be so large.