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. Centralized Agent Upgrade Fails

Centralized Agent Upgrade Fails

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 23.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.
  • C
    C
    ChrisC
    wrote on last edited by
    #1

    I have followed the instructions here:
    https://www.netxms.org/documentation/adminguide/upgrade.html?highlight=upgrade agent#centralized-agent-upgrade, but when I try and deploy the agent, none of them work, and I get the message "Agent's version doesn't match package version after upgrade"
    I am running NetXMS Server 3.9.298, and am trying to install the agent 3.9.334 and will upgrade the server soon afterwards.
    I have never tried this before.

    Looking at the agent logs, it seems to be receiving the file in chunks, which are then merged back into the original .exe.
    I see this in the log also:

    2021.10.29 11:33:38.769 *D* [procexec           ] ProcessExecutor::execute(): process "CMD.EXE /C "C:\NetXMS\var\nxagent-3.9.334-x64.exe" /VERYSILENT /SUPPRESSMSGBOXES /LOG /FORCECLOSEAPPLICATIONS /NORESTART" started
    

    which I guess is good news, but I can't see anything obvious after this.

    All agents I am trying to upgrade are on the same LAN, so I doubt it's a network problem.
    I ran the above command manually on one of the failing servers, and it worked.

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

      There was a bug recently that upgrade command was actually not executed.
      The upgrade however is uploaded.
      You can create agent action that executes CMD.EXE /C "C:\NetXMS\var\nxagent-3.9.334-x64.exe" /VERYSILENT /SUPPRESSMSGBOXES /LOG /FORCECLOSEAPPLICATIONS /NORESTART
      and it should do the job.
      You can create agent configuration policy in a template and apply this template to your nodes - this way you can distribute this action to your agents.

      1 Reply Last reply
      0
      • C
        C
        ChrisC
        wrote on last edited by
        #3

        Thanks Filipp!
        I'll try it out.

        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