On Wed, Jun 14, 2017 at 08:48:30PM +0700, Vadim Yanitskiy wrote:
Neels,
What would be possible reasons for this failure,
and how can we go about fixing it?
As I know, this happens when scheduler detects, that
system time is changed. For example, it might be caused
by NTP time correction.
- Do you have NTP enabled?
yes, indeed. But I wouldn't expect that frequent changes of as much as four
seconds? We could switch off NTP ... though I enjoy having timestamps identical
to my own box's time.
- Have you specified process realtime priority?
Yep. Wait, have I? Looking up cmdlines from the log:
osmo-trx -x
osmo-bts-trx -r 1 -c [...]
At least for osmo-bts-trx I have -r 1. Do I need to do the same for osmo-trx?
No, it does so by default, right?
It seems that these failures have become less frequent again, which could
indeed be related to NTP activity. I'll switch off NTP and see if these go away
completely.
Hmm, doesn't NTP log its clock corrections somewhere? Can't find any...
Thanks Vadim!
~N