asciilifeform: also fwiw his total block delays (red) match the ones on my ssd node (zoolag)

asciilifeform: doesn't see zoolag at all

asciilifeform: mircea_popescu: zoolag, the more reliable of my 2 nodez, has 4GB total !

asciilifeform: http://btcbase.org/log/2017-03-15#1627306 << it worx great for zoolag-to-dulap, and ben_vulpes , trinque are also on ssh wires, no bug reports so far ☝︎☟︎

asciilifeform: (right now, e.g., zoolag and dulap happily also find each other over ordinary peer table and connect plaintext)

asciilifeform: http://nosuchlabs.com/pub/wtf/what_mp_had_and_zoolag_didnt.txt << new link, for posterity.

asciilifeform: http://nosuchlabs.com/pub/wtf/zoolag_blk0037.txt << uploaded for completeness/replicability.

asciilifeform: so looks like zoolag (and dulap, and everybody) reorged, but mircea_popescu's node didn't

asciilifeform: grep -wFf mp_but_not_zoolag.txt mp_blk0036.txt > what_mp_had_and_dulap_didnt.txt

asciilifeform: diff mp_u.txt zoolag_u.txt | grep '^>' | sed 's/^>\ //' > zoolag_but_not_mp.txt

asciilifeform: diff zoolag_u.txt mp_u.txt | grep '^>' | sed 's/^>\ //' > mp_but_not_zoolag.txt

asciilifeform: cut -d' ' -f1 zoolag_blk0036.txt | sort | uniq > zoolag_u.txt

asciilifeform: http://nosuchlabs.com/pub/wtf/zoolag_blk0036.txt ;

asciilifeform: mircea_popescu: the 40-80 secs. verifications are still 15x slower than on zoolag (ssd box). i wonder, possibly , if the remaining delay still consists of disk -- but of block fetches, rather than tx index.

asciilifeform: so far it's dulap <--> zoolag.

asciilifeform: but interestingly 0 reorgs on zoolag in past couplea months

asciilifeform: mircea_popescu: this was on zoolag after <24 hrs.

asciilifeform: in other updates, 0 blackholing since wiring zoolag to dulap. thus far.

asciilifeform: mircea_popescu: holy fuck, 454403 14 minutes (and counting) on dulap; verified on zoolag in 15 seconds

asciilifeform: in other noose! zoolag and dulap are now wire-via-ssh-tunneled together.

asciilifeform: !~later tell mircea_popescu in re: http://btcbase.org/log/2017-02-23#1617048 , interestingly zoolag -- despite being an x86 comp the size of a tea saucer, and weighing ~400 gram -- has roughly 3x faster block verification (of given block) than dulap ! -- on account of ssd. ☝︎

asciilifeform: in other noose, http://wotpaste.cascadianhacker.com/pastes/jJ7iS/?raw=true << on a traditional (zoolag) trb node. i never once saw these in past log readings, and now they are quite common.

asciilifeform: because as it is, trb nodes (such as zoolag) are getting the hammer.

asciilifeform: mod6: dulap (with the new snip) is actually beating zoolag

asciilifeform: the other major disgrace is that i have no way to make, e.g., zoolag and dulap NEVER MOTHERFUCKING BREAK UP

asciilifeform: in other wtf's, banning pings took dulap from 50+ to 7 peers (1 of which is zoolag), and none of'em seem to know of any block past 454073

asciilifeform: BingoBoingo, jurov , and anybody else still running old prb nodes for whatever reasons of their own -- note that you will no longer be able to connect to dulap. (or to zoolag, when i patch it. or to anybody else who includes this patch.)

asciilifeform: what ~can~ you connect to? zoolag?

asciilifeform: zoolag is current and working

asciilifeform: thestringpuller: zoolag

asciilifeform: i.e. dulap will occasionally drop zoolag! and there is currently nothing i can do to force it not to

asciilifeform: http://wotpaste.cascadianhacker.com/pastes/SlwGQ/?raw=true << this is fresh from zoolag. and very typical.

asciilifeform: ( though zoolag is blackholed, it is not unusual, sits like this half the time )

asciilifeform: aaaaand now zoolag blackholed, instead.

asciilifeform: fwiw neither zoolag nor dulap have ever oom'd.

asciilifeform: in other noose, 70.33.211.11 (yes, 1 box) has been ddosing trb nodes, in particular zoolag. ☟︎

asciilifeform: dulap & zoolag are at 426394.

asciilifeform: zoolag = 72.83.9.184

asciilifeform: in other nyooz, zoolag has been blackholed for almost a day.

asciilifeform: however an auto-deedbotronic 'zoolag is up/down' might be useful.

asciilifeform: mircea_popescu, ben_vulpes, mod6, et al: zoolag @ 72.83.9.184.

asciilifeform: and zoolag

asciilifeform: zoolag is back, at 72.83.9.196:8333.

asciilifeform: in other interesting nyooz, zoolag appears to be perma-blackholed.

asciilifeform: interestingly, it was among those NEVER exposed directly to the net, fed -connect directly from zoolag (on lan)

asciilifeform: zoolag is a different machine !

asciilifeform: gotta do a few things to the mains wiring, i (and zoolag) will be down for 30 min. to an hour.

asciilifeform: on zoolag, to be specific

asciilifeform: in other news, zoolag was blackholed for a record-breaking 8 hours. ☟︎

asciilifeform: ^ currently in live fire on zoolag and dulap

asciilifeform: achtung panzers: zoolag is back online.

asciilifeform: achtung panzerz! brief scheduled outage on zoolag, starting now.

asciilifeform: ~zoolag~ is a dozen behind

asciilifeform: nothing on zoolag.

asciilifeform: ben_vulpes: the aws box which appeared to exist solely to tie up zoolag - quite aggressively

asciilifeform: kakobrekla et al: zoolag is back.

asciilifeform: kakobrekla et al: zoolag will be going down for ssd upgrade starting now and ending with a few hrs later

asciilifeform: incidentally, zoolag is under heavy and modestly-clever ddos ☟︎

asciilifeform: 173.73.235.152 --- zoolag

asciilifeform: not on zoolag tho

asciilifeform: with zoolag a close second

asciilifeform uncrates brand new half-TB ssd for zoolag

asciilifeform: zoolag is also running same, as of last night.

asciilifeform: kakobrekla et al: zoolag is back. (at least until it exhausts its disk)

asciilifeform: attn kakobrekla et al: zoolag going down for maintenance, next ~8hr or so

asciilifeform: zoolag F actually

asciilifeform: in other nyooz, 73 connexions on zoolag, 41 - on bucephalus.

asciilifeform: (incidentally, 67 connexions on zoolag, 28 on bucephalus, both at full height)