Pandora FMS Community

Unable to process XML data file

mjohnson · 16 sept 2014, 3:47 · 10 mensajes · 94 visitas

  1. Inicio del debate

    Pandora FMS server is unable to parse agent upload xml file. The event reads: Unable to process XML data file '/var/spool/pandora/data_in/GSM-SBS-01.8360.data': not well-formed (invalid token) at line 2, column 178, byte 218 at /usr/lib64/perl5/XML/Parser.pm line 187 thread 1 What is odd is it is on line 2 but I am betting it is because of the circle R character (registered symbol, in Microsoft Windows) but I don't know how to fix or work around the issue. Can anyone help me with this issue?

  2. Hi, I think it's a problem of windows agent in that particular version. We will patch it and send you a link to a modified version of windows agent ASAP. a greeting Sergio

  3. Until we can fix it, let's try another thing: Are you using UTF-8 encoding in the agent?, try to set the UTF8 encoding, restart the agent and see it works.

    Pandora FMS server is unable to parse agent upload xml file. The event reads: Unable to process XML data file '/var/spool/pandora/data_in/GSM-SBS-01.8360.data': not well-formed (invalid token) at line 2, column 178, byte 218 at /usr/lib64/perl5/XML/Parser.pm line 187 thread 1 What is odd is it is on line 2 but I am betting it is because of the circle R character (registered symbol, in Microsoft Windows) but I don't know how to fix or work around the issue. Can anyone help me with this issue?

  4. Thanks smartin, I'd appreciate that. Sancho, the agent is already configured to use encoding UTF-8  :( I even tried using the update agent recently pushed to nightfiles but had the same results. Thanks for you interest in this, both of you. Since I found Pandora FMS I've really been excited about this project and very much would like to get it working in our environment, as it would be great for when we grow enough to require Enterprise. Our current monitoring solution isn't terrible but it isn't great either, and I desperately desire to migrate to a better offering.

  5. Thanks for the feedback :) Please, send me (using wetransfer or any other system) a sample of your problematic XML file and the agent conf file, so we can see what is the problem, with UTF8 encoding it should work ! :( Send me directly my mail to slerena ( ~ ) artica (dot) es Thx!

    Thanks smartin, I'd appreciate that. Sancho, the agent is already configured to use encoding UTF-8  :( I even tried using the update agent recently pushed to nightfiles but had the same results. Thanks for you interest in this, both of you. Since I found Pandora FMS I've really been excited about this project and very much would like to get it working in our environment, as it would be great for when we grow enough to require Enterprise. Our current monitoring solution isn't terrible but it isn't great either, and I desperately desire to migrate to a better offering.

  6. Sancho, you should be receiving an email from me shortly

  7. Updating this discussion, so that any else affected may find this useful. Changing the encoding parameter value to ISO-8859-1 corrected the issue, where the Pandora FMS server was unable to parse the XML file. However, with the agent processing the config file entries, I am now noticing a series of errors within event viewer that correspond with the timing of the data collection performed by the agent - all relating to wmi (see below). In the Agent's detail console, I do see data returned but it is not reliable data and values often don't update for several cycles - or goes "unknown" - despite what is actually collected on the host. Additionally, when the agent performs the data collection, I see a huge spike in CPU resources (60%) that lasts 15 or seconds - on a quad-core xeon. I'll admit that I am collecting a good number of items (83 items precisely) but I don't think that is what's causing wmiprvse.exe to crash. Any thoughts? Log Name:      Application Source:        Application Error Date:          9/17/2014 3:14:00 PM Event ID:      1000 Task Category: (100) Level:        Error Keywords:      Classic User:          N/A Computer:      GSM-SBS-01.gsm.local Description: Faulting application name: wmiprvse.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d42 Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c Exception code: 0xc00000fd Fault offset: 0x0000000000173220 Faulting process id: 0x4518 Faulting application start time: 0x01cfd2ab8958270c Faulting application path: C:Windowssystem32wbemwmiprvse.exe Faulting module path: C:Windowssystem32ole32.dll Report Id: c75f4c69-3e9e-11e4-967e-00155d64f515 Event Xml:           1000     2     100     0x80000000000000         457273     Application     GSM-SBS-01.gsm.local             wmiprvse.exe     6.1.7601.17514     4ce79d42     ole32.dll     6.1.7601.17514     4ce7c92c     c00000fd     0000000000173220     4518     01cfd2ab8958270c     C:Windowssystem32wbemwmiprvse.exe     C:Windowssystem32ole32.dll     c75f4c69-3e9e-11e4-967e-00155d64f515   Log Name:      Application Source:        Windows Error Reporting Date:          9/17/2014 3:14:11 PM Event ID:      1001 Task Category: None Level:        Information Keywords:      Classic User:          N/A Computer:      GSM-SBS-01.gsm.local Description: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: wmiprvse.exe P2: 6.1.7601.17514 P3: 4ce79d42 P4: ole32.dll P5: 6.1.7601.17514 P6: 4ce7c92c P7: c00000fd P8: 0000000000173220 P9: P10: Attached files: C:WindowsServiceProfilesNetworkServiceAppDataLocalTempWER52FA.tmp.appcompat.txt C:WindowsServiceProfilesNetworkServiceAppDataLocalTempWER5359.tmp.WERInternalMetadata.xml C:WindowsServiceProfilesNetworkServiceAppDataLocalTempWER535A.tmp.hdmp C:WindowsServiceProfilesNetworkServiceAppDataLocalTempWER54D2.tmp.mdmp These files may be available here: C:ProgramDataMicrosoftWindowsWERReportQueueAppCrash_wmiprvse.exe_8953994f733d53b2314f667ac52799919c84fb3_cab_35be5711 Analysis symbol: Rechecking for solution: 0 Report Id: c75f4c69-3e9e-11e4-967e-00155d64f515 Report Status: 4 Event Xml:           1001     4     0     0x80000000000000         457274     Application     GSM-SBS-01.gsm.local                     0     APPCRASH     Not available     0     wmiprvse.exe     6.1.7601.17514     4ce79d42     ole32.dll     6.1.7601.17514     4ce7c92c     c00000fd     0000000000173220                     C:WindowsServiceProfilesNetworkServiceAppDataLocalTempWER52FA.tmp.appcompat.txt C:WindowsServiceProfilesNetworkServiceAppDataLocalTempWER5359.tmp.WERInternalMetadata.xml C:WindowsServiceProfilesNetworkServiceAppDataLocalTempWER535A.tmp.hdmp C:WindowsServiceProfilesNetworkServiceAppDataLocalTempWER54D2.tmp.mdmp     C:ProgramDataMicrosoftWindowsWERReportQueueAppCrash_wmiprvse.exe_8953994f733d53b2314f667ac52799919c84fb3_cab_35be5711             0     c75f4c69-3e9e-11e4-967e-00155d64f515     4

  8. Another update on this:: Doing further research into the appcrash events, I ran across this post that seems to hit the nail on the head. From the Post: "It turns out there is a hotfix for Windows 2008 R2 – which addresses a possible leak when an application queries the Win32_Service class frequently.  A monitoring tool would do this ... " http://blogs.technet.com/b/kevinholman/archive/2010/06/09/wmi-leaks-memory-on-server-2008-r2-monitored-agents.aspx (Link not available anymore) I will apply the hotfix and try to update this discussion with any findings

  9. I was unable to install the available hotfix - which wasn't cool, since I had to register before I was able to download. It failed to install, prompting that it was not meant for this platform. I figure it is doing a platform check, querying the registry and expecting Windows Server 2008 R2 (or the build number) but it is, instead, retrieving Window Small Business Server 2011 Standard (which is built on 2008 R2). In any case I was able to locate a number of web pages with descriptions of this issue (memory leaks when querying WMI provider Win32_Service class many times in one go) and I am still confident in this theory. As a workaround, I tried following this: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx However, I am still experiencing the same results Application log errors from wmipvse.exe appcrash ole.dll But now I also receive others, same event but the faulting module is ntdll.dll and a few others. It should be noted that I am not experiencing this issue on my other lab server, which runs Windows 2008 R2 server My next step is to try executing the modules in varied intervals using module interval, as the agent runs all checks every 15 minutes. I hope this works because I don't know what else to try.

  10. OK, just so this discussion is as complete as possible ... here's the results of my troubleshooting. The condition was caused by the number of checks I was attempting to conduct using this agent. After reducing the number of checks, targeting windows services, no further events have been logged. This isn't a devastating condition, as I can live with the resulting level of monitoring, but it does mean that, since this issue exists within the OS, I will not be able to gain the degree of visibility I was intending -- but I can't find any evidence where this is an issue relating to the Pandora FMS agent.

Entra en tu cuenta para publicar.