Search Engine: Elastic

Article ID: 131344, created on Aug 22, 2017, last review on Aug 22, 2017

  • Applies to:
  • Operations Automation

Symptoms

After some massive logparser service reconfiguration (example: Awstats server migration, massive launch of pem.syncServiceConfiguration API calls, etc.), the logparser configuration is broken across a number of service nodes.

config.xml file located inside etc/logparser subdirectory of OA home folder contains wrong service ID and wrong log files definitions.

The Dump logparser service task was generated with correct parameters and succeeded.

Cause

The behavior is recognized as a product issue with ID POA-112650 (Parallel execution of Dump logparser service tasks results in broken logparser configuration)

Resolution

  1. Download fix_logparser_config.py script to the Management Node.
  2. Run the script:

    # python fix_logparser_config.py
    

The script takes ~1 hour to process 500 service nodes.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF