The services fail to start after editing the table-map.xml or index-concentrator-custom.xml files
Originally Published: 2014-11-23
Last Modified: 2023-10-06
Article Number
Applies To
RSA Product/Service Type: Log Decoder, Concentrator
RSA Version/Condition: 10.3.x
Platform: Platform (Other): CentOS
Issue
Module logdecoder failed to load: Diagnostic information: Throw in function nw::XmlNode& nw::XmlDocument::pop()
Dynamic exception type: nw::XmlError
std::exception::what: ERROR: pop() - XmlDocument stack is empty.
[boost::errinfo_at_line_*] = 1499
[boost::errinfo_file_name_*] = /etc/netwitness/ng/envision/etc/table-map-custom.xml
Cause
Resolution
Example:
Login to an ssh session on the Log Decoder and then execute the following command:
xmllint validate /etc/netwitness/ng/envision/etc/table-map.xml
Login to an ssh session on the Concentrator and then execute the following command:
xmllint validate /etc/netwitness/ng/index-concentrator-custom.xml
You may refer Meta not available on device' is displayed in RSA Security Analytics investigations for the correct procedure to add a custom log meta key in 10.3.x.
Note : Its advisable to backup a copy of the file prior to making any changes.
Related Articles
Error when importing security questions xml file in RSA Authentication Manager 8.x 49Number of Views AdminServiceException when attempting to import partner metadata xml file. 13Number of Views Select Hardware Tokens for Provisioning 48Number of Views Importing a token via CT-KIP fails indicating that the token already exists 94Number of Views Distribute One Software Token Using File-Based Provisioning 52Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?