Support Center > Search Results > SecureKnowledge Details
Indexes are not created for Firewall and VPN blade Technical Level
Symptoms
  • Indexes are not created for Firewall and VPN blade for gateways that logging to this specific machine, while non-indexed logs look fine - all blades all gateways are visible.

  • The indexer.elg file shows:

    [DATE] msg: SolrCore 'firewallandvpn_' is not available due to init failure: Could not load core configuration for core firewallandvpn_<date>
    [DATE] trace: org.apache.solr.common.SolrException: SolrCore 'firewallandvpn_<date>' is not available due to init failure: Could not load core configuration for core firewallandvpn_<date>
    SolrException: Error loading solr config from /opt/CPrt-R80/rfl_server/solr/configsets/firewallandvpn/solrconfig.xml
    [DATE] SolrClient::Implementation::ParseJavaBinReply Bad Java bin format
    [DATE] RFLIndexDoer::sendToSolr: Send error occurred(19,19). Tried 2 out of max 2
    [DATE] RFLIndexDoer::Partial_Buf_Process: The following log is not accepted by solr (file = @A@@B@1556689950 position = 16579102) :<doc>

    Caused by: org.apache.solr.common.SolrException: Error loading solr config from /opt/CPrt-R80/rfl_server/solr/configsets/firewallandvpn/solrconfig.xml
    at org.apache.solr.core.SolrConfig.readFromResourceLoader(SolrConfig.java:148)
    at org.apache.solr.core.ConfigSetService.createSolrConfig(ConfigSetService.java:79)
    at org.apache.solr.core.ConfigSetService.getConfig(ConfigSetService.java:61)
    ... 49 more
    Caused by: org.apache.solr.common.SolrException: Value of 'maxMergeCount' can not be parsed as 'int': "2.5"
    at org.apache.solr.util.DOMUtil.addToNamedList(DOMUtil.java:167)
    at org.apache.solr.util.DOMUtil.nodesToNamedList(DOMUtil.java:106)
    at org.apache.solr.util.DOMUtil.childNodesToNamedList(DOMUtil.java:96)
    at org.apache.solr.core.PluginInfo.< init >(PluginInfo.java:52)
    at org.apache.solr.core.SolrConfig.readPluginInfos(SolrConfig.java:345)
    at org.apache.solr.update.SolrIndexConfig.getPluginInfo(SolrIndexConfig.java:197) ...


  • If manually replacing the solrconfig.xml file from /opt/CPrt-R80/rfl_server/solr/configsets/firewallandvpn/conf/ to /opt/CPrt-R80/rfl_server/solr/configsets/firewallandvpn/ And restart the Indexer with evstop;evstart:

    • New FirewallAndVpn folder is recognized under the log_indexes for the current date
    • New indexed logs are visible in SmartConsole, but refreshing the view shows the logs time lagging from the current time and soon the indexer process will stop to create a new indexes.

  • No FirewallAndVpn folder under the log_indexes directory.

Cause
  1. The exception seen in the log_indexer.elg and solr.log files point to a Integer parsing error:
    Caused by: org.apache.solr.common.SolrException: Value of 'maxMergeCount' can not be parsed as 'int': "2.5"

    This seems to start the chain of exceptions that leads the SOLR to look for the solrconfig.xml at a wrong place.

  2. The maxMergeCount is a variable that hold the number of threads used for merging the SOLR core segments. SOLR code expects this variable to be an integer, when the value is a float number the exception is caused. The value of maxMergeCount is read from the file $FWDIR/conf/serverSettings.props.

    In this case the value is 2.5 - RFL_SOLR_MAX_MERGE_COUNT=2.5


  3. The default value is in the solrconfig,xml file, that value gets override with the value in -$CPDIR/conf/CpSetupInfo_resourceProfiles.conf according to the specific machine profile.

    For example:

    :complex_expression (
               :name (RFL_SOLR_MAX_MERGE_COUNT)
       :type (numeric)
       :default (2)
       :condition_exp ("CPU_NUMBER == 2")
       :false_exp ("2 MAX CPU_NUMBER / 2")
       :true_exp (2)
    )

Solution
Note: To view this solution you need to Sign In .