ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    ELK stops accepting logs

    IT Discussion
    elk filebeat
    3
    26
    7.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403 @Danp
      last edited by

      @Danp Just as a similar item MineCraft FTB has a similar memory leak issue. I have yet to find a solution for it (among the the million of people talking about it around Google)

      1 Reply Last reply Reply Quote 0
      • DanpD
        Danp
        last edited by

        Ran a plugin update. Will see if that has any effect.

        Updated logstash-codec-json 2.1.0 to 2.1.1
        Updated logstash-filter-dns 2.0.2 to 2.1.0
        Updated logstash-filter-json 2.0.3 to 2.0.4
        Updated logstash-input-beats 2.1.3 to 2.2.0
        Updated logstash-input-rabbitmq 3.1.4 to 3.3.0
        Updated logstash-input-redis 2.0.2 to 2.0.3
        Updated logstash-output-elasticsearch 2.5.1 to 2.5.3
        
        DanpD 1 Reply Last reply Reply Quote 0
        • DanpD
          Danp @Danp
          last edited by

          During the command bin/plugin update, received the error

          Error Bundler::InstallError, retrying 1/10
          An error occurred while installing manticore (0.5.5), and Bundler cannot continue.
          Make sure that `gem install manticore -v '0.5.5'` succeeds before bundling.
          

          Discussions on similar issues can be found here and here.

          1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller
            last edited by

            Lots of reports on this, although I have a feeling that it might not be a leak but might be just "how much memory Logstash needs."

            Try setting it to something high and see if it stops expanding.

            DanpD 1 Reply Last reply Reply Quote 0
            • DanpD
              Danp @scottalanmiller
              last edited by

              @scottalanmiller said:

              Lots of reports on this, although I have a feeling that it might not be a leak but might be just "how much memory Logstash needs."

              Try setting it to something high and see if it stops expanding.

              I already went from 1g to 2g. I could be off base, but I suspect a memory leak b/c it runs for days before the OOM condition occurs. The only active feed is from my XO server, and that activity should be light.

              scottalanmillerS 1 Reply Last reply Reply Quote 0
              • DanpD
                Danp
                last edited by

                Found this current Github discussion that describes the plugin update issue I ran into.

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller @Danp
                  last edited by

                  @Danp said:

                  @scottalanmiller said:

                  Lots of reports on this, although I have a feeling that it might not be a leak but might be just "how much memory Logstash needs."

                  Try setting it to something high and see if it stops expanding.

                  I already went from 1g to 2g. I could be off base, but I suspect a memory leak b/c it runs for days before the OOM condition occurs. The only active feed is from my XO server, and that activity should be light.

                  That would be the expected behaviour whether a leak or just hasn't fully grown yet.

                  1 Reply Last reply Reply Quote 0
                  • DanpD
                    Danp
                    last edited by

                    Finally back up and running...

                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller @Danp
                      last edited by

                      @Danp said:

                      Finally back up and running...

                      What did you do?

                      DanpD 1 Reply Last reply Reply Quote 0
                      • DanpD
                        Danp @scottalanmiller
                        last edited by

                        @scottalanmiller Reinstalled ruby-maven and manticore.

                        1 Reply Last reply Reply Quote 1
                        • DanpD
                          Danp
                          last edited by

                          No issues in almost a week. I will probably drop the heap size back to 1g and see if it remains stable.

                          1 Reply Last reply Reply Quote 1
                          • 1
                          • 2
                          • 2 / 2
                          • First post
                            Last post