log☇︎
79100+ entries in 0.025s
asciilifeform: idea was, this-here static build will do same thing on every box where it builds and doesn't bomb on warmup.
asciilifeform: just like http://btcbase.org/log/2017-08-04#1694106 observation. ☝︎
asciilifeform: it was still THERE, waiting.
asciilifeform: see, it may seem to mod6 that asciilifeform is simply being difficult, whereas what asciilifeform found was that WE NEVER ACTUALLY FIXED 168K ☟︎
asciilifeform: weigh the 2 kernels, you'll see why.
asciilifeform: if at all possible.
asciilifeform: out of bsd.
asciilifeform: naively thought 'i'll start with the smallest trb node!'
asciilifeform: i'd like to get OFF linux.
asciilifeform: if i am mistaken, mod6 et al plox to say when and where it was resolved.
asciilifeform: went away on linux ( and apparently openbsd ) from locks patch, and that was the end of the thread
asciilifeform: http://btcbase.org/log/2015-07-23#1210108 << afaik this was never actually resolved in the logs ☝︎
asciilifeform: signed, passes checksums , etc.
asciilifeform: i am using literally the same deps dir as for past 2y.
asciilifeform: SAME ONE WE ALL USE
asciilifeform: which else
asciilifeform: THE MOTHERFUCKING FROZEN ONE
asciilifeform: http://btcbase.org/log/2015-07-05#1188043 ☝︎
asciilifeform: mod6: i've been 'seeing' for ~3h now
asciilifeform: !#s 2c2314f353
asciilifeform: 4evah.
asciilifeform: and it goes on, and on, the invalidchainfound index marches on and on, then reorg fails, then ... etc
asciilifeform: http://wotpaste.cascadianhacker.com/pastes/GWzyh/?raw=true << the pattern, in short. ☟︎
asciilifeform: http://nosuchlabs.com/pub/liquishit.txt << representative sample of the interesting part. (warning -- 20MB!)
asciilifeform: ^ whole debug log since t=0
asciilifeform: phf, mod6 , et al : http://nosuchlabs.com/pub/168k.txt.tar.gz << log ☟︎
asciilifeform: all this time i thought there were reproducibles. but it is nonsense to speak of reproducibles in 200Mb of liquishit dep that does whatever the fuck it wants
asciilifeform: i am increasingly of the notion that i can't rreason about ANY of it
asciilifeform: my suspicion is that the bdb locks patch somehow has no effect when bdb built on netbsd ☟︎
asciilifeform: on 1 particular os previously afaik untested
asciilifeform: 1 particular machine
asciilifeform: nor the timings.
asciilifeform: eatblock doesn't replicate the unknown stream of wild sewage that thing ate.
asciilifeform: how?
asciilifeform: replay??!
asciilifeform: debug how?
asciilifeform: anyway phf mod6 BingoBoingo et al taking suggestions ( other than the beneath-contempt nonsense of 'reboot and jiggle the handle blindly until it works and forget about cement fleet ' )
asciilifeform: http://btcbase.org/log/2017-03-28#1632985 << see also ☝︎
asciilifeform: BingoBoingo: i was reading plusminusweek of each of those search res for past 2h
asciilifeform: somehow
asciilifeform: but fixed by mp's patch 2.5y ago. and apparently unfixd by bsd
asciilifeform: phf: there was a bdb idiocy iirc that wedged at 168k
asciilifeform: ( i have 0 instances of wedged bring up on linux since mircea_popescu's bdb patch, in 30 or so shots on machines in various spots )
asciilifeform: trb on linux : does
asciilifeform: does not meet cement standard.
asciilifeform: BingoBoingo: the absolute most total nogood.jog
asciilifeform: ( and where if the addnode people get hiccupped it will pick a rando scum to rely on, and never drop him no matter how many hours, days, WEEKs without newblock incoming)
asciilifeform: i duneven know if to blame bsd ( how..? ) or the imbecile's sync algo where all depends on who first node syphilitically fucks on warmup
asciilifeform: fucking disgrace, is what this is
asciilifeform: i walked the logs , found no record of a nailed root cause or finalsolution
asciilifeform: i seem to recall.
asciilifeform: mod6, phf didja see 168kisms on openbsd?
asciilifeform: ( this ain't an ancient liquishit press )
asciilifeform: and nfi why.
asciilifeform: wedge at 168000 apparently. ☟︎
asciilifeform: worth a comparison
asciilifeform: and been a while since i synced from empty
asciilifeform: http://btcbase.org/log/2017-08-05#1694293 << i dun like relying on contents of rotten hdd any more than i have to ☝︎
asciilifeform: mod6: neato
asciilifeform bbl ( much meat )
asciilifeform: blockheight ~= 60k or so
asciilifeform: zoolag live as of now at ye olde 108.31.170.49 . ☟︎
asciilifeform: also at some point i'ma document this build and put own seal on phf's quite useful bsd fix.
asciilifeform: gentlemen, if anybody wants his wire back, write in. but it won't do you much good until the thing is synced.
asciilifeform: but worx.
asciilifeform: it won't be much use until syncs
asciilifeform: ACHTUNG PANZERS , welcome back the new zoolag
asciilifeform: ...fixed. the docs lied re default route
asciilifeform: why would it demand a working network PRIOR to assignment of static ip ?!!!!
asciilifeform: motheFUCKER 'route: writing to routing socket: Network is unreachable' when rebooted with the by-the-book static ip config.
asciilifeform: about to put zoolag back in service. it will sync, for some days.
asciilifeform: 4.8MB static elf, amd64, worx
asciilifeform: phf: worx!!!!
asciilifeform: better.
asciilifeform: you have nfi whether it is actually a last year's hex string, fed back to you again.
asciilifeform: what's there to inspect ? ☟︎
asciilifeform: random
asciilifeform: it's a hex string, neh
asciilifeform: noting ftr strictly.
asciilifeform: i do not know of anything that would qualify as a final solution for this.
asciilifeform: however one of the things that i always had ill ease about re pgp challenge-responsetrons , is that enemy who somehow substituted one, can get you to decrypt a message of his choice. (e.g. last year's launch codes.)
asciilifeform: trinque: this looks neato
asciilifeform: aaah lol 'realpath' dun exist.
asciilifeform: incidentally i have nfi how you got bdb to build, bsd libtool seems to be broken , tries to write to /include and barfs ( rather than to the demanded local dir )
asciilifeform: so i assumed it was a dud
asciilifeform: dunno -- possibly because it never turned into a proper vpatch ..?
asciilifeform: phf: the result runs ?
asciilifeform: yes indeed this is exactly it.
asciilifeform: phf: ty
asciilifeform: phf: remember by any chance when/where this was ?
asciilifeform: hm.
asciilifeform: but possibly because плохому танцору яйца мешают (tm)
asciilifeform: i had a year+ of unsuccess with openbsd
asciilifeform: i have this memory of phf barfing
asciilifeform: phf: didja do this at some point ?
asciilifeform attempts a build of traditional stator trb inside netbsd ( as rotor is unnecessary there, there is no drepper glibc )
asciilifeform: my barf was premature
asciilifeform: worx nao
asciilifeform: (needed perl)
asciilifeform: hm nm, fixed