00:33:59 <hyc> the memory use is irrelevant
00:34:12 <hyc> 6.7G of shared memory is all the DB and filesystem cache
00:35:06 <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
00:35:23 <hyc> it's using that RAM because nothing else is.
00:35:31 <hyc> unused RAM is wasted RAM ...
00:39:33 <KnifeOfPi> hi
08:57:32 <artefact> aka "what is page cache"
11:59:49 <igoris> Hey, I am running monerod
12:00:35 <raecarruth> great
12:00:40 <igoris> It was runing fine for some time, currently node height is by 2 block behind
12:00:50 <igoris> height = 2230331
12:00:56 <igoris> target_height = 2230333
12:01:24 <igoris> is it save to post transaction in this case, how could I bump the node to keep with the network without restarting it?
12:02:45 <igoris> runing on a version v0.17.1.1
12:05:24 <dEBRUYNE> igoris: Please update to v0.17.1.4 (GUI) or v0.17.1.3 (CLI)
12:05:49 <dEBRUYNE> Also, please see: https://www.reddit.com/r/Monero/comments/jrh7mv/psa_informational_thread_on_the_recently_observed/
12:14:56 <igoris> thanks a lot!
12:29:37 <dEBRUYNE> np
13:05:13 <Mochi101> I never noticed before that Kaiser Report has a couple of Magical Crypto Friends characters on the bookshelf: https://youtu.be/cnfgb6WquuA?t=126
13:05:18 <Mochi101> fluffypony ^^^
13:12:45 <raecarruth> https://test.xmr.to/blog/blogging-and-logging
13:13:54 <Lyza> damn, xmr.to won't even let me read their blog from the US lmao
13:15:17 <Lyza> ah, yeah. saw that one. a real shame.
13:17:16 <asymptotically> >We have detected that you might have accessed our site using a VPN. We have discussed our policy on VPNs in our blog
13:17:26 <asymptotically> :o
13:18:48 <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.
13:20:21 <moneromooo> What really makes me puke is the fact close to nobody gives a shit when it's not labelled as communist.
13:20:48 <Lyza> capitalist oppression? man that's called freedom
13:21:08 <Lyza> j/k j/k
13:21:14 <asymptotically> freedumb
13:47:42 <artefact> the internet of today is just for big companies to sell product and harness user data
13:48:21 <artefact> take steps against the latter, and you'll enjoy captcha hell on half the pages you load
14:08:08 <yonatan1111> accidental hardfork>
14:08:10 <yonatan1111> ?
14:08:15 <yonatan1111> some nodes running behind, by a lot
14:17:04 <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.
14:17:20 <fluffypony> lol
14:17:25 <Mochi101> Did you see?
14:18:08 <yonatan1111> @fluffypony it seems like some nodes are having problems at the moment, mind checking that out?
14:18:37 <fluffypony> yonatan1111: best is to post actual details to #monero-dev
14:18:40 <fluffypony> my node looks fine
14:19:37 <Mochi101> fluffypony, did you see? https://www.youtube.com/watch?v=cnfgb6WquuA&t=126
14:19:43 <Mochi101> Look on the shelf in the background.
14:19:50 <fluffypony> lol nice
14:20:35 <Mochi101> Those are new.
14:20:52 <fluffypony> they're from MCC VR this year
14:21:16 <Mochi101> I mean new as new on their set.
14:21:42 <fluffypony> ah ok cool
14:22:12 <Mochi101> So I'm thinking Max also likes Monero... even though he mostly shills BTC
14:22:45 <Mochi101> Or maybe Stacy has the hots for you fluffypony
14:23:24 <fluffypony> lol
16:19:45 <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?
16:20:35 <rbrunner> I have both a release node and a two-week old "master" self-compiled node acting quite strangely.
16:21:06 <hyc> strange how?
16:21:11 <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 ...
16:21:40 <dEBRUYNE> Did you check your peer list rbrunner?
16:21:52 <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
16:22:07 <dEBRUYNE> I think master doesn't have all the fixes yet
16:22:13 <rbrunner> No, did not yet analyse my peers
16:22:46 <rbrunner> Yeah, I am aware that master is behind, that's why I ask myself whether the strategy of those bad nodes *changed*
16:23:34 <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
16:24:00 <tobtoht> rbrunner: I have observed multiple nodes acting the same way, including one of my own (that was still running v0.17.1.1).
16:24:27 <tobtoht> I've updated my node to v0.17.1.3 and it seems to be acting normal now
16:24:32 <rbrunner> Splendid, more white mice running around :)
16:26:15 <rbrunner> Things are pretty bad if you must have the very latest point release to have your daemons sync without problems ...
16:26:37 <rbrunner> If true of course
16:28:10 <tobtoht> http://eu-west.node.xmr.pm:18089/get_info http://eu-west-2.node.xmr.pm:18089/get_info http://usa-east-va.node.xmr.pm:18089/get_info http://canada.node.xmr.pm:18089/get_info http://singapore.node.xmr.pm:18089/get_info http://nodes.hashvault.pro:18081/get_info http://xmr-node-eu.cakewallet.com:18081/get_info http://xmr-node-usa-east.cakewallet.com:18081/get_info http://node.xmr.pt:18081/get_info http://node.xmr.ru:18081/get_info
16:28:15 <tobtoht> ^ all above have this issue
16:28:28 <tobtoht> some are +1, while others +4
16:29:09 <rbrunner> You mean they pretend they did sync higher than the "real" chain?
16:29:28 <rbrunner> Or even are there, somehow?
16:29:47 <tobtoht> No, they report a target height that is higher than the real height
16:29:57 <rbrunner> Ah, only the target height
16:29:57 <tobtoht> which causes wallet to stop synchronizing
16:30:19 <tobtoht> Yes, height key is accurate
16:31:39 <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?
16:31:46 <tobtoht> Or, GUI at least: https://github.com/monero-project/monero/blob/master/src/wallet/api/wallet.cpp#L2171
16:31:51 <tobtoht> CLI might have a similar check
16:32:26 <rbrunner> Uh oh ...
16:33:58 <selsta> good reminder for everyone to update their node
16:34:13 <rbrunner> Lol ... that's the spirit :)
16:40:07 <dEBRUYNE> vikrants: One of CakeWallet's nodes is included
16:41:57 <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
16:42:37 <tobtoht> ah, good
16:42:49 <selsta> tobtoht: how did you check the list of nodes?
16:43:05 <selsta> they seem fine to me
16:43:21 <selsta> though I only tested a couple
16:43:29 <tobtoht> Compare target_height to height
16:43:53 <selsta> ok you mean the higher target height
16:44:00 <tobtoht> yes
16:44:07 <selsta> do you have access to the .xmr.pm nodes?
16:44:19 <tobtoht> I don't but I pinged dsc_
16:56:15 <rbrunner> Of course afterwards you are always wiser, but that check there for "daemon is synced" looks somewhat over-eager.
16:57:45 <rbrunner> So looks like with this "current blockchain height + 2" nonsense the fun with the bad nodes went up a notch :)
17:29:41 <vikrants> dEBRUYNE: okie
17:31:50 <vikrants> dEBRUYNE: we have pointed ours to node.xmr.to
19:42:13 <kinghat[m]> https://gitbackup.org/#/