Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

untrusted stratum value for TrueTime: 0 ? #125

Open
ZimM-LostPolygon opened this issue Dec 26, 2019 · 1 comment
Open

untrusted stratum value for TrueTime: 0 ? #125

ZimM-LostPolygon opened this issue Dec 26, 2019 · 1 comment

Comments

@ZimM-LostPolygon
Copy link

No idea what triggers it, but occasionally, TrueTimeRx fails to initialize with a untrusted stratum value for TrueTime: 0. I am using the pool.ntp.org pool.

After a few hours, the issue just goes away, but it's usually back soon enough. Looking at the logs, my guess about what happens is that TrueTimeRx only does requests to a single server (193.70.94.182 in this case) again and again, even though it is misbehaving. Perhaps it would be better to retry with a different server instead of wasting all attempts on a single one?

Code I use:

mTrueTime =
	TrueTimeRx
		.build()
		.withLoggingEnabled(true)
		.withConnectionTimeout(15 * 1000)
		.withServerResponseDelayMax(1000)
		.withRootDispersionMax(1500)
		.withRootDelayMax(1500)
		.withSharedPreferencesCache(context);
mTrueTime
	.initializeRx("pool.ntp.org")
	.subscribeOn(Schedulers.io())
	.subscribe(...)

Full log: log.txt

@mice777
Copy link

mice777 commented May 12, 2023

Another source indicates that value 0 is valid (= Unspecified or Unavailable)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants