Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-848

log-logstash logstash pipeline fails to start after oom standard config changes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Beijing Release
    • Beijing Release
    • None
    • None
    • OOM Sprint 10 - Integration

      After the oom standard configuration was committed for https://jira.onap.org/browse/OOM-740, the logstash pipeline was not mounted correctly so the logstash pipeline is failing to start. 

      The failure log message can be seen from the logstash container standard output: root@onap:/home/ubuntu# kubectl -n default logs --tail onap-log-logstash-d577b98b7-vh4jq

      [2018-03-29T18:07:22,257][ERROR][logstash.pipeline ] A plugin had an unrecoverable error. Will restart this plugin.
      Plugin: <LogStash::Inputs::Beats id=>"beats_plugin", port=>5044, include_codec_tag=>false, enable_metric=>true, codec=><LogStash::Codecs::Plain id=>"plain_f405f25ctric=>true, charset=>"UTF-8">, host=>"0.0.0.0", ssl=>false, ssl_verify_mode=>"none", ssl_handshake_timeout=>10000, congestion_threshold=>5, target_field_for_codec=>"rsion=>1.2, cipher_suites=>["TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256", "TLS_ECDHEE_ECDSA_WITH_AES_256_CBC_SHA384", "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384", "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256"], client_inactivity_timeout=>60>
      Error: event executor terminated

            nealch nealch
            nealch nealch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: