awt[asciilifeform|billymg]: asciilifeform, shinohai: http://logs.bitdash.io/log-search?q=peer_offline_interval_seconds&chan=pest
awt[asciilifeform|billymg]: asciilifeform: what evidence is there that this is a bug?
asciilifeform: awt: hmm what's that knob set to by default ?
shinohai[asciilifeform]: ack awt, I had forgotten to set that.
shinohai[asciilifeform]: Still seeing asciilifeform as hearsay tho.
asciilifeform: seeing shinohai as peered tho
shinohai[asciilifeform]: heh that time you came through normally.
awt[billymg]: asciilifeform: try %knob
asciilifeform: awt: 60
awt[asciilifeform|billymg]: Yeah that's the default
asciilifeform: these join/parts defo not 60s apart
bitbot: Logged on 2022-04-19 01:15:59 shinohai[asciilifeform]: http://btc.info.gf/uploads/PEST2.png
asciilifeform: (and no such join/parts seen on asciilifeform's end fwiw)
asciilifeform: hence suspected bug
shinohai[asciilifeform]: imma try setting that knob to large # guess I can cobble together filter for weechat if dunwork.
asciilifeform: shinohai: notice they weren't 60s apart tho
asciilifeform: and no join/part noise b/w/ asciilifeform showing up on shinohai's end as peered vs hearsay
shinohai[asciilifeform]: Yeah the join/parts all occur on my end @ completely random times.
asciilifeform: so difficult to see how the knob pertains
asciilifeform: fwiw shinohai has been showing up on asciilifeform's console as peered ever since this point
bitbot: Logged on 2022-04-18 22:15:59 shinohai[asciilifeform]: aha! now works, you just "joined".
awt[asciilifeform|billymg]: asciilifeform: are you familiar with how the decision is made as to when to send a join/part?
asciilifeform: awt: iirc is when no packets recvd during peer_offline_interval_seconds neh
asciilifeform: (then , 'part')
awt[asciilifeform|billymg]: presence check is made every 5 seconds
awt[asciilifeform|billymg]: So join could come much sooner than 60s
asciilifeform: join yes. but why the part ?
awt[asciilifeform|billymg]: a part indicates (duriing a presence check) that the at hasn't been updated for > 60s.
asciilifeform: awt: do i misread or is the timestamp in fact only updated when there's a logline rather than when any valid packet?
asciilifeform: or hm, superficially correct. but still suspect that update_at was not being called, for some reason, on shinohai's station
awt[asciilifeform|billymg]: asciilifeform: see station.py:141
awt[asciilifeform|billymg]: should be called on IGNORE
asciilifeform: http://btcbase.org/patches/9978-bugfixes/tree/blatta/lib/station.py << lol 404 ( hey phf ?? )
asciilifeform goes to look in local copy
asciilifeform: awt: loox like in get_at , the time is converted from utc to local, but in in handle_is_online, time.time() used ?
asciilifeform currently suspects that bug triggered on machine where local clock not set to utc. but not yet found concrete proof
awt[asciilifeform|billymg]: asciilifeform: possibly but pestbot is running on a machine with local time not set to utc and I don't see these issues.
asciilifeform: hmm
signpost[asciilifeform] just set his server to UTC to see if that caused peering with billymg to work.
signpost[asciilifeform]: doesn't look like it, current active peers are asciilifeform, awt, jonsykkel, mod6, shinohai.
shinohai[asciilifeform] has no other peer in list currently but asciilifeform however sees signpost fine.
awt[asciilifeform|billymg]: signpost: possible debugging technique for peering issues could be do backup blatta db, remove all other peerings, then send to the other party to debug locally
signpost[asciilifeform]: will give that a try when he pops on next
billymg: !c uptime
billymg: meh, still nothing. tried opening crawlerbot's port via ec2's "security groups" UI
billymg: so not that
billymg: signpost: still a mystery to me why we're not peered but at this point i'm ok to wait for it to "fix itself" (via whatever random change in system or config finally shakes it loose)