#metabrainz

Kia ora zas! I posted on the socials about our AI-crawler slowdowns, and again have had questions about why we don’t use Anubis, Cloudflare, etc (people are trying to be helpful, I guess). Perhaps you have a simple reply for them? I assume it’s because it blocks too much legit traffic, but I don’t think I’ve actually asked before

Actually we are currently pondering about various "solutions", none is perfect, and fitting them in our infrastructure isn't always simple. The ones you cited are candidates of course.

Thanks for the info! I'll reply

On test.mb.o why do we have such queries? https://test.musicbrainz.org/ssssss/mbid-a5433b... looks like CAA/IA query

[metabrainz.org] 14fettuccinae opened pull request #518 (03metabrainz-notifications…mail-sender): Seperate class to send mails https://github.com/metabrainz/metabrainz.org/pu...

bitmap: tests pass in https://github.com/metabrainz/musicbrainz-serve... - if you can take a look and it seems sensible, I'd put it on beta for a while for people to catch any AC weirdnesses we might have missed :)

yvanzo: looking at MBS-12729 that you shared yesterday :)

MBS-12729: Drop support for search.musicbrainz.org https://tickets.metabrainz.org/browse/MBS-12729

"By default, search queries are sent to search.musicbrainz.org and are rate limited." we should drop that line. But I guess given MBS-12730 is not done at the moment, the whole "Rate limiting" section in the install docs is basically outdated now

MBS-12730: Redirect search requests from search-disabled mirrors to the main server https://tickets.metabrainz.org/browse/MBS-12730

I guess we could rewrite it to something like "the server doesn't rate limit by default, if you are getting 503s check if the owner of the server you are using in SEARCH_SERVER has set specific rate limits"

Or actually just rename this section to "Searches"

Something like that, I guess

[metabrainz.org] release 03v-2025-07-04.0 has been published by 14github-actions[bot]: https://github.com/metabrainz/metabrainz.org/re...

zas: is there a problem with consul right now?

I can't get the metabrainz-prod container on isaac to start.

Jul 4 10:43:18 810cea9ddcd8 consul-template[30]: (view) kv.get(docker-server-configs/MeB/config.prod.json/payments/production): Unexpected response code: 429 (Your IP is issuing too many concurrent connections, please rate limit your calls) (retry attempt 6 after "8s")... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

these were the errors I was getting, but now the container is silent and not starting.

hmm. the old container starts fine. odd.

lucifer: any idea why this release might be broken as above? https://github.com/metabrainz/metabrainz.org/re...

checking

===== haproxy-postgres... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

* `=`... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

mayhem: not sure what is going on, but likely some service is spamming consul

Hi monkey... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

<zas[m]> "mayhem: not sure what is going..." <- did you stop the container just now?

I'm stopping few containers, in order to identify which one it is

shit, people are going to be missing their replication packets this hour.

thanks for looking at it, though. the others will live.

adhawkins: ^^ this wobble is known and should be resolved for the next hour.

pgbouncer containers are showing some errors :(

ok, spam stopped, I stopped metabrainz-prod artwork-redirect-beta metabrainz-test metabrainz-oauth-test

Did you mean to tag me in this? Or was it because I'm the one usually 'complaining' about local instances of mbserver? 😄

can I restarted meb-prod?

s/restarted/restart/

mayhem: wait, I'll do

done

adhawkins[m]: you're certain to notice when your client misses a packet for an hour, so I thought I'd let you know.

Nah, I'm not *that* anal about replication. Thanks for thinking of me though mayhem[m]!

zas: let me restart the latest version then.

k

artwork-redirect-beta metabrainz-test metabrainz-oauth-test are stopped, perhaps that's one of those

the container isn't starting. :(

metabrainz-prod is running

zas: please don't restart that container again for a while, I need it to do some critical tasks (send invoices).

yes, I restarted it the known good version.

k

I keep those test/beta containers off

bitmap: when you are around, please check isaac' pgbouncer & haproxy-postgres

<holycow23[m]> "hey lucifer have you added genre..." <- hey lucifer is this done?

holycow23: no not yet.