Fatal Error in Metadata retrival

Hi there,
i'm new to serviio and played arround with it for like 6 days now.Everthing worked fine, i just loved the metadata-online-plugin but since yesterday no new tv-shows were added so i digged into it myself and found this

  Code:

[Fatal Error] b06293f7-dbcb-4f63-90e4-c65ddd4d578a:2:1: Content is not allowed in prolog.
[Fatal Error] 22a881ec-b80e-451c-ae8f-026e0212a894:2:1: Content is not allowed in prolog.
[Fatal Error] 9e443d31-8b27-4a4d-954d-a974388ad4ca:2:1: Content is not allowed in prolog.
[Fatal Error] 9312b2b1-3d1c-4434-b9e6-630bb643e387:2:1: Content is not allowed in prolog.
[Fatal Error] 96fec7fd-06d7-4fc8-9569-036be52301db:2:1: Content is not allowed in prolog.
[Fatal Error] 0e903216-8e5f-406e-9449-e81fdbb53983:2:1: Content is not allowed in prolog.
[Fatal Error] 77e616b5-aa8e-49a0-ba15-d514abd86738:2:1: Content is not allowed in prolog.
[Fatal Error] f4c40a91-5899-4495-8bed-88f3f028b1ac:2:1: Content is not allowed in prolog.
[Fatal Error] 2b78c3a5-4836-4d93-94e5-358de0bd8af1:2:1: Content is not allowed in prolog.
[Fatal Error] 4f9cd572-a7ad-4431-95a1-8651427e16ac:2:1: Content is not allowed in prolog.
[Fatal Error] f008caf3-786c-49cf-9bbd-6a1b5e23e10e:2:1: Content is not allowed in prolog.
[Fatal Error] 23bf4d4f-a72b-4e92-81d0-96ce20def3e9:2:1: Content is not allowed in prolog.
[Fatal Error] 0b02fab2-7095-41d1-8169-4b9977320c0a:2:1: Content is not allowed in prolog.
[Fatal Error] 078136df-ba6c-4ba2-b036-b762ee599fa3:2:1: Content is not allowed in prolog.
[Fatal Error] 9b68ac75-e771-47f7-98bb-11ee3bcc5954:2:1: Content is not allowed in prolog.
[Fatal Error] ac6094dd-52d6-4f5b-a2e1-41ebca40699a:2:1: Content is not allowed in prolog.
[Fatal Error] 58cad14c-1dea-4120-b82b-60599e835f0a:2:1: Content is not allowed in prolog.
[Fatal Error] c6cc7215-381a-412f-960b-77c868e21907:2:1: Content is not allowed in prolog.
[Fatal Error] 2fadf468-1269-4b2e-a965-f8313fcebd14:2:1: Content is not allowed in prolog.
[Fatal Error] 8b48c5fc-69ff-4b81-a211-c2ea82b470ca:2:1: Content is not allowed in prolog.
[Fatal Error] 4f32fc66-da3a-4963-bea2-7a3c06b8b4c4:2:1: Content is not allowed in prolog.
[Fatal Error] d06ea448-9e34-45c6-8cdc-6c9bf43e8470:2:1: Content is not allowed in prolog.
[Fatal Error] 06693e5c-4e69-4617-b55e-126bd5e161a2:2:1: Content is not allowed in prolog.
[Fatal Error] 8ed76eb6-fc0f-45da-adbd-f176a0d4e5ec:2:1: Content is not allowed in prolog.
[Fatal Error] 3ce7a721-3748-4bf8-91fe-828a64086232:2:1: Content is not allowed in prolog.

Which happens to me with the "Filebot" which is posted elsewhere on this board while scanning for a show for the first time.If i scan second time everything works fine.
Maybe thetvdb.com changed the api or something like that, i just would love to see this back working again soon.With my like 100 tv-shows with approx. 10000 files this feature was the major point for getting serviio.

Kind regards and merry x-mas
Tamrael

PS: I'm sorry for any bad language or gramma-errors, this is not my native language

EDIT:
Ok so i just thought ... stop being the stupid enduser and give some more infomations like you would like for your own projects.
Systeminfo: Linux Serviio 1.1 with ffmpeg compile by hand like in wiki
Loginfo:

  Code:

DEBUG [TheTVDBSourceAdaptor] Searching for series 'navy cis'
DEBUG [TheTVDBSourceAdaptor] No series with the name has been found
DEBUG [TheTVDBSourceAdaptor] Searching for series 'ncis s06'

repeating for every show and every episode cause i rescanned the whole folder(delete/readded it) allong the way to get more info's about the problem.Api-documentation from thetvdb.com doesn't talk about this prologue shit as far i read about it and the whole thing kind of gets disturbing.If anyone needs more info's just ask and no my edit is not a sign of impatience but i just know what it's like to be the one who has to figure out the matter and wanted to give more infos.take your time i'm off to sleep and again merry x-mas to all of you

[zip]

The error above doesn't look like Serviio error. Is it from the script? This normally happens when trying to parse an illegal XML document, e.g. empty, dodgy first character or a normal text file when xml is expected.

the error mentioned above is not displayed in serviio log but by the serviio.sh itself which runs in a screen on the unix system.
i know it's not really a problem from serviio an the cause seems to be a malformed xml returned by thetvdb.com.
that's why i thought they maybe thanged there api but i couldn't find any news on there site to explain those changes.

[zip]

Did you try to make the api call in your browser to see what comes back? Might be the service is down.

Good point i will check later what comes back from api-calls directly, but filebot doesn't have that problem when scanning thetvdb.com for shows and episodelists.
Anyway thank you for your time i will report back later with the results of the api-calls

EDIT: Ok to get things back on the line...thetvdb.com had to move there server's and for that there was a minor downtime, i just dropped every other scanjob for metadata(movies etc.) and now the tv shows are scanned ok again.For more background click here they seem to have a major money problem over there monthly bandwidthusage.

EDIT2: For me this Topic is solved, thank you for your quick replys Zip