-
Tips for BADXML files
Hi guys,
I had recurrent problems with some servers generating a lot of BADXML files. The solution for common problems helped (changing the encode type), but I have another tips to share with you:
1. Check if the modules in /etc/pandora_agent.conf have *at least* this lines for each module:
module_begin
module_name
module_type
module_exec
module_description
module_endI don’t have sure, but you should keep the lines in this order to avoid BADXML.
2. Check if you have a return data value equal to “0.00”. I don’t know why (maybe a bug?) but all my agents that have this return value generate a BADXML. So, I change this to simply “0” and the XML worked perfectly.
I hope this tips help you guys. For the pandora staff, I suggest to put this in the “Solution to commom problems” area.
obs: Still using version 2.0… 🙁
Regards.
-
8 Replies
-
-
-
Hi everybody.
Another chapter with bad_xml files.
I have 2 servers that always give me some bad_xml files (about 3 or 4 per day). I have tried a lot of changes to get rid of them, but with no success..
Yesterday I tried to change the encoding only of the badxml files, change their names (removing the badxml suffix) and got them processed successfully. After change the encoding in the pandora_agent.conf of the monitored servers, I’m still getting some badxml files…
I don’t know why, but some files (from the same server) are only successfully processed when alternating between UTF-8 and iso-8859-1… (iso-8859-1 not -15)
My last try was to remove the first line of the badxml files (this line has just the encode type and xml version) and rename them (remove the badxml suffix). After that, all of them were successfully processed.
Is it possible that the monitored servers use the wrong encode type from time to time?
I will try some other changes in encoding type from this agents and let you know the results.
obs: Actually I have a monitor to show me how many badxml files I have in the server 😉
obs2: I attached 2 of the badxml files (before I removed the first line to get them processed).Regards.
-
-
Hi Nil
I’m little late with this… Still using version 2.0…
I have changed the encoding type and restarted the agents on the 2 servers yesterday. Until now, no badxml files.
It’s worth emphasize the necessity to restart the pandora agent after change the encoding type to make the changes valid.
I will keep you updated about this issue. Thanks.
-
News:
Without any explanation, some servers start to generate badxml… I tried to remove the first line of the xml file (), rename the file to remove the BADXML suffix and the pandora server can process the file successfully…
Any idea about what is happening? The badxml files come and go without any change in the configurations…
Nil, I’m still using 2.0 version… (shame on me).
-
-
Hi Manu. Thanks for your reply.
I didn’t noticed any change in the OSes… I’m using CentOS in most of the servers where this problem happens. I will investigate further the cron jobs (some oracle jobs) but until now, I coul’d isolate this problem…
One add about this issue: If I remove the first line of the xml file OR change the encoding type (sometime from iso to utf other times from utf to iso) the pandora server process the file without problem. If a force the encoding type in the pandora_agent.conf, the problem happens again after a random slot of time…
As soon as I got some free time, I will upgrade pandora 😉
