Topic: Bad Gateway

I'm trying to load an album into Picard:

http://musicbrainz.org/release-group/69 … 2810ee872c

However, the album fails to load and the log shows a Bad Gateway error

E: <sip.voidptr object at 0x035B7B90> 00:33:41 u'Error downloading http://musicbrainz.org:80/ws/2/release/ … level-rels - server replied: Bad Gateway'

I've tried to open the error's URL in a browser (chrome), and get the same error:

502 Bad Gateway

nginx/0.7.65

How do I go about getting this problem fixed? Is the data in the DB corrupt? Is there an issue with the API? Is it a problem with the number of tracks in the release (116), or is the code choking on an extended character, or is something else weird and wonderful happening?

Re: Bad Gateway

It's a problem with the number of tracks in the release and the amount of relationships they have themselves. Picard is trying to load a crapton of data and choking. Disable "use track relationships" (or something similar, can't remember the exact wording), tag, re-enable. Of course, that means it won't get composer tags... but at least it'll get the rest.

Re: Bad Gateway

Thanks, that did the job.

Re: Bad Gateway

The problem is not limited to picard. There are some releases also which don't display on the webpage as well, see e.g. http://musicbrainz.org/release/9c5c043e … af9c81e6dc

In any case, it is not picard fault, it is rather overload (or some limits) of the server.