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 to 1.2.8 Version

Upgrade to 1.2.8 Version

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 19.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.
  • A
    A
    ademirel
    wrote on last edited by
    #1

    Hi,

    I try to upgrade from 1.2.7 to 1.2.8 version. It is giving an error when I install the new packages: undefined symbol: wgetenv

    What can be the problem? is it a bug?

    Regards

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

      Hi!

      On what platform you are installing? How do you install server - from sources, from binary package?

      Best regards,
      Victor

      1 Reply Last reply
      0
      • A
        A
        ademirel
        wrote on last edited by
        #3

        My platform is debian. Firstly, I compiled from source code netxms-1.2.8. And then, I installed debian packages such as agent,base,server.

        I did it according to this document.

        http://wiki.netxms.org/wiki/Server_Installation_Guide#Upgrading_NetXMS_Server_on_UNIX

        Regards

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

          You shouldn't use both methods ion same machine. Most likely you now have two incompatible set of binaries - one under /user and seconds under /usr/local (or other place if you specify --prefix at configure stage). Try to identify wrong binaries and delete them.

          Best regards,
          Victor

          1 Reply Last reply
          0
          • A
            A
            ademirel
            wrote on last edited by
            #5

            oops, I re-configured it using different prefix and it solved.

            Thanks Victor.

            Best Regards

            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