MetaAppender logger

[steveFuturePerfect]

MetaAppender logger

[jonbartels]

Cross linking to question in odoodo/Mirth-MetaAppender#4

How are you running Mirth? Locally? Container? VM?

Both errors relate to clock drift. Both the pooler and the scheduler would be sensitive to thinks like the computer sleeping.

[steveFuturePerfect]

My Mirth Connect instances are run locally and on remote servers, both displaying the mentioned logged messages.

As its only a warning, nothing too much too worry about?

[jonbartels]

Clock drift usually only happens when a physical computer is put to sleep or if a container/VM is paused. If there are not sleeps, pauses, etc. then I would not ignore these warnings. The warnings are telling you a time-sensitive operation failed or was reset after clock drift was detected.

Possible causes of clock drift WITHOUT a sleep or pause could be:

• poor time sync (are you running NTP to maintain system time?)
• extremely high CPU load

I suspect that you've had the warnings happening for a long time but the MetaAppender made it easier to see the errors. That is a good thing. That is what the Meta Appender does for its users!

[steveFuturePerfect]

Thanks Jon,

That may very well be the case. I'm going to have to accept the intrusion of these messages in the logs

Thanks for your help anyway

Steve