[17:45:12] !staff CVNBot14 has flooded out from #cvn-commons and has not returned for over an hour [17:45:13] Thanks AntiComposite, staff have been notified of your request and should be around shortly to assist you. [17:45:42] AntiComposite: thx, checking logs now [17:45:56] AntiComposite: so what did you see in #cvn-commons? Did the bot go quiet, or also leave? [17:46:26] batch deletions, each with a summary longer than one line [17:46:47] it got halfway through a multi-line message and then [12:22:05] ◀━━ Quits: CVNBot14 (~CVNBot14@cvn/bot/CVNBots-C) (Excess Flood) [17:47:32] > cvn.cvn+ 11853 20.3 0.9 1025224 80228 ? Sl Oct04 852:19 /usr/bin/mono /srv/cvn/services/cvnbot/CVNBot14/CVNBot.exe [17:47:37] I don't see it on the irc.wikimedia side either [17:49:35] it's flooded out a lot recently looking at the logs in #cvn-bots [17:50:10] I'm trying to find out what happened in irc.wm.o, since it's not there but I don't see it leave [17:50:15] the bot is meant to restart on its own if that happens [17:51:24] AntiComposite: so.. this is diffrent from the issue where you restart it with command because now you can't [17:52:44] 821423:[2021-10-07 14:48:24] → CVNBot14 joined (~CVNBot@anonymous.user) [17:52:44] 877226:[2021-10-07 17:22:43] ⇐ CVNBot14 quit (~CVNBot@anonymous.user): Read error: Connection reset by peer [17:52:48] (from irc.wikimedia.org) [17:56:03] AntiComposite: https://github.com/countervandalism/CVNBot/issues/74 [17:56:10] OK, so it did see the error and tried to restart [17:57:17] Could not connect to: irc.libera.chat:6667 Could not resolve host 'irc.libera.chat' [17:57:45] that would be a problem [17:58:03] !log killall cvn.cvnservice @ cvn-app8 [17:58:04] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Cvn/SAL [17:58:50] Still it should have exited and let a new process try [17:58:54] it's up and speaking [17:59:00] but for now I"m gonna say that's unrelated to the main problem we've been monitoring [17:59:11] where RCReader stops but it stays in the feed channel [17:59:21] yes, I think we get to blame this one on dns