MusicBrainz v4.1 can't update library, stuck on replication packet 183355

Hi,
i am not home in this stuff
This is the first time i create such monster :stuck_out_tongue:
I started 19-01-2026 to build the offline server i think with MusicBrainz v3.1, don’t ask wich version (28-29)
After my 5th import and indexing the dumps without a crash i had my own working server.
my last update and replication packet was 183355. 24-01-2026
so far the good news.

Then i went to build 4.01, db version 30, Perl Upgrade (v5.38.2), Python 3.10.12
Now i have a working offline server that works with that build 4.01.

i don’t run the server 24/24 7/7
i run them when i use the server.

i just got stuck with the replication packets, also that they are another “version” too with another numbering? (v2.tar.bz2)
i can't find out how to fix the update part for my library.
when asking a “random” number i got 1 update flag

art@Tiez09:~/musicbrainz-docker$ docker compose exec db psql -U musicbrainz -d musicbrainz_db -c “UPDATE replication_control SET current_replication_sequence = 183465;”
UPDATE 1
art@Tiez09:~/musicbrainz-docker$

so there should be an update
but if i try to get it says

art@Tiez09:~/musicbrainz-docker$ docker compose exec musicbrainz env PERL5LIB=/musicbrainz-server/local/lib/perl5:/musicbrainz-server/lib MUSICBRAINZ_REPLICATION_BASE_URL=https://metabrainz.org MUSICBRAINZ_DB_SCHEMA_SEQUENCE=30 METABRAINZ_REPLICATION_ACCESS_TOKEN=V***********h0RytxLZD ./admin/replication/LoadReplicationChanges
Mon Jan 26 23:07:32 2026 : Downloading https://metabrainz.org/api/musicbrainz/replication-183466-v2.tar.bz2 to /tmp/replication-183466-v2.tar.bz2
Mon Jan 26 23:07:32 2026 : Replication packet #183466 not available
art@Tiez09:~/musicbrainz-docker$

or

art@Tiez09:~/musicbrainz-docker$ docker compose exec musicbrainz env PERL5LIB=/musicbrainz-server/local/lib/perl5:/musicbrainz-server/lib MUSICBRAINZ_REPLICATION_BASE_URL=https://metabrainz.org MUSICBRAINZ_DB_SCHEMA_SEQUENCE=30 METABRAINZ_REPLICATION_ACCESS_TOKEN=V**********Ehxus0yh0Ry0ZD ./admin/replication/LoadReplicationChanges
Mon Jan 26 23:09:22 2026 : Downloading https://metabrainz.org/api/musicbrainz/replication-183465-v2.tar.bz2 to /tmp/replication-183465-v2.tar.bz2
Mon Jan 26 23:09:22 2026 : Error retrieving https://metabrainz.org/api/musicbrainz/replication-183465-v2.tar.bz2:
500 Can’t connect to metabrainz.org:443 (Connection reset by peer)
Content-Type: text/plain
Client-Date: Mon, 26 Jan 2026 23:09:22 GMT
Client-Warning: Internal response

Can’t connect to metabrainz.org:443 (Connection reset by peer)

Connection reset by peer at /musicbrainz-server/local/lib/perl5/LWP/Protocol/http.pm line 49.
Mon Jan 26 23:09:22 2026 : Retrying in 10 seconds…
Mon Jan 26 23:09:35 2026 : Downloading https://metabrainz.org/api/musicbrainz/replication-183465-v2.tar.bz2 to /tmp/replication-183465-v2.tar.bz2
Mon Jan 26 23:09:35 2026 : Replication packet #183465 not available
art@Tiez09:~/musicbrainz-docker$

In short

  1. Migration Status: Successfully migrated from v3.1 (Schema 29) to v4.1 (Schema 30).

  2. Environment: Running Docker on WSL2 (Ubuntu 22.04).

  3. Fixes Applied: Corrected PERL5LIB paths to resolve module location issues with the Perl v5.38 upgrade.

  4. The Problem: The new -v2 replication packets return a 500 Connection reset by peer or remain Not available, despite using a valid token and the correct /api/musicbrainz/ URL.

    thnx for the effort

Generally you should always use the latest version if you don’t want errors.

But Connection reset by peer is actually the MB servers getting hammered

1 Like

:clinking_beer_mugs: :clinking_beer_mugs: :wine_glass:

Sorry, that just made me laugh… or is it only an English phrase? :joy:

3 Likes

IIRC hammered also fit servers getting spammed. Don’t quote me on this tho

Yeah - hammered also means being beaten up. And it was a perfect choice of phrase for what the spammy AI bots are doing. Just also made me laugh as I imagined the server getting bored and just getting the beers in. My head makes weird associations with words at times.