shinohai: Being that ViaBTC mined it, I'm surprised block not empty
adlai: iirc, "prb" was poweranger, not publicrelations
mod6: asciilifeform: yeah, my node seems to be 'blackholed' at the moment. investigating before a restart here.
mod6: as to your thought on debugging, will think on it.
mod6: while I'm at it, did anyone try out those three new vpatches? I've been running with them just fine on test nodes.
snsabot: (trilema) 2019-12-26 mp_en_viaje: in other housekeeping, hey diana_coman lobbes wouldja mind taking alf's derpy alt-bitcoinwizards off the loggers header list ?
curiousd0g: "He who comes to us with a turd, by the turd shall perish."
mod6: asciilifeform: my log looks like your log. will provide if you really want to see tho.
shinohai: mod6: I hopefully can try 'em this weekend, it got put on back burner last weekend had a sick concubine to care for.
mod6: no worries shinohai
mod6: but do let me know if/when they work for ya.
mod6: yeah, i mean, getting blackholed is nothing new. seems like what it is. that's what I would have thought if no one would have said anything.
mod6: i guess generally speaking, if i let this just figure itself out, it usually does. just may take some time. hours usually.
mod6: I think I'm going to restart my main node. And I'm gonna leave my test node in this state. See what happens.
mod6: LoadBlockIndex(): hashBestChain=0000000000000000000358b1f55d0fa15d185693974f0fa1dc3249109151f2b0 height=618405
mod6: So yah, had 618405, was waiting for, or trying to digest 618406
mod6: SetBestChain: new best=0000000000000000000686f8b07d684d9950f9b017ae1d9774de18c861ccb095 height=618413 work=3994228844468425383327109680
mod6: ploughing right back up.
mod6: i saw the discussion before about txs that sit, often 0 fee. you mean like that?
mod6: time out after 2 weeks.
mod6: maybe so. i'd like to get to the bottom of this weird issue. i kinda see it from time to time. maybe not as broadly impacting as this one tho.
mod6: heck, i see this kinda thing ... often. log looks just like it does (where I pasted above). thing doesn't respond to RPC commands.
mod6: often tho, just seems to sort itself out after some time.
mod6: i mean, more than since '18, sure. I typically think of these as 'blackholed'. I don't block ips quite like as encouraged on this one particular node. although, i should.
mod6: but i kinda like it to be beaten harder. per-se.
mod6: right. usually by the time I see it too, it's already been going on for a bit. hard to pinpoint.
mod6: never saw this thing since 18 with dulap?
mod6: hm. see I don't think it has anything to do with the block. which is why I try to stay away from 'wedged', unlike the other circumstances where we've said 'wedged'. i forget the block numbers off hand.
mod6: there've been a couple of cases where we've all been digging to figure out what the issue was.
mod6: could be a heathen command tho. your dumping the cmds idea could be a helpful tool here.
superkuh: Fucking apple. Setting their browser to declare any TLS cert with a lifetime of greater than a year to be invalid. Corps gonna corp.
superkuh: But I do see apple users in my site logs.
superkuh: And they'll be gone now. Not a huge loss given apple users, but still.
mod6: asciilifeform: well 'magic turd' in there. what have you.
mod6: i guess i'd be surprised if that was the problem, a 'magic turd'.
mod6: perhaps, yeah, could be some sort of weird dead-lock.
mod6: same. this seems to be something more rare. like I said, I don't see it all the time. but certainly not years between either.
mod6: (could just be my noad too, fwiw, doing something weird)
mod6: now there's a helpful thing too. not sure I'd do it 2h's but, yeah, perhaps some interval.
mod6: (im up to 618529 nao)
mod6: yeah, my test node is still derping. will write in when it recovers. won't wait forever, but may wait a few days to see.
snsabot: Logged on 2020-02-22 11:15:24 asciilifeform: wonder how long until they notice.
mod6: its possible that 406 just took a long time to verify for some reason, which causes a cascade of other issues that render it derped for a bit.
mod6: yeah, fair enough, once restarted, verified very quickly.
mod6: yeah, i get that too. this seems like it might be 1 problem or perhaps more likely a confluence of issues that build up at the right time. i'd rather fix that shit, than give it a pill.
mod6: only way to find out, really, is just to debug and wait for the issue to arise, then disect.
mod6: well, once one has an idea of wtf, then yes, can reproduce at will. otherwise, tilt at windmills.
mod6: to >1 trb node, this could be true.
BingoBoingo has trb node 143.202.160.10:8333 sitting at blockheight 618530 at present, but sits on version string 70001
BingoBoingo: asciilifeform: Just version string. It's the rotor/stator recipe baked to give the nameservers something to do with their cycles.
BingoBoingo: I don't recall if I included dumpblock in the press, Will see if I can get anything interesting out of the logs.
mod6: hmm. ok. keep an eye on it. im on 618530
mod6: which now, looks like a few blocks behind. 618532 has been announced a few minutes ago.
BingoBoingo: mod6: Which version flag is your node flying and does it sit on port 8333?
mod6: I took it offline a minute ago tho.
snsabot: Logged on 2020-02-18 19:31:19 asciilifeform: verisimilitude:
this one ?
mod6: Will restart it in a minute.
adlai intended to link a different line from that same conversation, although there is no need for a correction since the conversation should probably be read along with the article
adlai rarely has any disagreement with asciilifeform, and in this case, no objections to your objections !
adlai: especially, the bit about lispers not caring even one byte specifier about style
adlai: the word 'lispers' here refers to those who actually have to write and maintain the code; managers of teams of programmers are likely to care quite a bit about the optics.
adlai: consistent styling also leads to fingerprinting.
adlai: verisimilitude: thank you for the reminder about using loop keywords from the keyword package. this is a habit that i have yet to adopt, although i probably should.
adlai: fingerprinting, i.e. "this code smells like nakamoto"
adlai: you probably work very few net meters of cardboard/cement/etc from cubefarms were people scrub signatures before deploying code.
adlai: possibly even forging signatures and fingerprints to implicate their false flag of choice.
adlai: my guess is that it's much more fun, in the long run, to be able to claim your work as your own, and the suffering anons who can't, gotta console themselves with... dunno, salaries? conference chicken? etc
verisimilitude: I wrote my style document, because a fellow in my group wanted to read some, and I was lacking writing ideas.
verisimilitude: I neither expect to see nor care if anyone uses my style described therein.
adlai: eh, nobody cares about centrifuges anymore; these days the cool kids are all about that other kind of 'TMSR'
verisimilitude: With no disrespect, adlai, I'm not particularly interested in changing my writing style so. I strive to avoid some circumlocution in my writing, but I'd rather not use headers and whatnot. I write for a very particular constraint, which would've been obvious if you'd seen the document before it was converted to HTML, and I'm uncertain if you'd.
adlai: lemme put it this way: your style guide seems written for recitation to students, rather than quick glances by a working programmer
verisimilitude: That's a good point; I suppose it's not written for quick glances, no.
adlai: (and there is no problem with this! provided that you can find any students who still want to learn lisp...)
adlai: In other news, I do often wonder as to just how amazingly accurate asciilifeform was in once calling the people treating mp, dc, et al as their 21st century Elizae the 'patients'
adlai: also, congratulations are in order for BingoBoingo, both for the birthday, and apparently for turning #ossasepia into another chapter of AA!
shinohai: Except step 3 isn't "God as you understand him" but "thou shalt have no other deity sans MP".
snsabot: Logged on 2020-02-22 12:11:40 asciilifeform: adlai: hm?
adlai: shinohai: nonononono; "thou shalt have no other used car salesman but pete"
shinohai: pete_d has pretty nice cars, I'd deffo but his shared Lotus if it isn't too ragged out.
adlai: asciilifeform: well, mp claimed in one of the bits of legalese about "bitcoin as game currency, mpex as recursive game" that he's insane; yet look at that parade of 'normal' folks, just lining up to have him and his cohort set them straight about their troubles. it's almost as though the crazy are sane, and the sane -- crazy!
adlai goes back to eating oxford's ru-en+en-ru via retina
mod6: Node is back up, on block 618539
adlai: regrettably their idea of "dictionary" is almost entirely devoid of grammatical reference, so recommendations of particularly good summaries of the usage (either online or in print) would be much appreciated
adlai meanwhile starts crawling thru wiktionary
mod6: So, ok, restarted my node yet again. This time in debug=true mode.
mod6: Was caught up, now fell behind. Here's something that ~might~ be of interest...
mod6: that address 138.197.207.236 is always getting disconnected directly after the flood control message -- a number of times in my 12Gb debug.log file.
mod6: anyone turn anything else up from that IP that looks "interesting"?
mod6:
http://paste.deedbot.org/?id=l08E << Here's a grep of my log for that IP 4 lines before and after found. Might be just a version 70013 trying to sync. Timing seems odd to that flood control though.
mod6: Found basically ~same thing on test node with regard to behavior. Different IP's syncing. This time tho, 122 of the 'getdata' commands came in, then a flood control message, then ~32,161 more.
mod6: Then the weirdness/wedging seems to have started.
mod6: If anyone sees the same things in your debug.log, please write in.
mod6 been looking at this for some time now. Need food. bbs.
mod6: back around. will keep checkin' back.
shinohai: The cognitive dissonance of that lot amazes me "because mp says".
snsabot: (ossasepia) 2020-02-22 BingoBoingo: In other news, a number of visible trb nodes have been wedged for some time.
mod6: asciilifeform: I haven't gotten a new block since ~1pm on my last restart.
mod6: So, I'll clean my log, and restart again. It'll probably catch up a bit, but then we'll see.
mod6: Granted, could be just doing something wrong. I dunno. From what you're saying to me, sounds like your nodes are back to working 'fine'?
mod6: *shrug* we'll see how it goes. just started my node. height = 618545 currently.
mod6: if it keeps up, great! if not, will publish debug.log.
mod6: yeah, well, was looking for something that might point to why the fuck i wasn't getting any blocks.
mod6: well, it ~was~ getting blocks, upon immediate restart. then would promptly fall behind, and never get another, meanwhile not accepting any RPC commands.
mod6: just call 'getinfo' or 'stop' and just hang there in term.
mod6: i posted the log above, after the 'getdata' onslaught, RPC hang.
mod6: That doesn't show you much, but it does show that I issued the command after the wave of 'getdata'. It hung there for ~8 hours until I finally killed it off like about 10 minutes ago.
mod6: alright, have a good night.