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. Triggering configuration poll/template deployment by NXSL

Triggering configuration poll/template deployment by NXSL

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 17.6k 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.
  • F
    F
    Benjamin Dill
    wrote on last edited by
    #1

    Following situation: We have nodes which are only a few minutes online every day, used for running a few scripts. These scripts are deployed by templates in NetXMS and are updated from time to time, but as these nodes are virtually never online for a configuration poll and updated files from the templates get never deployed.

    Is there a way to trigger a configuration poll of these nodes by script, using one of the hooks? I studied the NXSL reference but I found nothing helpful.

    Thank you!

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

      Configuration polls are executed periodically on their own schedule (previously it was so that configuration poll was executed only if status poll detected node up situation, but that had issued - e.g. SNMP community string changed and that required conf poll to find the correct one).

      For tunnel nodes, however, conf poll should be scheduled right after tunnel is established, so you can try that.

      There is no way to force a poll from NXSL, I've created an issue so at some moment of time this could be added: https://track.radensolutions.com/issue/NX-2480

      A bit crazy approach which might currently work - we have an option to redefine poll intervals using custom attributes, e.g:

      SysConfig:Objects.ConfigurationPollingInterval
      

      so status poll hook can detect that node comes up and set such custom interval (with value say 60) and conf poll hook would delete this custom attribute.

      1 Reply Last reply
      0
      • F
        F
        Benjamin Dill
        wrote on last edited by
        #3

        Wow, thanks, that will work: These nodes are up for about 15 minutes. If I set the custom attribute to 10 minutes every node should get one poll per uptime  🙂

        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