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. Upgrade 2.2.10 -->2.2.12 Segmentation Fault

Upgrade 2.2.10 -->2.2.12 Segmentation Fault

Scheduled Pinned Locked Moved Support
6 Posts 2 Posters 42.7k 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
    Meandmybrain
    wrote on last edited by
    #1

    Hi,

    I need your help :-
    Today I updated netxms (upgrading netxms-packages) and now netxmsd gets killed straight after starting.
    With "netxmsd -D 4" I get following text at the end:

    "...
    2019.02.04 15:03:42.621 *D* 0 startup scripts processed
    2019.02.04 15:03:42.621 *D* Server initialization completed in 2053 milliseconds
    2019.02.04 15:03:42.622 *I* NetXMS Server started

    NetXMS Server V2.2.12 Build 9516 (UNICODE) Ready
    Enter "help" for command list or "down" for server shutdown
    System Console

    netxmsd: 2019.02.04 15:03:43.620 *D* [action            ] Executing scheduled action [1] for event (null) on node [2453]
    2019.02.04 15:03:43.620 *D* [action            ] Executing action 1 (Send E-Mail on node down) of type SEND EMAIL
    Segmentation fault"

    It seems to me that the server crashes when it is trying to send a Email.(?)
    I checked server configs and everything is like before.
    I use Ubuntu 18.04 LTS and postgresql on x64.
    DB-upgrade was fine and without errors.

    Has anybody some helpful suggestions for me?
    THX

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

      Hi!

      Do you have a core dump? If not, could you run netxmsd under gdb and when it crashes, issue command bt and provide it's output?

      Best regards,
      Victor

      1 Reply Last reply
      0
      • M
        M
        Meandmybrain
        wrote on last edited by
        #3

        Hi,

        thanks for your answer. Unluckily I'm a noob at linux. I will figure out what "under gdb" means and try to send the dump.

        For now, the server is working after deleting the data in table "scheduled task".
        It seems that SEGV still happens when netxmsd is restarting while an alert-email is scheduled.
        Is there any known solution for this behavior?

        Best, Sebastian

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

          Hi,

          to get the dump, do the following:

          1. Stop netxmsd process
          2. Run command

          gdb netxmsd

          1. You'll get "gdb>" prompt - run command

          run -D4

          1. Wait for the crash. When process crashed, you'll get "gdb>" prompt again.

          2. Run command

          bt

          and send me it's output.

          If you have installed server from deb packages, make sure that package netxms-server-dbg is installed.

          Best regards,
          Victor

          1 Reply Last reply
          0
          • M
            M
            Meandmybrain
            wrote on last edited by
            #5

            Hi Victor,

            I answered weeks ago, now my post seems to be gone 😮

            But everything is fine now. I had to delete some entries from database table "scheduled tasks". Seemed that there was something false with them.

            Best Regards
            Sebastian

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

              Hi,

              yes, this is known issue fixed in 2.2.13 (crash because of improperly loaded scheduled task).

              Best regards,
              Victor

              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