Show Idle (>14 d.) Chans
← 2020-05-05 | 2020-05-07 → ↓
verisimilitude: I've tried specifying this from the <a> before, but WWW browsers helpfully ignore that, for no reason.
verisimilitude: Oh, while it's on mind, I'd appreciate if the RSS feed is only accessed every twelve hours or so; I don't update often enough for more than a few daily checks.
feedbot: http://mvdstandard.net/2020/05/imperial-college-pantsuit-panic-queen-sacked-for-breaking-zher-own-rules/ << The Montevideo Standard -- "Imperial College" Pantsuit Panic Queen Sacked For Breaking Zher Own Rules
spyked: http://logs.nosuchlabs.com/log/asciilifeform/2020-05-05#1011275 <-- done. in other news, I dunno wtf, I set the exact socket knobs for feedbot as snsabot and it still gets stuck somewhere. will have to debug further
snsabot: Logged on 2020-05-05 23:57:07 asciilifeform: defo interested. spyked plz add when you get a chance.
spyked: asciilifeform, did you set any other options (e.g. rcv timeout) besides the ones in http://www.loper-os.org/pub/logotron/active_disconnect_r3.kv.vpatch ?
spyked: http://logs.nosuchlabs.com/log/asciilifeform/2020-05-06#1011288 <-- hm. atm there's no per-feed setting for that, it just checks all feeds about once per minute. I could set it a bit higher, but I've already gotten complaints from other users that the (publish->notification) delay is high.
snsabot: Logged on 2020-05-06 01:05:38 verisimilitude: Oh, while it's on mind, I'd appreciate if the RSS feed is only accessed every twelve hours or so; I don't update often enough for more than a few daily checks.
spyked: so... verisimilitude, if it's really bothersome for you (does it eat up a lot of traffic, or what?), I'll add this to the feature list.
spyked: but right now getting the reconnect logic right is top priority, because wtf, I'm basing my schedule on the life of a tcp socket
verisimilitude: It's bothersome to me, yes; it makes my logs less pleasant to read. In the latest item, I've told whomever's checking the feed once every two minutes to stop, and I've told people to stop for every five minutes as well. If others don't mind, perhaps a per-site setting could be added, although I understand how burdensome this could be. I won't ask it be prioritized, but I'd appreciate it, spyked.
spyked: verisimilitude, got it, I'll see how I can make this work. meanwhile if you can use any further info to grep -v (e.g. the IP address that curls that link), I'd be happy to help.
verisimilitude: I don't understand what's meant by that. I typically browse through my HTTP server logs to see the referrers and whatnot; I simply dismiss accesses to the RSS feed and similar such resources if I want to get a less inaccurate idea of how my website's being accessed. If I understand, I'll clarify I don't need any particular help in ignoring feedbot, spyked.
spyked: verisimilitude: I meant that I can't solve your problem right away and I don't plan to atm (will review it in ~2 weeks from now, I guess), but I'll help with further info (e.g. feedbot's HTTP-side IP) if you need it.
spyked: tbh, I don't see why this is a problem at all. as you said, you can filter the access logs if there's too much noise there.
spyked: but in general, I don't see why one'd have expectations wrt access frequency for *any* public resource.
verisimilitude: Alright; I understand. I don't need the IP address, no. It's just the ``old-Internet'' vibe, spyked; I can ask the access be reduced and I'd prefer it, so why wouldn't I ask? Were it a great burden, I'd simply deal with it, but if it can be handled maybe two weeks from now, that would be nice.
verisimilitude: Since I'm asking for something to be done, feel free to suggest I do something, if wanting, of course.
spyked: verisimilitude, alright, makes sense. re. suggestions, perhaps it'd be useful to add that I personally let awstats do all the work for me, handling log processing and generating site usage reports. I rarely inspect logs manually, usually to see the latest weird that attackers are trying to cook up
spyked meant particularly webserver access logs
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-05-06#1011292 << this was the final solution to bot wedges, rather than that
snsabot: Logged on 2020-05-06 02:35:56 spyked: asciilifeform, did you set any other options (e.g. rcv timeout) besides the ones in http://www.loper-os.org/pub/logotron/active_disconnect_r3.kv.vpatch ?
asciilifeform: spyked: fleanode has a mysterious failure mode where disconnects you but doesn't close yer socket. linked item was my pill for this.
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-05-06#1011297 << you don't dedupe log prior to reading?! wainot?
snsabot: Logged on 2020-05-06 04:01:05 verisimilitude: It's bothersome to me, yes; it makes my logs less pleasant to read. In the latest item, I've told whomever's checking the feed once every two minutes to stop, and I've told people to stop for every five minutes as well. If others don't mind, perhaps a per-site setting could be added, although I understand how burdensome this could be. I won't ask it be prioritized, but I'd appreciate it, spyked.
asciilifeform: i'd go mad surely, if i did that
spyked: asciilifeform, ty. so if i understood correctly, the sock.recv call always returns after a while, doesn't it?
spyked will have to dig a bit into cl-irc internals to figure how ircbot behaves there, there's prolly some more obscurity in the cl "stream" abstraction
spyked: to be more pedantic: by "returns" I meant "returns or jumps into an exception". iirc the default socket receive timeout is infinite, so I'm wondering if python does some more setup there.
asciilifeform: spyked: in mine, i set it to time out deliberately
asciilifeform: it's the 'timeout' constant in the config.
asciilifeform: all recv time out after this-many s.
asciilifeform: when they time out during normal operation, rather than initial connection (where -- retries),nothing happens
asciilifeform: spyked: this is the mechanism you're interested in, i think.
trinque: spyked: if you find a way of setting a global socket timeout in sbcl I'd be mighty interested to know!
spyked: asciilifeform, setsockopt (in particular the description of SO_RCVTIMEO) says that "The default for this option is zero, which indicates that a receive operation shall not time out." but hm, I'll read your code more carefully and try to determine empirically if this is troo
asciilifeform: when one of those timeouts elapses, we check whether we've in fact received anyffin from upstream in the preceding Discon_TO (config constant) seconds.
asciilifeform: spyked: default dun timeout, no. i set it.
spyked: oh okay
asciilifeform: when connecting.
spyked: trinque, by 'global' do you mean 'for all sockets owned by the process'? buut.. yeah, I should document this properly, since I've started hacking into SBCL's setsockopt options already
spyked: the version I have is missing a few
asciilifeform: trinque: afaik you gotta set it :timeout s when opening ea. socket
trinque: something like python's socket.setdefaulttimeout would be nice
trinque: asciilifeform: aha
trinque: yeah, the python one applies to every socket created after the default is set; I know I can set it on each socket
trinque: (that was the problem years back with deedbot, slothfully didn't!)
asciilifeform: the interesting bit is that i had the timeout in the genesis version, and it in fact didn't help. because of fleanode's peculiar zombie effect. the detector was required to get rid of all wedges.
snsabot: Logged on 2020-05-06 09:44:33 asciilifeform: spyked: fleanode has a mysterious failure mode where disconnects you but doesn't close yer socket. linked item was my pill for this.
asciilifeform: trinque: my bot created the socket when connecting, and set timeout ea. time
asciilifeform: !q uptime
snsabot: asciilifeform: time since my last reconnect : 26d 19h 18m
asciilifeform: !w uptime
watchglass: asciilifeform: time since my last reconnect : 26d 21h 8m
asciilifeform: never 1ce had to manually cycle the thing, since that patch .
asciilifeform: (it auto-disconnects & reconnects when there's > disc_t seconds of silence from upstream. disc_t in default config is 180 s. )
asciilifeform: !w poll
watchglass: Polling 11 nodes...
watchglass: 143.202.160.10:8333 : Could not connect!
watchglass: 205.134.172.26:8333 : Alive: (0.021s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629237
watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.082s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629237
watchglass: 108.31.170.3:8333 : (pool-108-31-170-3.washdc.fios.verizon.net) Alive: (0.047s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629237 (Operator: asciilifeform)
watchglass: 205.134.172.27:8333 : Alive: (0.084s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629237 (Operator: asciilifeform)
watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.143s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=629237
watchglass: 208.94.240.42:8333 : Alive: (0.209s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629237
watchglass: 213.109.238.156:8333 : Alive: (0.291s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629237
watchglass: 103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.574s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629237
watchglass: 188.121.168.69:8333 : (rev-188-121-168-69.radiolan.sk) Alive: (0.056s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629238
watchglass: 192.151.158.26:8333 : Busy? (No answer in 20 sec.)
asciilifeform: spyked, trinque : in case still not obv.: there are no 'magic' pythonisms used in the example bot. errything in'ere oughta be 100% portable to anyffin that sits on posix sockets.
asciilifeform: originally i attempted the bot in ada, but realized that there aint a working sqlism glue for it just yet. hence ended up with that kludge.
jurov: BingoBoingo, I'm not going to please you: http://paste.deedbot.org/?id=N3LB
BingoBoingo: jurov: Thank you for letting me know. The only channel I can suggest is the comments on his blog posts.
jurov: thebitcoin.foundation/therealbitcoin.org was moved to 95.142.167.185 if anything is broken, i'm responsible
asciilifeform: jurov: hrm where's the ml link ?
asciilifeform: used to be on the front pg
jurov: oh i've removed #t and it somehow went together with it. moment
asciilifeform: jurov: btw are you planning to make a dedicated trb chan ?
asciilifeform: if so lemme know so i can add it to logotron
jurov: yes, later
asciilifeform: jurov: ml link back & worx, ty
asciilifeform: jurov: is the proggy that ate patches still attached ?
jurov: No, the site is completely static. You want to keep posting there?
asciilifeform: jurov: not critical. but was wondering whether it still worked.
jurov: asciilifeform: it was wired to mailman turd
jurov: Will set up the channel shortly and there discuss patch submission.
asciilifeform happy to supply logging, and if jurov later wants to set up own instance of such logotron also, will help
asciilifeform: jurov: lemme know if you want watchglass in there too .
asciilifeform: it doesn't speak unless manually commanded .
asciilifeform: !w poll
watchglass: Polling 11 nodes...
watchglass: 143.202.160.10:8333 : Could not connect!
watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.022s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629249
watchglass: 205.134.172.26:8333 : Alive: (0.089s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629249
watchglass: 205.134.172.27:8333 : Alive: (0.096s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629249 (Operator: asciilifeform)
watchglass: 108.31.170.3:8333 : (pool-108-31-170-3.washdc.fios.verizon.net) Alive: (0.098s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629249 (Operator: asciilifeform)
watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.114s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=629249
watchglass: 208.94.240.42:8333 : Alive: (0.228s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629249
watchglass: 213.109.238.156:8333 : Alive: (0.350s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629249
watchglass: 188.121.168.69:8333 : (rev-188-121-168-69.radiolan.sk) Alive: (0.360s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629249
watchglass: 103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.562s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=629249
watchglass: 192.151.158.26:8333 : Busy? (No answer in 20 sec.)
asciilifeform finds it pretty handy, not only for monitoring own nodez, but to determine whose nodes actually work, and makes sense to peer with
asciilifeform: !w peers 205.134.172.27
watchglass: 205.134.172.27:8333 : reported peers: 18.141.160.175 23.239.0.21 31.48.249.2 34.219.185.136:9595 34.220.232.128 46.88.183.195 46.229.165.143 65.96.222.54 69.118.65.228 71.34.1.183
watchglass: 205.134.172.27:8333 : reported peers: 77.8.57.5 78.99.137.154 78.110.73.83 83.99.245.20 91.45.93.126 91.134.145.202 91.219.25.232 92.117.182.4 93.6.41.59 142.196.232.55
watchglass: 205.134.172.27:8333 : reported peers: 174.114.124.12 177.74.189.121 177.96.224.194 177.206.254.253 178.14.17.17 179.113.85.13 190.177.114.36 192.164.247.23 194.14.246.200 199.247.7.208
watchglass: 205.134.172.27:8333 : reported peers: 203.129.27.87 208.94.240.42 213.109.238.156
asciilifeform: ^ in that vein, also handy .
verisimilitude: I read the Apache2 logs directly, asciilifeform, and I don't usually get more than two thousand requests in a day.
feedbot: http://mvdstandard.net/2020/05/two-kilometers-of-copper-phone-line-stolen-in-melo-cerro-largo/ << The Montevideo Standard -- Two Kilometers Of Copper Phone Line Stolen In Melo, Cerro Largo
← 2020-05-05 | 2020-05-07 → ↑
Random(asciilifeform) | Download hourly DB snapshot | Get Source Code