Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Active IQ Unified Manager Discussions

NetApp-Harvest Poller Failing: NaServer::parse_xml - Error in parsing xml:


I'm attempting to monitor a pair of arrays running 8.1.4 7-Mode.  The poller reports the follwoing in the log file:


[2015-12-01 09:03:49] [NORMAL ] WORKER STARTED [Version: 1.2.2] [Conf: netapp-harvest.conf] [Poller: fitn11p011]
[2015-12-01 09:03:49] [NORMAL ] [main] Poller will monitor a [FILER] at [fitn11p011:443]
[2015-12-01 09:03:49] [NORMAL ] [main] Poller will use [password] authentication with username [netapp-harvest] and password [**********]
[2015-12-01 09:03:50] [NORMAL ] [main] Collection of system info from [fitn11p011] running [NetApp Release 8.1.4 7-Mode] successful.
[2015-12-01 09:03:50] [NORMAL ] [main] Using best-fit collection template: [7dot-8.1.0.conf]
[2015-12-01 09:03:50] [NORMAL ] [main] Using graphite_root [netapp.perf7.DC11.fitn11p011]
[2015-12-01 09:03:50] [NORMAL ] [main] Using graphite_meta_metrics_root [netapp.poller.perf7.DC11.fitn11p011]
[2015-12-01 09:03:50] [NORMAL ] [main] Startup complete.  Polling for new data every [60] seconds.
[2015-12-01 09:04:30] [WARNING] [cifs_stats] update of counter_list cache failed with reason: NaServer::parse_xml - Error in parsing xml:
unclosed token at line 4, column 14717, byte 14876:
<!DOCTYPE netapp SYSTEM '/na_admin/netapp_filer.dtd'>
<netapp version='1.1' xmlns='http://www.netapp.com/filer/admin'>
<results status="passed"><counters><counter-info><name>instance_name</name><desc>Instance Name</desc><privilege-level>diag</privilege-level><properties>string</properties><unit>none</unit></counter-info><counter-info><name>node_name</name><desc>System node name</desc><privilege-level>diag</privilege-level><properties>string</properties><unit>none</unit></counter-info><counter-info><name>instance_uuid</name><desc>Instance UUID</desc><privilege-level>diag</privilege-level> . . .
at /usr/lib/perl5/XML/Parser.pm line 187.

[2015-12-01 11:24:16] [WARNING] [disk] data-list update failed.
[2015-12-01 11:45:11] [WARNING] [system] update of data cache failed with reason: Timeout. Could not read API response.
[2015-12-01 11:45:11] [WARNING] [system] data-list poller next refresh at [2015-12-01 11:45:00] not scheduled because it occurred in the past
[2015-12-01 11:45:11] [WARNING] [system] data-list update failed.

Any ideas?





The Data ONTAP API interface packages uses XML and from this error there was a failure to parse some response.  I suspect some kind of network failure caused the XML document to get truncated which resulted in a failure to parse it and that error.  If you see it often I would suspect network errors or instability in the network are to blame.


Maybe you can take a packet trace or use other network troubleshooting techniques to research deeper?



Chris Madden

Storage Architect, NetApp EMEA (and author of Harvest)

Blog: It all begins with data


P.S.  Please select “Options” and then “Accept as Solution” if this response answered your question so that others will find it easily!

NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner