Closed zantharax closed 8 years ago
Could it be that you had some connectivity problems at some stage? This error indicates that the XML we got from CCP was corrupt/invalid/empty.
No, I doubt so. These are the only errors that occur and they trigger very predictably. This happens on 13 specific keys, every time I run them. Could it be something in a mail that these 13 accounts have that is causing issues when parsing the API pull?
If it is that predictable, could you have a look at the XML that is on disk and reply with it here?
Sorry, I'm not sure how to go about that. I've tried to go through the mailboxes stored for a pair of these keys, and compare it to a key that is not generating this error, but cannot find any mails unique to these keys that could contain the error.
If you have anywhere else to look, or a better way to identify where the problem may be I would be more than happy to do so.
If you look in /var/www/seat/app/storage/cache/phealcache/KEYID/VCODE/char you should see directories for the various things pulled by that key, and in those directories xml files.
The directory is slightly different than what you described - /var/www/seat/storage/app/pheal/(KEYID)/(VCODE)/ However, the /char/MailBodies/ directory is empty of any files.
Looking at known-good keys, this directory appears to be removed (perhaps this is done after mails are parsed). I've have tried clearing the cache, and specifically removed the /Mailbodies directory, but it is recreated on the API Query run. Permissions look good as well, 777 to www-data (the user seat is running as).
Sorry I gave you the path for 0.x not 1.x
No worries, was able to poke around and find it.
After doing some more comparison, I was able to find the offending mail. In other API clients, I receive a Malformed XML error as well. I would suspect that the mail (which is bi-lingual) has some formatting or characters that is breaking out of XML and malforming the object.
I will try to get a copy of the mail from one the 13 users who got it and see if I can identify the issue.
Please paste the broken XML here as well as the mail messageID. Can try poke someone at CCP if needed.
It's an alliance mail, so I can't post it directly on here, but I the mail ID is 357801633.
This is a CCP problem for sure though - direct api queries for the mail generate errors. From the browser:
This page contains the following errors:
error on line 6 at column 343: Input is not proper UTF-8, indicate encoding !
Bytes: 0x0C 0x3C 0x62 0x72
Below is a rendering of the page up to the first error.
From a web-based parser:
Unable to parse any XML input. org.jdom2.input.JDOMParseException: Error on line 6: An invalid XML character (Unicode: 0xc) was found in the CDATA section.
Had a chat to CCP Tellus about this one, and there was no real indication on whether this will be looked at, yet alone fixed. So, for now I am going to wrap the error and just try handle in gracefully for now.
Problem Statement
After running API update for certain characters, an error is generated - "Last Updater: Processing: MailBodies"
Log Extracts / Proof
Output of
php artisan seat:admin:diagnose