#metabrainz

Is there an alternate location I can get dumps from other than data.metabrainz.org? I'm getting a stupid slow 300kb/s - it's going to take 6 hours to get mbdump.tar.bz2. I should be getting over 1MB/s

bitmap[m] No row found in event_art_archive.event_art with keys id='41481508877'. at /musicbrainz-server/admin/replication/ProcessReplicationChanges line 507.

No row found in event_art_archive.event_art with keys id='41481509334'. at /musicbrainz-server/admin/replication/ProcessReplicationChanges line 507.

No row found in event_art_archive.event_art with keys id='41481515769'. at /musicbrainz-server/admin/replication/ProcessReplicationChanges line 507.

Still getting these with your eaa-dump branch. I wasted fucking hours. :(

Oh, was I supposed to wait for the next dump or something? geez.

i notice that chatbrainz.org is still running synapse 1.115.0, which is 6 months old - might want to double-check processes for keeping that server updated/maintained.

[listenbrainz-server] 14MonkeyDo opened pull request #3240 (03master…typescript-5): chore: Update Typescript to v5 https://github.com/metabrainz/listenbrainz-serv...

[listenbrainz-server] 14MonkeyDo opened pull request #3241 (03master…hide-apple-music-export): Hide "Export to Apple Music" option if user not signed in, or into Apple Music https://github.com/metabrainz/listenbrainz-serv...

nelgin (IRC): sorry, I realized that musicbrainz-docker will use the "prebuilt" images by default, so simply switching to the eaa-dump branch and doing a build won't actually see those changes. if you show me the contents of your .env file (in the musicbrainz-docker dir) I can help you make the necessary modifications to build the changes

it does store the mbdump files in a volume, so I believe it shouldn't have to redownload them at least

yvanzo: hi, is there any way to opt-out of the using the prebuilt images other than by hand-editing the compose files?

s/the//

Hi, I have a really quick question. I've been super busy the past week so I haven't had a chance to be active here, but I've already submitted my ideas for GSOC and talked with a few members, specifically mayhem . Do I need to do anything else before I apply? I'm planning on submitting it this weekend. (I was the person discussing sentiment analysis within recommendation systems + visualizations pertaining to recommender systems)

[musicbrainz-server] 14mwiencek merged pull request #3323 (03master…MBS-13453): MBS-13453: Avoid double-decoding some errors https://github.com/metabrainz/musicbrainz-serve...

bitmap[m], I

I'm still going to have themissing entries from replication thought, aren't I?

# cat .env

MUSICBRAINZ_WEB_SERVER_HOST=192.168.168.1

MUSICBRAINZ_CRONTAB_PATH=/restore/musicbrainz-docker/local/replication.cron

COMPOSE_FILE=docker-compose.yml:local/compose/memory-settings.yml:compose/replication-token.yml

great, now what?

compose exec indexer python -m sir amqp_setup

amqp.exceptions.AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile.

nelgin: my understanding is that you're still seeing those because it never actually downloaded/imported the EAA dump. hopefully we can fix that

I'm not a musicbrainz-docker expert, so bear with me

#236 appears to have fixed that issue.

bitmap[m] sure, let's give it a go. I can always start again tomorrow after the new dump :/

Are you wanting me to make that change in the yaml file?

nelgin (IRC): first try making the changes I linked above to docker-compose.yml, then run `docker compose build`

(on the eaa-dump branch)

# git branch

* eaa-dump

Yup, I'm there

if this works you won't have to wait for the next dump btw

docker compose build will take a while to complete

urgh, I wish it picked a color other than blue.

<JuliaHusar[m]> "Hi, I have a really quick..." <- Hi! I'm still waiting for an answer to my questions on our community forums from last week. we should really work out a plan for what you actually plan on doing before submitting an application.

so, start by providing answers on that thread.

mayhem[m]: Oh shoot, sorry I didn't see that! I will do that later today :)

bitmap[m] ok that just finished

nelgin (IRC): now you'll have to drop the existing DB so you can reimport: docker compose down db -v

note that will delete your pgdata volume

then you can creating the DB from scratch: docker compose run --rm musicbrainz createdb.sh -fetch

but keep an eye on the output and make sure it actually downloads the event-art-archive dump

Saving to: ‘/media/dbdump/mbdump-event-art-archive.tar.bz2

looks good

After the import is complete should I do the materialized tables step, replication and add the indexes?

yep, you'll have to follow the rest of the setup as before

I just noticed a bunch of missing "attributes" is that ok?

No data file found for 'area_attribute', skipping

No data file found for 'area_attribute_type', skipping

No data file found for 'area_attribute_type_allowed_value', skipping

nelgin (IRC): that's expected since those tables are currently empty

Cool.

Fri Mar 28 17:40:22 2025 : Creating search indexes ... (CreateSearchIndexes.sql)

hmm interesting...

why is moon.metabrainz.org down

Why do you ask?

i can't connect to musicbrainz without a vpn

moon.metabrainz.org didn’t send any data.

ERR_EMPTY_RESPONSE

If you can't connect that's likely because your IP was blocked, and it was likely because MB services are overloaded by traffic for stupid AI bots using residential IPs. You can send your current IPv4 & v6 to me so I can check if that's the reason.

s/for/from/

zas[m] read dms

bitmap[m] I probably should have waited until tomorrow considering how long replication is going to take to catch up.

One thing I don't like about pgsql, replication is sooooo sllloooowwww....

it should catch up fine if you let it run overnight :)

No row found in documentation.l_artist_work_example with keys id='450882'. at /musicbrainz-server/admin/replication/ProcessReplicationChanges line 507.

No row found in documentation.link_type_documentation with keys id='834'. at /musicbrainz-server/admin/replication/ProcessReplicationChanges line 507.

I don't think documentation is included in repcliation right?

those tables are included in the documentation dump, which also isn't fetched by musicbrainz-docker. it's very unlikely you'd need them though

replication finished.

I forgot the step to load the search indexes tho. :/

wget: memory exhausted