Following up from the previous answer, I'm not so sure it's related to the server's time. If the problem persists, we would request that you stop the node, zip up the blockchain directory, and send it to multichain dot debug at gmail dot com, so we can take a detailed look. The debug.log file is most likely to contain the clue but it helps to have the whole thing.