[11:52:41] <wm-bb>	 <ederporto> Hello, everyone. Some of my tools have been presenting a 503 error for a few weeks now: ("`upstream connect error or disconnect/reset before headers. reset reason: connection termination`") and I seem to be unable to solve it or debug. I think is the same problem @Hugo_Lz reported in April. The repositories I witnessed this happening are wmb.toolforge.org and now,
[11:52:41] <wm-bb>	 more urgently, <clipped message>
[11:52:41] <wm-bb>	 <ederporto> sara-wmb.toolforge.org :(
[17:04:44] <andrewbogott>	 ederporto, are the 503s happening when accessing the tool, or happening internally to the tool itself? When I click on your two tool links they work just fine from here, at least their front pages.
[17:05:15] <andrewbogott>	 An easy-to-remember but questionable site I sometimes use for things like this is https://downforeveryoneorjustme.com/
[17:06:07] <wm-bb>	 <jeremy_b> hah questionable. are some sites too small potatoes for them to track?
[17:10:33] <taavi>	 I finished and deployed the fix to the overly long Istio headers earlier today which I expect made things a lot better in that regard
[17:18:59] <andrewbogott>	 jeremy_b, I don't think they track things, it's just literally a way to do a page load from some other IP that's not in your house.
[17:20:33] <andrewbogott>	 or, I guess, they do track things but that's not the feature that I use it for
[17:32:21] <wm-bb>	 <jeremy_b> right
[19:17:40] <wm-bot>	 !log jeanfred@tools-bastion-15 tools.integraality Deploy 73ac3a4 (Remove stray '>' character inside the <script> tag in base HTML template)
[19:17:42] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL
[19:17:42] <wm-bot>	 !log jeanfred@tools-bastion-15 tools.integraality Deploy ac8d9f4 (Replace invalid nested <ul> tag in footer in base HTLM template)
[19:17:44] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL
[19:17:45] <wm-bot>	 !log jeanfred@tools-bastion-15 tools.integraality Deploy f07edf9 (Add Queries endpoint support for P1/Q2/P3 qualifier columns) for T251008
[19:17:47] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL
[19:56:48] <wm-bot>	 !log lucaswerkmeister@tools-bastion-15 tools.lexeme-forms deployed 3c09a6963f (l10n updates: nl)
[19:56:51] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL
[20:05:31] <wm-bot>	 !log jeanfred@tools-bastion-15 tools.integraality Deploy c5294b1 (Support ?grouping as qualifier column value)
[20:05:34] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL
[20:23:49] <dhinus>	 !log tools.dimastbkbot stopped the tool to investigate db issues T428139
[20:23:52] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.dimastbkbot/SAL
[20:23:53] <stashbot>	 T428139: [toolsdb] Transaction History Length growing too much - https://phabricator.wikimedia.org/T428139
[23:23:10] <wm-bb>	 <Uyen> Hi @bd808, first of all thank you for your response. I have thought of using the same container as yours, only with the module embedded. I am new to building images and the build service, but would it be wise/possible to create a fork of your project with the added .so binary file of the module and to load it within the redis.conf? (re @wmtelegram_bot: <bd808> @Uyen: you
[23:23:10] <wm-bb>	 could tr <clipped message>
[23:23:11] <wm-bb>	 <Uyen> y making yourself a custom redis container something like https://gitlab.wikimedia.org/toolforge-repo...)
[23:58:52] <bd808>	 @Uyen: yeah, I think it would be possible. "Wise" is maybe a loaded question. ;) If you give it a good try I would be happy to give you some help if you end up stuck.