Wallet not connecting to any of the nodes (peer has too large time offset)

The technical support subforum.
Forum rules
Do you have trouble running Riecoin software? To integrate Riecoin software in your project? Not sure where to start for your next Riecoin project? Ask here!
Be sure to give details about your issues, and more importantly to have properly read the instructions! Do some investigation first, tell us what you have tried to do so far, show us your configuration files if applicable,...
Requests that show no effort from your side will get you a caution Image.
Post Reply
otava
Posts: 5
Joined: 2021-11-07 21:16:31

Wallet not connecting to any of the nodes (peer has too large time offset)

Post by otava »

here is the log (I sit on 1Gb optic lane)
I added all the nodes I was able to find on your page with live nodes about a week ago.


2022-04-06T07:41:28Z Riecoin Core version 22.03 (release build)
2022-04-06T07:41:28Z Qt 5.12.11 (static), plugin=windows (static)
2022-04-06T07:41:28Z Static plugins:
2022-04-06T07:41:28Z QWindowsIntegrationPlugin, version 330752
2022-04-06T07:41:28Z QWindowsVistaStylePlugin, version 330752
2022-04-06T07:41:28Z Style: windowsvista / QWindowsVistaStyle
2022-04-06T07:41:28Z System: Windows 10 (10.0), x86_64-little_endian-llp64
2022-04-06T07:41:28Z Screen: \\.\DISPLAY1 2560x1440, pixel ratio=1.0
2022-04-06T07:41:28Z Assuming ancestors of block 0531ac83b4ec8ee5699fe8cbd591ffbdaf369187fb75227449bc640a9e19dd1a have valid signatures.
2022-04-06T07:41:28Z Setting nMinimumChainWork=0000000000000000000000000000000000000f3b2ad51d094cff78ef96200000
2022-04-06T07:41:28Z Prune configured to target 953 MiB on disk for block and undo files.
2022-04-06T07:41:28Z Using the 'shani(1way,2way)' SHA256 implementation
2022-04-06T07:41:28Z Using RdSeed as additional entropy source
2022-04-06T07:41:28Z Using RdRand as an additional entropy source
2022-04-06T07:41:28Z Default data directory C:\Users\Gaming\AppData\Roaming\Riecoin
2022-04-06T07:41:28Z Using data directory D:\xxx\Riecoin
2022-04-06T07:41:28Z Config file: D:\xxx\Riecoin\riecoin.conf
2022-04-06T07:41:28Z Config file arg: addnode="174.118.153.85"
2022-04-06T07:41:28Z Config file arg: addnode="195.15.219.10"
2022-04-06T07:41:28Z Config file arg: addnode="31.164.1.54"
2022-04-06T07:41:28Z Config file arg: addnode="31.40.27.210"
2022-04-06T07:41:28Z Config file arg: addnode="47.212.210.206"
2022-04-06T07:41:28Z Config file arg: addnode="66.96.228.144"
2022-04-06T07:41:28Z Config file arg: addnode="78.192.117.13"
2022-04-06T07:41:28Z Config file arg: addnode="88.91.78.185"
2022-04-06T07:41:28Z Config file arg: addnode="147.135.86.84"
2022-04-06T07:41:28Z Config file arg: addnode="158.69.25.32"
2022-04-06T07:41:28Z Config file arg: addnode="185.140.244.246"
2022-04-06T07:41:28Z Config file arg: addnode="185.220.101.44"
2022-04-06T07:41:28Z Config file arg: addnode="195.201.104.49"
2022-04-06T07:41:28Z Config file arg: addnode="198.199.70.169"
2022-04-06T07:41:28Z Config file arg: addnode="2.86.147.248"
2022-04-06T07:41:28Z Config file arg: addnode="5.9.193.21"
2022-04-06T07:41:28Z Config file arg: addnode="51.178.184.41"
2022-04-06T07:41:28Z Config file arg: addnode="51.195.232.226"
2022-04-06T07:41:28Z Config file arg: addnode="51.81.102.216"
2022-04-06T07:41:28Z Config file arg: addnode="51.81.102.219"
2022-04-06T07:41:28Z Config file arg: addnode="51.81.102.220"
2022-04-06T07:41:28Z Config file arg: addnode="70.174.95.10"
2022-04-06T07:41:28Z Config file arg: addnode="79.147.209.121"
2022-04-06T07:41:28Z Config file arg: addnode="90.180.59.182"
2022-04-06T07:41:28Z Using at most 125 automatic connections (2048 file descriptors available)
2022-04-06T07:41:28Z GUI: "registerShutdownBlockReason: Successfully registered: Riecoin Core didn't yet exit safely…"
2022-04-06T07:41:28Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2022-04-06T07:41:28Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2022-04-06T07:41:28Z Script verification uses 11 additional threads
2022-04-06T07:41:28Z scheduler thread start
2022-04-06T07:41:28Z Using wallet directory D:\xxx\Riecoin
2022-04-06T07:41:28Z init message: Verifying wallet(s)…
2022-04-06T07:41:28Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2022-04-06T07:41:28Z Using wallet D:\xxx\Riecoin\wallet.dat
2022-04-06T07:41:28Z BerkeleyEnvironment::Open: LogDir=D:\xxx\Riecoin\database ErrorFile=D:\xxx\Riecoin\db.log
2022-04-06T07:41:28Z init message: Loading banlist…
2022-04-06T07:41:28Z SetNetworkActive: true
2022-04-06T07:41:28Z Using /16 prefix for IP bucketing
2022-04-06T07:41:28Z Cache configuration:
2022-04-06T07:41:28Z * Using 2.0 MiB for block index database
2022-04-06T07:41:28Z * Using 8.0 MiB for chain state database
2022-04-06T07:41:28Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2022-04-06T07:41:28Z init message: Loading block index…
2022-04-06T07:41:28Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2022-04-06T07:41:28Z Opening LevelDB in D:\xxx\Riecoin\blocks\index
2022-04-06T07:41:28Z Opened LevelDB successfully
2022-04-06T07:41:28Z Using obfuscation key for D:\xxx\Riecoin\blocks\index: 0000000000000000
2022-04-06T07:41:34Z LoadBlockIndexDB: last block file = 9
2022-04-06T07:41:34Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=36967, size=40234158, heights=1657385...1694356, time=2022-01-25...2022-03-30)
2022-04-06T07:41:34Z Checking all blk files are present...
2022-04-06T07:41:34Z LoadBlockIndexDB(): Block files have previously been pruned
2022-04-06T07:41:34Z Opening LevelDB in D:\xxx\Riecoin\chainstate
2022-04-06T07:41:34Z Opened LevelDB successfully
2022-04-06T07:41:34Z Using obfuscation key for D:\xxx\Riecoin\chainstate: e38589abd71b577f
2022-04-06T07:41:34Z Loaded best chain: hashBestChain=b4a0ad3b056798da9983a01e84780792806b5f459109294b3566ef7501dee17c height=1694356 date=2022-03-30T19:34:37Z progress=0.998369
2022-04-06T07:41:34Z init message: Verifying blocks…
2022-04-06T07:41:34Z Verifying last 6 blocks at level 3
2022-04-06T07:41:34Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2022-04-06T07:41:34Z No coin database inconsistencies in last 6 blocks (9 transactions)
2022-04-06T07:41:34Z block index 5955ms
2022-04-06T07:41:34Z init message: Loading wallet…
2022-04-06T07:41:34Z BerkeleyEnvironment::Open: LogDir=D:\xxx\Riecoin\database ErrorFile=D:\xxx\Riecoin\db.log
2022-04-06T07:41:34Z [default wallet] Wallet File Version = 169900
2022-04-06T07:41:34Z [default wallet] Keys: 2002 plaintext, 0 encrypted, 2002 w/ metadata, 2002 total. Unknown wallet records: 0
2022-04-06T07:41:34Z [default wallet] Wallet completed loading in 73ms
2022-04-06T07:41:34Z [default wallet] setKeyPool.size() = 2000
2022-04-06T07:41:34Z [default wallet] mapWallet.size() = 3042
2022-04-06T07:41:34Z [default wallet] m_address_book.size() = 1
2022-04-06T07:41:34Z Unsetting NODE_NETWORK on prune mode
2022-04-06T07:41:34Z init message: Pruning blockstore…
2022-04-06T07:41:34Z block tree size = 1694357
2022-04-06T07:41:34Z nBestHeight = 1694356
2022-04-06T07:41:34Z loadblk thread start
2022-04-06T07:41:34Z Imported mempool transactions from disk: 1 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2022-04-06T07:41:34Z loadblk thread exit
2022-04-06T07:41:34Z torcontrol thread start
2022-04-06T07:41:34Z Bound to 127.0.0.1:28334
2022-04-06T07:41:34Z Bound to [::]:28333
2022-04-06T07:41:34Z Bound to 0.0.0.0:28333
2022-04-06T07:41:34Z init message: Loading P2P addresses…
2022-04-06T07:41:34Z Loaded 5230 addresses from peers.dat 13ms
2022-04-06T07:41:34Z Loaded 0 addresses from "anchors.dat"
2022-04-06T07:41:34Z 0 block-relay-only anchors will be tried for connections.
2022-04-06T07:41:34Z init message: Starting network threads…
2022-04-06T07:41:34Z net thread start
2022-04-06T07:41:34Z dnsseed thread start
2022-04-06T07:41:34Z addcon thread start
2022-04-06T07:41:34Z 0 addresses found from DNS seeds
2022-04-06T07:41:34Z opencon thread start
2022-04-06T07:41:34Z msghand thread start
2022-04-06T07:41:34Z dnsseed thread exit
2022-04-06T07:41:34Z init message: Done loading
2022-04-06T07:41:34Z GUI: Platform customization: "windows"
2022-04-06T07:41:35Z peer=0 has too large time offset 16 s, disconnecting
2022-04-06T07:41:36Z peer=1 has too large time offset 16 s, disconnecting
2022-04-06T07:41:37Z peer=2 has too large time offset 16 s, disconnecting
2022-04-06T07:41:37Z peer=3 has too large time offset 16 s, disconnecting
2022-04-06T07:41:40Z peer=4 has too large time offset 16 s, disconnecting
2022-04-06T07:41:49Z peer=5 has too large time offset 16 s, disconnecting
2022-04-06T07:42:12Z peer=6 has too large time offset 15 s, disconnecting
2022-04-06T07:42:12Z peer=7 has too large time offset 16 s, disconnecting
2022-04-06T07:42:14Z peer=8 has too large time offset 16 s, disconnecting
2022-04-06T07:42:15Z peer=9 has too large time offset 15 s, disconnecting
2022-04-06T07:42:32Z peer=10 has too large time offset 15 s, disconnecting
2022-04-06T07:42:35Z peer=11 has too large time offset 16 s, disconnecting
2022-04-06T07:42:36Z peer=12 has too large time offset 15 s, disconnecting
2022-04-06T07:42:36Z peer=13 has too large time offset 16 s, disconnecting
2022-04-06T07:42:38Z peer=14 has too large time offset 15 s, disconnecting
2022-04-06T07:42:38Z peer=15 has too large time offset 16 s, disconnecting
2022-04-06T07:42:44Z peer=16 has too large time offset 16 s, disconnecting
2022-04-06T07:42:45Z peer=17 has too large time offset 16 s, disconnecting
2022-04-06T07:42:46Z peer=18 has too large time offset 16 s, disconnecting
2022-04-06T07:42:59Z peer=19 has too large time offset 16 s, disconnecting
2022-04-06T07:43:27Z peer=20 has too large time offset 16 s, disconnecting
2022-04-06T07:44:08Z peer=21 has too large time offset 16 s, disconnecting
2022-04-06T07:44:39Z peer=22 has too large time offset 16 s, disconnecting
2022-04-06T07:44:40Z peer=23 has too large time offset 16 s, disconnecting
2022-04-06T07:44:41Z peer=24 has too large time offset 16 s, disconnecting
2022-04-06T07:44:58Z peer=25 has too large time offset 16 s, disconnecting
2022-04-06T07:45:04Z peer=26 has too large time offset 16 s, disconnecting
2022-04-06T07:45:05Z peer=27 has too large time offset 15 s, disconnecting
2022-04-06T07:45:11Z peer=28 has too large time offset 15 s, disconnecting
2022-04-06T07:45:11Z peer=29 has too large time offset 16 s, disconnecting
2022-04-06T07:45:12Z peer=30 has too large time offset 16 s, disconnecting
otava
Posts: 5
Joined: 2021-11-07 21:16:31

