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. NetworkService.Status brings false Values

NetworkService.Status brings false Values

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 27.2k 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.
  • S
    S
    Spheron
    wrote on last edited by
    #1

    Hello @all,

    since Update NetXMS to V4.4.3 all Checks with the Function NetworkService.Status (with verify-peer=false)Ā failed with error 5

    Example:
    NetworkService.Status(https://10.99.45.44,verify-peer=false)

    Up to V4.4.2 this one works without problems. If URL is reached it throws a Result "0". Since V4.4.3 it always throws Code "5".

    NetworkService.Status checks without the "verify-peer=false" option works without any problems.

    Has anyone else seen this behavior?

    Greetings
    Marco

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

      I don't remember exactly, but there probably was a bug with default values of these named parameter of NetworkService.Status. Your URL contains IP address, but certificate was probably issued for a domain name, so host verification fails. To skip host verification, add the following:

      NetworkService.Status(https://212.70.163.157,verify-peer=false,verify-host=false)

      Documentation on all available parameters should be up to date:
      https://www.netxms.org/documentation/adminguide/service-monitoring.html#network-service-monitoring-using-dci

      1 Reply Last reply
      0
      • S
        S
        Spheron
        wrote on last edited by
        #3

        Hi Filipp,

        thanks for your answer. I added the verify-host=false to my configs and voila: it worked again... šŸ™‚

        Many thanks for that hint...Ā 

        GreetingsĀ 
        Marco

        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