Show Idle (>14 d.) Chans


← 2022-01-10 | 2022-01-12 →
asciilifeform: helloworld
PeterL[asciilifeform]: hello asciilifeform!
asciilifeform: wb PeterL
asciilifeform: asciilifeform[4] | wb PeterL << loldupe
PeterL[billymg]: are you trying out a new version today or just saying hi?
asciilifeform: PeterL: smoketest
shinohai[asciilifeform|billymg]: ping billymg .... testing rekey
billymg: shinohai: working?
billymg: i'm still seeing you as hearsay
shinohai[asciilifeform]: same I still see you via whaack
shinohai[asciilifeform]: and asciilifeform
billymg: weird, dunno
shinohai[asciilifeform|billymg]: imma restart blatta one sec
billymg: shinohai: so in my logs i see lines where i'm sending you packets, but none where i've received any directly from you
billymg: can you see in your logs if you've sent anything to me?
asciilifeform: worth looking at yer clocks too
asciilifeform: iirc already 1 observed case of 2 peers not w/in +/- 15min of ea. other
billymg: "Tue Jan 11 17:04:20 -00 2022"
asciilifeform: billymg: you want date +"%s"
whaack[asciilifeform]: looks like a lot of people are having trouble peering
asciilifeform: i.e. epochal utc time
billymg: "1641920698"
PeterL[asciilifeform|billymg]: looks like you are about 10 minutes fast
shinohai[asciilifeform] ran `date -s "$(curl -sD - btc.info.gf | grep '^Date:' | cut -d' ' -f3-6)Z"` and keeps time synced to own www server ...
whaack[billymg]: PeterL: What's the time on your clock?
whaack[asciilifeform]: i have 1641920375
PeterL[asciilifeform]: I had 1641920180 when you posted above
asciilifeform: iirc whaack aint behind a nat. PeterL are you behind a nat?
asciilifeform: so it aint the clox
asciilifeform: hm billymg the logger still aint loggin pestnet
asciilifeform: defo <15m diff there
asciilifeform: (still oughta work if only 1 peer is)
asciilifeform: the 1 behind a nat needs to be the 1 who adds the other's ip:port to his at tho
asciilifeform: ohey hole in log
asciilifeform: oh yea from this, aite
asciilifeform: err, billymg
asciilifeform: loox like it was billymg <-> whaack peering that dunwork, correct?
whaack[asciilifeform]: no, we peered successfully
whaack[asciilifeform]: i've successfully peered in both directions, receiving and giving info
PeterL[asciilifeform]: I don't think I've connected with whaack yet though
whaack[asciilifeform]: PeterL<-> whaack, i sent peterL my info
whaack[asciilifeform]: PeterL: did you successfully peer to someone who has sent you info? or have all your peers been obtained by you sending them your info?
billymg: asciilifeform: whaack and i were able to peer
asciilifeform: billymg: hm what turned out to be the cure ?
billymg: no idea, whaack sent me some updated peering info yesterday or the day before and that did it
asciilifeform: billymg: so, wait, yer peered, but occasionally missing lines, or wat
bitbot: Logged on 2022-01-11 17:08:39 asciilifeform: hm billymg the logger still aint loggin pestnet
asciilifeform: ( we dunhave 'getdata' yet so i'd expect this'll happen periodically )
asciilifeform: billymg: aha
billymg: hrm, no echo though, i probably need to restart that one too after the date change
billymg: test
billymg: !. uptime
bitbot: billymg: time since my last reconnect : 0d 0h 0m
billymg: ok cool
whaack[asciilifeform]: billymg and i never had trouble peering. i gave him the wrong info at first, that was all
asciilifeform: hm interestingly, on asciilifeform's console, billymg , saw the bitbot output just prior to your cmd
asciilifeform: (which i'd expect would happen moar often given as current blatta doesn't look at selfchain/netchain iirc)
asciilifeform: i suppose bot output is close enuff timewise to the trigger ln
billymg: asciilifeform: i've seen out of order echos from the bot in my console before too
asciilifeform wonders whether bot output oughta have a small deliberate delay to avoid chain forkage
asciilifeform: 1/2s oughta suffice 100%
← 2022-01-10 | 2022-01-12 →