Re: Latest wallet not connecting to any of the nodes

Post by otava »

Also I have tried to disable my antivirus - no change
User avatar
Pttn
Forum Staff
Forum Staff
Posts: 186
Joined: 2021-02-18 21:32:13
Location: Switzerland
Miner Score: 135.517
Contact:

Re: Latest wallet not connecting to any of the nodes

Post by Pttn »

As said in the Guide,
Ensure that your clock and timezone are correct! A few seconds off or a wrong timezone will cause connection issues. You can check your clock on various websites like Time.gov
According to the logs, your clock is off by about 16 s, Riecoin Core tolerates a margin of 5 s.
Adjust precisely your clock and the issue will disappear. If there is an option to synchronize your clock with the network, enable it.
Riecoin developer
Stelo.xyz pool operator
otava
Posts: 5
Joined: 2021-11-07 21:16:31

Re: Wallet not connecting to any of the nodes (peer has too large time offset)

Post by otava »

Hello Pttn and thank you for the ansewer.

I use windows 11 - probably as vas majority users time synchronization by microsoft (enabled by default).
I am not sure to what is the time compared to, but that is let's say industry standard. Imagine all the impacted users in case RIE coin gets widely adopted.
To me it looks like bug that can have serious consequences.

Best regards,
Petr
User avatar
Pttn
Forum Staff
Forum Staff
Posts: 186
Joined: 2021-02-18 21:32:13
Location: Switzerland
Miner Score: 135.517
Contact:

Re: Wallet not connecting to any of the nodes (peer has too large time offset)

Post by Pttn »

This is part of measures that prevent some blockchain attacks. Besides a confused user about that once a while, I don't see any practical issue that could cause. Before it, most of my nodes already had a 0 or 1 s offset...

And in the event Riecoin gets massively adopted, most would use a thin wallet instead, that don't require connection to nodes, like few people actually use Bitcoin Core...
Those choosing to operate a Full Node are responsible to ensure that the conditions to run it are met, that is all. And ensuring a precise clock is a very reasonable expectation in 2022.
Riecoin developer
Stelo.xyz pool operator
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests