| 00:02 |
jonsykkel |
am getting some messages with up to [12] in the hearsay count |
| 00:02 |
jonsykkel |
(have 6 peers) |
| 00:02 |
awt |
jonsykkel: that's not good |
| 00:02 |
awt |
testing whitespace |
| 00:04 |
awt |
jonsykkel: were those messages with a relayer count of 12 GETDATA responses? |
| 00:04 |
jonsykkel |
yes |
| 00:05 |
awt |
ok noted, thx |
| 00:05 |
awt |
something wrong with the arithmetic there |
| |
~ 4 hours 45 minutes ~ |
| 04:50 |
awt |
I suspect mod6 has not updated, so there's still the potential for dupes. |
| 04:51 |
awt |
whaack also, afaik |
| |
~ 5 hours 13 minutes ~ |
| 10:04 |
jonsykkel |
wouldnt these stations crash tho |
| 10:05 |
jonsykkel |
i dont seem to be recving packets from whaack looking @ logs anyway. not peered with mod6 |
| 10:07 |
jonsykkel |
(mine did not cuz had patched manually) |
| |
~ 39 minutes ~ |
| 10:46 |
jonsykkel |
testing123 |
| 10:48 |
jonsykkel |
ok smalpesting now, bot sees me anyway |
| |
~ 2 hours 57 minutes ~ |
| 13:45 |
PeterL |
awt: http://btc.info.gf/paste/467a4e@raw crashed, you know what this error message means? |
| |
~ 2 hours 7 minutes ~ |
| 15:53 |
awt |
PeterL: I haven't seen this exception before. Are you perhaps on a laptop where the network interface is going up/down? |
| 15:54 |
awt |
jonsykkel: true whaack and mod6 appear to be offline from here as well |
| 15:54 |
PeterL |
2022-03-01 15:51:58: so looking at that on a laptop, but it was plugged in all night, and it has always been pretty stable in the past |
| 15:56 |
awt |
PeterL: anything in syslog indicating network downtime? |
| 15:59 |
awt |
pestbot: echo gm |
| 15:59 |
pestbot |
2022-03-01 15:59:25: gm |
| 16:00 |
PeterL |
2022-03-01 15:57:19: what does pestbot do? |
| 16:00 |
awt |
PeterL: supports one command: echo. For sanity checks when lines aren't showing up in the log, etc. |
| 16:01 |
PeterL |
2022-03-01 15:58:15: ah, I see. Are you going to add more functions to it? |
| 16:01 |
awt |
PeterL: no immediate plans. Lemme know if you have ideas. |
| 16:07 |
awt |
Inititally there were a lot of issues with the logger either omitting certain lines or not sending log line echoes, etc. So I set up pestbot also for a sanity check in those cases. |
| 16:08 |
awt |
As a minimum case to ensure blatta is funcioning at a basic level. |
| 16:19 |
billymg |
!. uptime |
| 16:19 |
bitbot |
billymg: time since my last reconnect : 3d 17h 34m |
| 16:19 |
billymg |
i still only see responses from the bot in the logs, not in my console |
| 16:19 |
billymg |
lemme check the blatta logs |
| 16:20 |
billymg |
!. uptime |
| 16:20 |
bitbot |
billymg: time since my last reconnect : 3d 17h 35m |
| 16:22 |
billymg |
logs show that the bot sends its response to asciilifeform, but not billymg |
| 16:22 |
billymg |
asciilifeform: do you see bitbot's echos in your console by any chance? |
| 16:23 |
billymg |
echos and/or responses to commands |
| 16:23 |
asciilifeform |
2022-03-01 16:22:49: billymg: not since pressed awt's latest ver |
| 16:31 |
billymg |
actually, sorry, the bot's pest station logs show that it's relaying my "!. uptime" message to asciilifeform, not its response. its responses don't show up anywhere in the station logs |
| |
~ 41 minutes ~ |
| 17:13 |
awt |
how does asciilifeform envison timestamp wallops to look? |
| |
~ 16 minutes ~ |
| 17:30 |
asciilifeform |
awt: was thinking, simply precede erry replayed msg w/ 1 wallop containing e.g. 'Replay: 2022-03-01 10:57:19:' |
| 17:31 |
asciilifeform |
afaik there's no way to make this (and many other ircisms) entirely un-ugly |
| |
~ 6 hours 28 minutes ~ |
| 23:59 |
awt |
asciilifeform: why wallop and not notice? wallops seems kind of weird |