Changed the Acoustid Api-Key -> same result. That happens at least since yesterday
Wrong Acoustid Api-Key?
I just tried myself and it appears to work correctly
Are you using 11.7 Jaikoz 11.7 Idles released May 22nd 2023 ?
There was a change made by Acoustid that recently broke fingerprinting because changed max match size from 20 to 10 but gave misleading error message, and 11.7 is needed to resolve that.
I use Jaikoz 11.7 released May 22nd 2023
but take a look at
At least the text of the error message points in the wrong direction
Okay thanks, does the problem only occur when trying to submit fingerprints fot songs that not currently on acoutid database?
Okay seems problem is with Acoustid - https://community.metabrainz.org/t/acoustid-server-replied-internal-server-error-for-submission/641670
But from your log extract it may just be there is issue when trying to link mbids, acoustids for newly matched release back to Acoustid, I.e it should not affect matching I think, so I would let it continue to run.
Hey,
this thread is maybe better to report the issue I reported in my other post.
A quick 1 minute analysis of the logs :
root@Tower:/mnt/cache/appdata/songkong/Logs# tail -f songkong_user0-0.log |grep "Check Api"
19/06/2023 21.43.00:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.05:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.06:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.13:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.21:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.28:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.29:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.30:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.30:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.32:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.40:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.43:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.53:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.43.56:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.09:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.14:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.17:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.23:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.30:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.34:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.38:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.38:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.40:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
19/06/2023 21.44.43:CEST:SEVERE: --Acoustid Submission Failed Check Api Key:lj5NgggIwD
I think there is still an issue, right ?
The message is suggesting you check the api key because problem occurring, but I dont think there is actually anything wrong with your api key, but there is an issue with Acoustid, I cannot fix that as I dont run AcoustId.
But i think the issue is only when submitting data to Acoustid, I dont think it affects lookup acoustids.