Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Out of memory NetXMS v1.2.5

Out of memory NetXMS v1.2.5

Scheduled Pinned Locked Moved Support
32 Posts 4 Posters 180.9k Views
  • 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.
  • M
    M
    millerpaint
    wrote on last edited by
    #20

    Hi,

    One thing seems strange, it crashes with out of memory right away running under valgrind.  If I run netxmsd normally, it can run for hours before crashing.

    -Kevin C.

    1 Reply Last reply
    0
    • M
      M
      millerpaint
      wrote on last edited by
      #21

      OK, good news Alex.  The script you provided shut down NetXMS gracefully after it reached the 1GB of RAM threshold.  It took 12-15 minutes running under valgrind before it crashed.  I have attached the valgrind log.

      Thanks,

      -Kevin C.


      netxmsd-valgrind.log

      1 Reply Last reply
      0
      • V
        V
        Victor Kirhenshtein
        wrote on last edited by
        #22

        Hi!

        @millerpaint said in Out of memory NetXMS v1.2.5:

        One thing seems strange, it crashes with out of memory right away running under valgrind.  If I run netxmsd normally, it can run for hours before crashing.

        This is normal, when running under valgrind program takes tens times more memory then when it run normally. Valgrind allocates extra memory around each dynamically allocated block to detect boundary violations, etc.

        Best regards,
        Victor

        1 Reply Last reply
        0
        • M
          M
          millerpaint
          wrote on last edited by
          #23

          This is normal, when running under valgrind program takes tens times more memory then when it run normally. Valgrind allocates extra memory around each dynamically allocated block to detect boundary violations, etc.

          OK, that makes sense Victor.

          I have attached a screenshot of my Network Discovery panel, so you can see more about the details of my configuration.  I also have (2) SNMP community strings listed, but they are not visible in the screenshot image.

          I am using top to monitor the memory consumption of netxmsd - it seems to be consuming 1/10th of 1% of available RAM every few seconds, running in normal mode.

          -Kevin C.


          netdiscovery.pdf

          1 Reply Last reply
          0
          • A
            A
            Alex Kirhenshtein
            wrote on last edited by
            #24

            Unfortunately, there nothing related to your issue in this log.
            Could you please change 1Gb limit to 2Gb in the script and rerun it?

            @millerpaint said in Out of memory NetXMS v1.2.5:

            OK, good news Alex.  The script you provided shut down NetXMS gracefully after it reached the 1GB of RAM threshold.  It took 12-15 minutes running under valgrind before it crashed.  I have attached the valgrind log.

            1 Reply Last reply
            0
            • M
              M
              millerpaint
              wrote on last edited by
              #25

              Hi Alex,

              I modified the script for a 2GB threshold and re-ran it, the new log file is attached.  Hopefully this will provide some clues as to what is going on.

              When monitoring with top, it seems to start consuming RAM when the timer reaches 14:41:

              netxmsd starts out using .5% available RAM of server.  Then:
              14:41 - .6%
              15:50 - .7%
              16:53 - .8%
              17:69 - .9%
              18:60 - 1%
              19:20 - 1.1%
              20:05 - 1.2%
              etc.

              Thanks for your help!

              -Kevin C.


              netxmsd-valgrind.log

              1 Reply Last reply
              0
              • M
                M
                millerpaint
                wrote on last edited by
                #26

                FYI, I have completely disabled auto-discovery, and it is still running out of memory.

                -Kevin C.

                1 Reply Last reply
                0
                • V
                  V
                  Victor Kirhenshtein
                  wrote on last edited by
                  #27

                  Hi!

                  We are still trying to figure out what could cause such a high memory consumption. Can you please do the following:

                  1. Run netxmsd under valgrind with additional options:
                  valgrind --leak-check=full --undef-value-errors=no --show-reachable=yes --log-file=netxmsd-valgrind.log netxmsd -D3
                  

                  (or modify script sent by Alex by adding --show-reachable=yes to valgrind's command line).

                  1. Run valgrind's heap profiller:
                  valgrind --tool=massif --time-unit=ms --stacks=yes --threshold=0.5 --max-snapshots=1000 --log-file=netxmsd-massif.log netxmsd -D3
                  

                  and send me profiler's result (it will be named massif.out.<pid>).

                  Also, can you please show me you configuration hook script and transformation scripts?

                  Best regards,
                  Victor

                  1 Reply Last reply
                  0
                  • M
                    M
                    millerpaint
                    wrote on last edited by
                    #28

                    Hi Victor,

                    OK, I can do step 1 additional options with no problem.

                    With Step 2, you are asking me to run valgrind's heap profiler.  I have questions on that:

                    1. Is step 2 option run after I have completed running the step 1 test, and it runs out of memory?
                    2. Do I need to start Alex's script before running step 2?

                    -Kevin C.

                    1 Reply Last reply
                    0
                    • V
                      V
                      Victor Kirhenshtein
                      wrote on last edited by
                      #29

                      Hi!

                      Yes, you should run step 2 after step 1 is completed. You can use Alex's script for step 2 too.

                      Best regards,
                      Victor

                      1 Reply Last reply
                      0
                      • M
                        M
                        millerpaint
                        wrote on last edited by
                        #30

                        Hi Victor,

                        I am unable to attach the valgrind log from Step 1, it is about 600k in size, and your forum will not allow me to post it.

                        Can you please raise the limit of your attachment size on this forum, or else let me know your email address?

                        Thanks,

                        -Kevin C.

                        1 Reply Last reply
                        0
                        • V
                          V
                          Victor Kirhenshtein
                          wrote on last edited by
                          #31

                          You can send it to [email protected].

                          Best regards,
                          Victor

                          1 Reply Last reply
                          0
                          • M
                            M
                            millerpaint
                            wrote on last edited by
                            #32

                            OK thanks - all log files you have requested from valgrind have been sent to that email address.

                            -Kevin C.

                            1 Reply Last reply
                            0

                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                            With your input, this post could be even better 💗

                            Register Login
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            • Login

                            • Don't have an account? Register

                            • Login or register to search.
                            Powered by NodeBB Contributors
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Tags
                            • Popular
                            • Users
                            • Groups