All nodes I connect has odd timeoffset - between -100 to -60. Also I am pretty sure, that I have correct time at my node. Is there something I can do with that?
Either you need to update your clock, or everyone does. This can be caused because of clock drifting, or some other issues. Please sync your computer with an NTP server to be sure your clock is right: Google have a huge NTP server and a nice tutorial here
https://developers.google.com/time/guidesThe Raspberry has the time correctly synchronized. I started the clam node on my work PC (also synced)
Both nodes are connected to the same peer 69.121.201.75:31174, but Raspberry says "timeoffset" : -185, WorkPC says "timeoffset" : 0,
I have no idea whats wrong...
Raspberryntpdate -d time1.google.com | sed -n '$s/.*offset //p'
-0.008269 sec
cli getpeerinfo | grep timeoffset
"addr" : "67.191.63.234:31174",
"timeoffset" : -182,
(...)
Work PC (currently syncing)
ntpdate -d time1.google.com | sed -n '$s/.*offset //p'
host found : time1.google.com
0.000309 sec
"addr" : "178.62.8.78:31174",
"timeoffset" : 0,
"addr" : "67.191.63.234:31174",
"timeoffset" : -1,
"addr" : "158.69.32.10:31174",
(...)
This does not seem to be a bug in CLAM client, but a misconfiguration on your raspberry pi. Here is a link to get you started, but that's the best i can offer you as i don't have one to debug by myself:
I have some difficulties staking recently. I should obtain one coin every ~30 hours, but my last stake dates back to 2 of January 2019.
I am wondering, if something is wrong with my configuration. The wallet seems to be fine.
Just a few minutes ago I got an orphaned block... :-(
Is it normal, to wait such a long time?
Looks like you got forked from the network. To be sure, please verify the output of the command
to see if the number of the last block indexed is similar. A difference of 1 is acceptable, as the network can take a time to propagate blocks. But if the difference is bigger, then you got forked and need to resync