PureDisk WEB GUI with error : org.xml.sax.SAXParseException: Content is not allowed in prolog

Article:TECH175893  |  Created: 2011-11-30  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH175893
Article Type
Technical Solution



Attempting to login to PureDisk web gui results in error message: "org.xml.sax.SAXParseException: Content is not allowed in prolog" instead of login/password prompts.

The error "org.xml.sax.SAXParseException: Content is not allowed in prolog" indicates a 'corruption' in the xml content. This may be the result of an error message being inserted into the data stream before tomcat receives the xml data.

As tomcat gui retrieves data from the PureDisk 'web services', the data returned from the web services needs to be reviewed to identify root cause.


org.xml.sax.SAXParseException: Content is not allowed in prolog




In this instance, the root cause was incorrect file permissions on /etc/puredisk/agent.cfg

However any error message from web services will cause the symptoms and it's the web services that needs to be investigated for root cause.


# chown www-data:www-data /etc/puredisk/agent.cfg

Supplemental Materials


Testing PureDisk webservices for correct operation using 'wget'


# wget --no-check-certificate https://<spa_hostname>/spa/ws/ws_agent.php?login=root

results in the following error message returned:

nr: 999999
severity: 6
source: SPA-Webservices_Agent
description: Application not yet initialized; latest captured error: [2]fopen(/etc/puredisk/agent.cfg): failed to open stream: Permission denied

Article URL http://www.symantec.com/docs/TECH175893

Terms of use for this information are found in Legal Notices