Skip to main content
NetApp Knowledgebase

AutoSupport bundle in ONTAP are not creating - notifyd error 'Entity: line 3: parser error'

Views:
100
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • All Clustered Data ONTAP versions prior to ONTAP 9.3 
  • Data ONTAP 7-Mode prior to 8.2.5

Issue

  • AutoSupport messages are not sent to NetApp and no new AutoSupports are listed in the output of an

autosupport history show -node node_name  command.

  • The autosupport invoke command appears to work, but the AutoSupport is not generated:

Cluster01::> autosupport invoke -node Cluster01-01 -type test

  • The AutoSupport was successfully invoked on node "Cluster01-01" (sequence number: 123).

     Cluster01::> autosupport history show -node Cluster01-01 -seq-num 123
There are no entries matching your query.

  • Checking notifyd.log shows massive amounts numbers of errors similar to the following:

Mon Jun 04 2018 10:46:49 -07:00 [kern_notifyd:info:10003] fromXML: Could not parse XML.
Mon Jun 04 2018 10:46:49 -07:00 [kern_notifyd:info:10003] Entity: line 3: parser error : xmlParseCharRef: invalid xmlChar value 7
Mon Jun 04 2018 10:46:49 -07:00 [kern_notifyd:info:10003] message="1 login failure on console, "/>

Note: the xmlChar value above may be different, as well as the message= portion.

To inspect the notifyd.log file, run the following:

7-Mode:
> rdfile /etc/log/mlog/notifyd.log
 

Clustered Data ONTAP/ONTAP:
::> system node run -node Cluster01-01 rdfile /etc/log/mlog/notifyd.log

Note: Due to the nature of this issue, these log files will be very large

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support