-
pandora_agent.config max min bug
Hi everybody,
I have an agent with lots of modules configured inside pandora_agent.conf with max and min boundaries defined. This agent reports a lot of _BADXML. I’m suspicious about a bug involving this boundaries. When I remove the max and min, and remove de _BADXML from the filename, the pandora server consumes the data files without error.
The data reported by all the modules are between the max and min values.
I double checked the encoding parameter and did lots of tests. All of them pointed to the min/max thresholds as a problem.
I checked the pandora_server.error and the message below appears a lot of times (the argument changes in each line).Argument “3469709r69r3469640” isn’t numeric in sprintf at /usr/lib/perl5/site_perl/5.8.8/PandoraFMS/DB.pm line 905.
Attached an example of a badxml file.
ps: the values between boundaries returned by the agent where integers.
ps2: sorry about the long post… -
8 Replies
-
-
-
Hi everybody,
Thanks for the replies.
Raul, I’m using the 2.0 linux version (agent and server). I tested with 1.3 agent, but the problem remains the same.
Thank you Manu, but the missing “-” was a problem in copy and paste of the file here… 🙁 The original file had the correct string “encoding iso-8859-15”
By the way, I did a script with sed to remove all the max/min lines from the _BADXML files and renamed them (more than 300 files). After that, the server consumed all the files with no problem….
I stripped off the max/min lines from the pandora_agent.conf and, the problem disappeared. If you want to know more about this issue, I can put back the lines to see the problem again, just let me know.
Regards.
-
We have tested it here and it works with no problem.
You said the server you’re running is the one shipped in the VM or did you installed from packages? You might want to update yourself using the server code in the SVN (branches 2.0), if you want help with this, let me know and I can help you through the process. -
-
-
Thank you Manu, I will update to this branch.
By the way, today I arrived at my work and see 12 badxml files from the same agent… This time, there were no max/min parameters (I removed them the last time the problem appeared). I think this issue could be related with this specific machine. I will update to the branch and post here if this occurs again.
Thank you anyway and attached is an example of the badxml file (this time copied directly from the server to avoid copy/past typing error) 😉
