Google Search Appliance Feeds Protocol Developers Guide - Manual (Page 33)

Google Search Appliance: Feeds Protocol Developer’s Guide 33
Troubleshooting
Here are some things to check if a URL from your feed does not appear in the index. To see a list of
known and fixed issues, see the latest release notes for each version.
Error Messages on the Feeds Status Page
If the feeds status page shows “Failed in error” you can click the link to view the log file.
ProcessFeed: parsing error
This message means that your XML file could not be understood. The following are some possible
causes of this error:
• There is an error in the DOCTYPE line in your XML file. This line should be: PUBLIC "-//Google//DTD GSA Feeds//EN""">
• You have not escaped the ampersand or other reserved characters in a URL in your XML file.
• You have included content that requires base64 encoding. See “Providing Content in the Feed” on
page 11.
If none of the above are the cause of the error, run xmllint against your XML file to check for errors in
the XML. The xmllint program is included in Linux distributions as part of the libxml2 package.
The following is an example that shows how you would use xmllint to test a feed named full-
feed.xml.
$ xmllint -noout -valid full-feed.xml; echo $?
0
The return code of zero indicates that the document is both valid and well-formed.
If the xmllint command fails and displays the parsing error message, ensure that you have the
correct DTD file, or you can remove the -valid flag from the xmllint command line so that the
xmllint command doesn’t try to validate the XML file’s elements. For more information on the DTD, see
“Google Search Appliance Feed DTD” on page 41.
Feed Push is Not Successful
Before a search appliance can start processing a feed, you need to successfully push a feed to port
19900.
If the feed push is not successful, check the following:
• List the IP address of the computer that hosts the feed client in the List of Trusted IP Addresses.
For more information, see “Pushing a Feed to the Google Search Appliance” on page 27.
• Verify that the feed client connects to port 19900 on the correct IP address.
• Verify that port 19900 is reachable on the search appliance by running tracepath applianceIP/
19900 from the Linux command line.
• Check with your network team for firewall or connectivity issues to ensure access to port 19900.