[#MBS-4133] Internal server error editing recording - MusicBrainz JIRA

MusicBrainz Server

Internal server error editing recording

Created: 06/Jan/12 10:47 AM Updated: 07/Feb/12 12:21 PM Due: 06/Apr/12 Resolved: 07/Feb/12 12:21 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

Bug Fixes, 2012-02-20

Description

« Hide

I just got several internal server errors while trying to edit recordings to add disambiguation comments. Unfortunately beta doesn't show error messages, only "Error message: (No details about this error are available)", so I can't provide any more information about the error. Perhaps there's a log somewhere which has the error.

These happened around the same time that I got rate limit errors (see ~~MBS-4132~~), so it could be related.

Sort Order:

[ Permalink | « Hide ]

Oliver Charles added a comment - 06/Jan/12 05:35 PM

The bug has been resolved as beta wasn't using the right packages. However, I'm leaving this open as I can reproduce it on my own machine.

[ Permalink | « Hide ]

nikki added a comment - 06/Jan/12 11:02 PM

Note that this wasn't a consistent error - only some of the edit recording pages got it and it went away when I refreshed, hence why I think it might be related to the rate limiting errors I got on other pages at the same time.

[ Permalink | « Hide ]

Oliver Charles added a comment - 08/Jan/12 03:32 PM

The repository HEAD of HTML::FormHandler apparently doesn't cause this problem, but I need to confirm.

[ Permalink | « Hide ]

Oliver Charles added a comment - 09/Jan/12 02:31 PM

I can confirm that this is fixed with the latest HTML::FormHandler. I will leave this open until that gets released though.

[ Permalink | « Hide ]

Kuno Woudt added a comment - 30/Jan/12 03:11 PM

As Oliver claims this issue is fixed, I'm assigning this to him.

(now that we're using carton, I guess the fix is to set the correct version for HTML::FormHandler in carton.lock, if this has been done in master I think this ticket can be closed).

[ Permalink | « Hide ]

Oliver Charles added a comment - 03/Feb/12 02:57 PM

This upgrade requires us to move to Moose 2, which means all the memory cycle tests fail. What shall we do? I'm tempted to just nuke them tbh, as we have a "solution" for fixing the memory leaks.

[ Permalink | « Hide ]

Oliver Charles added a comment - 06/Feb/12 08:48 PM

Agreed to launch ze missiles and remove memory cycle tests in http://chatlogs.musicbrainz.org/musicbrainz-devel/2012/2012-02/2012-02-06.html. Upgrade to moose 2.