-
hyc
the memory use is irrelevant
-
hyc
6.7G of shared memory is all the DB and filesystem cache
-
hyc
it doesn't actually "need" 7GB of RAM - if you start up another process that is a memory hog, thmonerod's RAM usage will automagically decrease to make way
-
hyc
it's using that RAM because nothing else is.
-
hyc
unused RAM is wasted RAM ...
-
KnifeOfPi
hi
-
artefact
aka "what is page cache"
-
igoris
Hey, I am running monerod
-
raecarruth
great
-
igoris
It was runing fine for some time, currently node height is by 2 block behind
-
igoris
height = 2230331
-
igoris
target_height = 2230333
-
igoris
is it save to post transaction in this case, how could I bump the node to keep with the network without restarting it?
-
igoris
runing on a version v0.17.1.1
-
dEBRUYNE
igoris: Please update to v0.17.1.4 (GUI) or v0.17.1.3 (CLI)
-
dEBRUYNE
-
igoris
thanks a lot!
-
dEBRUYNE
np
-
Mochi101
I never noticed before that Kaiser Report has a couple of Magical Crypto Friends characters on the bookshelf:
youtu.be/cnfgb6WquuA?t=126
-
Mochi101
fluffypony ^^^
-
raecarruth
-
Lyza
damn, xmr.to won't even let me read their blog from the US lmao
-
Lyza
ah, yeah. saw that one. a real shame.
-
asymptotically
>We have detected that you might have accessed our site using a VPN. We have discussed our policy on VPNs in our blog
-
asymptotically
:o
-
moneromooo
In an infinite loop. Guess they want cookies. Ah, the brave new world of deputizing everyone to spy on everyone else. East Germany was just a misunderstood precocious child.
-
moneromooo
What really makes me puke is the fact close to nobody gives a shit when it's not labelled as communist.
-
Lyza
capitalist oppression? man that's called freedom
-
Lyza
j/k j/k
-
asymptotically
freedumb
-
artefact
the internet of today is just for big companies to sell product and harness user data
-
artefact
take steps against the latter, and you'll enjoy captcha hell on half the pages you load
-
yonatan1111
accidental hardfork>
-
yonatan1111
?
-
yonatan1111
some nodes running behind, by a lot
-
Mochi101
fluffypony made it onto the Kaiser Report with Max Kaiser.. I stared into his eyes pretty much the whole show because he was looking right at the camera.
-
fluffypony
lol
-
Mochi101
Did you see?
-
yonatan1111
@fluffypony it seems like some nodes are having problems at the moment, mind checking that out?
-
fluffypony
yonatan1111: best is to post actual details to #monero-dev
-
fluffypony
my node looks fine
-
Mochi101
-
Mochi101
Look on the shelf in the background.
-
fluffypony
lol nice
-
Mochi101
Those are new.
-
fluffypony
they're from MCC VR this year
-
Mochi101
I mean new as new on their set.
-
fluffypony
ah ok cool
-
Mochi101
So I'm thinking Max also likes Monero... even though he mostly shills BTC
-
Mochi101
Or maybe Stacy has the hots for you fluffypony
-
fluffypony
lol
-
rbrunner
Could it be that the so-called "asshole nodes" changed strategy and give back now a current blockheight of *2 higher* than actual, to confuse and disturb the network, or a similar nonsense?
-
rbrunner
I have both a release node and a two-week old "master" self-compiled node acting quite strangely.
-
hyc
strange how?
-
rbrunner
People over in -dev (where I currently don't have voice) also talked about some problems about 2 or 3 hours ago, for what it's worth ...
-
dEBRUYNE
Did you check your peer list rbrunner?
-
rbrunner
E.g. my master node telling me that it's 2 blocks behind, but not syncing there. Switching to the release node, that higher target height vanishes
-
dEBRUYNE
I think master doesn't have all the fixes yet
-
rbrunner
No, did not yet analyse my peers
-
rbrunner
Yeah, I am aware that master is behind, that's why I ask myself whether the strategy of those bad nodes *changed*
-
rbrunner
I guess it would be pretty confusing if they always gave back current blockchain tip as 2 higher than it is, but not delivering any blocks to get there of course
-
tobtoht
rbrunner: I have observed multiple nodes acting the same way, including one of my own (that was still running v0.17.1.1).
-
tobtoht
I've updated my node to v0.17.1.3 and it seems to be acting normal now
-
rbrunner
Splendid, more white mice running around :)
-
rbrunner
Things are pretty bad if you must have the very latest point release to have your daemons sync without problems ...
-
rbrunner
If true of course
-
tobtoht
-
tobtoht
^ all above have this issue
-
tobtoht
some are +1, while others +4
-
rbrunner
You mean they pretend they did sync higher than the "real" chain?
-
rbrunner
Or even are there, somehow?
-
tobtoht
No, they report a target height that is higher than the real height
-
rbrunner
Ah, only the target height
-
tobtoht
which causes wallet to stop synchronizing
-
tobtoht
Yes, height key is accurate
-
rbrunner
Don't see right now why wallets should stop to sync because of this. Don't they get whatever new blocks they can get from their daemon, always?
-
tobtoht
-
tobtoht
CLI might have a similar check
-
rbrunner
Uh oh ...
-
selsta
good reminder for everyone to update their node
-
rbrunner
Lol ... that's the spirit :)
-
dEBRUYNE
vikrants: One of CakeWallet's nodes is included
-
rbrunner
Not quite sure, but after a quick check I think that the CLI wallet does not have the same problem, i.e. only trying to get new blocks if the daemon feels synced
-
tobtoht
ah, good
-
selsta
tobtoht: how did you check the list of nodes?
-
selsta
they seem fine to me
-
selsta
though I only tested a couple
-
tobtoht
Compare target_height to height
-
selsta
ok you mean the higher target height
-
tobtoht
yes
-
selsta
do you have access to the .xmr.pm nodes?
-
tobtoht
I don't but I pinged dsc_
-
rbrunner
Of course afterwards you are always wiser, but that check there for "daemon is synced" looks somewhat over-eager.
-
rbrunner
So looks like with this "current blockchain height + 2" nonsense the fun with the bad nodes went up a notch :)
-
vikrants
dEBRUYNE: okie
-
vikrants
dEBRUYNE: we have pointed ours to node.xmr.to
-
kinghat[m]