March 3, 20197 yr This is happening since the latest update. @saarg is looking into it. I can only recommend Unraid. Hold on for the mbz docker to be fixed and you'll love it!
March 3, 20197 yr Good to know, thanks for the heads up. I did try and search the forum before posting but didn't see anything, couldn't have looked hard enough.
March 3, 20197 yr It just broke last week (see my post right above about database version conflict). My error messages have been changing, but I am now receiving the same error as you do. Should be related to the database upgrade.
March 3, 20197 yr @steve1977 @Habitual_Sinner Can you guys try to add :92 to the repository field? This way you should be back to before we migrated to the new build system and it should work. The problem is that we upgraded the alpine base from 3.6 to 3.9 and that bumped the database to a higher version.
March 3, 20197 yr 5 minutes ago, saarg said: @steve1977 @Habitual_Sinner Can you guys try to add :92 to the repository field? This way you should be back to before we migrated to the new build system and it should work. The problem is that we upgraded the alpine base from 3.6 to 3.9 and that bumped the database to a higher version. Thanks for your note. I may have added it wrongly, but not working. See full error below: Unable to find image 'linuxserver/plex:92' locally /usr/bin/docker: Error response from daemon: manifest for linuxserver/plex:92 not found.
March 3, 20197 yr 25 minutes ago, steve1977 said: Thanks for your note. I may have added it wrongly, but not working. See full error below: Unable to find image 'linuxserver/plex:92' locally /usr/bin/docker: Error response from daemon: manifest for linuxserver/plex:92 not found. Why did you add it to the plex container?
March 3, 20197 yr Oh Sleepy me... I believe this will solve the issue related to the database upgrade, so this should be fine for @Habitual_Sinner. I am still facing the issue though, which is likely related to my permission issues? (node:277) Warning: Possible EventEmitter memory leak detected. 12 resolve listeners added. Use emitter.setMaxListeners() to increase limit
March 3, 20197 yr 37 minutes ago, steve1977 said: Oh Sleepy me... I believe this will solve the issue related to the database upgrade, so this should be fine for @Habitual_Sinner. I am still facing the issue though, which is likely related to my permission issues? (node:277) Warning: Possible EventEmitter memory leak detected. 12 resolve listeners added. Use emitter.setMaxListeners() to increase limit No idea to be honest. Might be best to just start with a fresh database. But then you should update the container to the latest to get the new database engine.
March 3, 20197 yr Thanks, will try. Remove the docker and set up a new one with same settings? Or manually delete the database file on the cache disk?
March 3, 20197 yr 1 hour ago, steve1977 said: Thanks, will try. Remove the docker and set up a new one with same settings? Or manually delete the database file on the cache disk? No need to remove the container. Just set up a new folder for both the /data mount and the appdata folder.
March 4, 20197 yr 23 hours ago, saarg said: No need to remove the container. Just set up a new folder for both the /data mount and the appdata folder. Thanks. I've done so and it seemed to pull a new database. However, I am getting "502 bad gateway" when opening the GUI. There are some errors in the log including the following: Mon Mar 4 06:00:05 CST 2019 : LoadReplicationChanges failed (rc=111) - see /config/log/musicbrainz/slave.lo 2019-03-04 07:00:10.412 CST [26974] ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist 2019-03-04 07:00:10.412 CST [26974] STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE 2019-03-04 19:00:06.435 CST [7977] WARNING: SET TRANSACTION can only be used in transaction blocks Any thoughts?
March 4, 20197 yr 9 hours ago, steve1977 said: Thanks. I've done so and it seemed to pull a new database. However, I am getting "502 bad gateway" when opening the GUI. There are some errors in the log including the following: Mon Mar 4 06:00:05 CST 2019 : LoadReplicationChanges failed (rc=111) - see /config/log/musicbrainz/slave.lo 2019-03-04 07:00:10.412 CST [26974] ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist 2019-03-04 07:00:10.412 CST [26974] STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE 2019-03-04 19:00:06.435 CST [7977] WARNING: SET TRANSACTION can only be used in transaction blocks Any thoughts? I don't know why those messages are there, but I had it also, so that is not the reason. You are sure you have the latest image? Try a force update on the container.
March 5, 20197 yr @saarg I nuked both the image and the data and started fresh with latest. Looks like postgres needs to be brought up to v11. 2019-03-05 07:49:20.931 AWST [79942] FATAL: database files are incompatible with server 2019-03-05 07:49:20.931 AWST [79942] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 10.5.
March 5, 20197 yr 9 hours ago, saarg said: I don't know why those messages are there, but I had it also, so that is not the reason. You are sure you have the latest image? Try a force update on the container. Unfortunately still the same. @tjb_altf4's may point to the issue? Better to downgrade the database or do you anticipate a chance to get this work with the most recent built?
March 5, 20197 yr Just saw another docker update available, which I did. Error message now as below: 2019-03-05 19:46:28.148 CST [419] FATAL: database files are incompatible with server 2019-03-05 19:46:28.148 CST [419] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 10.5.
March 5, 20197 yr 3 hours ago, steve1977 said: Just saw another docker update available, which I did. Error message now as below: 2019-03-05 19:46:28.148 CST [419] FATAL: database files are incompatible with server 2019-03-05 19:46:28.148 CST [419] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 10.5. 15 hours ago, tjb_altf4 said: @saarg I nuked both the image and the data and started fresh with latest. Looks like postgres needs to be brought up to v11. 2019-03-05 07:49:20.931 AWST [79942] FATAL: database files are incompatible with server 2019-03-05 07:49:20.931 AWST [79942] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 10.5. We tested it here starting blank and didn't have that issue. Postgres 10.5 is in the current container based on alpine 3.8. We pushed an image based on alpine 3.9 that uses Postgres 11. So it looks like you didn't use the latest container when you start fresh again. Will check it when I get home.
March 5, 20197 yr 19 hours ago, tjb_altf4 said: @saarg I nuked both the image and the data and started fresh with latest. Looks like postgres needs to be brought up to v11. 2019-03-05 07:49:20.931 AWST [79942] FATAL: database files are incompatible with server 2019-03-05 07:49:20.931 AWST [79942] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 10.5. 7 hours ago, steve1977 said: Just saw another docker update available, which I did. Error message now as below: 2019-03-05 19:46:28.148 CST [419] FATAL: database files are incompatible with server 2019-03-05 19:46:28.148 CST [419] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 10.5. It's working here, so you have somehow used the container that used postgres 11 to initialize the database, then updated the container to the current one that uses postgres 10.5.
March 6, 20197 yr 5 hours ago, saarg said: It's working here, so you have somehow used the container that used postgres 11 to initialize the database, then updated the container to the current one that uses postgres 10.5. I'll nuke my install again and see how I go, it must have pulled the image just before it was updated.
April 2, 20197 yr Hello! I installed the Musicbrainz server locally on my unraid server. The databases have updated, and I see that they are updating regularly. My problem now is that Picard continues to ask for an authorization code to access the server. I've authorized Picard to work on the Musicbrainz website, and added the auth code. However, it still won't work with my local server. The error codes are as follows: E: 12:16:15,369 webservice._handle_reply:383: Network request error for http://10.0.30.200:5000/oauth2/token: Error transferring http://10.0.30.200:5000/oauth2/token - server replied: Bad Request (QT code 302, HTTP code 400) E: 12:16:15,371 oauth.on_refresh_access_token_finished:125: OAuth: access_token refresh failed: b'{"error_description":"Invalid protocol, only HTTPS is allowed","error":"invalid_request"}' E: 12:16:23,738 webservice._handle_reply:383: Network request error for http://10.0.30.200:5000/ws/2/collection: Host requires authentication (QT code 204, HTTP code 401) E: 12:16:23,739 ui.mainwindow.set_statusbar_message:326: Error loading collections: Host requires authentication I'm currently using Picard 2.1.3. Is this a problem with Picard or my server install? If I'm reading the error messages correctly, it seems like it wants my musicbrainz server to be an https:// connection. Any ideas?
April 3, 20197 yr OK I think I replicated your problem, you don't need to login with a musicbrainz account. Just add the server address and port of you musicbrainz docker and "make it so" (apply) and it'll start using your musicbrainz docker, nothing else is required to get it going.
April 3, 20197 yr 8 hours ago, tjb_altf4 said: OK I think I replicated your problem, you don't need to login with a musicbrainz account. Just add the server address and port of you musicbrainz docker and "make it so" (apply) and it'll start using your musicbrainz docker, nothing else is required to get it going. Yep, that got it! Now, I've just got to get the file permissions squared away. Now, I can't save the changes that Picard wants to make. I'll figure it out eventually.
April 13, 20197 yr On 11/18/2017 at 4:38 PM, DZMM said: yes, you can use the local database rather than musicbrainz.org for picard. It's also useful for the beets docker which is faster and more controllable than picard, and has a lot more functionality. If you use picard, you should give beets a go https://www.linuxserver.io/2016/10/08/managing-your-music-collection-with-beets/ It took me over a year since your reply, but I now indeed turned into an active user of beets. I am running beets on same local IP as Unraid (bridge mode). I am running MBZ docker on a separate local IP (br0 mode). Beets is working well, but I cannot get it to use the MBZ docker. I followed the configuration (https://beets.readthedocs.io/en/v1.3.17/reference/config.html#musicbrainz-options) and added MBZ info (musicbrainz: host: docker-IP:5000 ratelimit: 100). Unfortunately, this doesn't seem to be working and Beets docker cannot access MBZ docker. Any thoughts?
May 16, 20197 yr Has anyone been able to get this working, and if so how did you do it. I have tried every variation of settings and permissions but can't get it to work. Stops at unable to find/access the postgresql.conf file.
May 16, 20197 yr 20 minutes ago, beaglenz said: Has anyone been able to get this working, and if so how did you do it. I have tried every variation of settings and permissions but can't get it to work. Stops at unable to find/access the postgresql.conf file. It needs to support the new database schema they released. Not sure if it will be fixed if a new version is built or we have to do anything. I'll check it.
Archived
This topic is now archived and is closed to further replies.