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. Problem after Upgrade to 3.4.232

Problem after Upgrade to 3.4.232

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 16.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.
  • G
    G
    gkaudewitz
    wrote on last edited by
    #1

    Hello together,

    I did a strange upgrade from version 2.0.5 with old mysql-database on openesuse to new mariadb 10.3 and netxms version 3.4.232 (with netxms dbupgrade and backgroundupgrade) on debian.

    Using the GUI (via Tomcat and native gui on windows) first I was shoked, because from datacollection-configuration window I cannot display the linechart from a dci. Every time I'm trying this I will get "Cannot get value for DCI[0]:"<Name der DCI>" (Invalid object ID)".
    But displaying last values from an object will work properly and within the "lastValues"-Window using linechart for a dci will display graph properly too. Same for normal DCi an table DCI. As I can see within lastvalues window datacollection is working regulary.
    Editing a DCI from "Datacollection Window" I allways wil get the follwoing advice "This DCI was added by instance discovery Alllocal changes can be overwritten at any moment" but these DCIs are not edited with instance discovery!

    Can anyone help me?

    Best regards

    Georg

    1 Reply Last reply
    0
    • G
      G
      gkaudewitz
      wrote on last edited by
      #2

      After editing the dci (without changing it) only doing "apply and Save" the problem for the edited dci has disappeared.

      1 Reply Last reply
      0
      • G
        G
        gkaudewitz
        wrote on last edited by
        #3

        Solution with editing the dci does not work for templates! After "save and apply" the dci within the template does not has the advice "This DCI was added by instance ...." but within the component the template dci is associated the advice appears. Editing this dci within the component will lead to the advice within the template once more.

        1 Reply Last reply
        0
        • F
          F
          Filipp Sudanov
          wrote on last edited by
          #4

          The issue regarding "This DCI was added by instance ...." should have been fixed in current development branch and will be included in next patch release. The message is informative only so it does not affect functionality.

          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