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

G

GiHe

@GiHe
Unfollow Follow
About
Posts
4
Topics
4
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Web Service DCI not working
    G GiHe
    Support

    This works from the NetXMS server console:

    >nxwsget 127.0.0.1 http://10.9.8.7/metrics /started
    /started = 1760481688751

    Neither /started nor $.started work (with 'metrics' as the WS Name and using the URL above):

    >nxget -D 6 127.0.0.1 'metrics:/started'
    [crypto            ] Validating ciphers
    [crypto            ]    AES-256 enabled
    [crypto            ]    Blowfish-256 disabled (validation failed)
    [crypto            ]    IDEA disabled (config)
    [crypto            ]    3DES enabled
    [crypto            ]    AES-128 enabled
    [crypto            ]    Blowfish-128 disabled (validation failed)
    [crypto            ] Crypto library initialized (OpenSSL 3.0.13 30 Jan 2024)
    [agent.conn.1      ] New connection created (address=127.0.0.1 port=4700 compression=allowed)
    [agent.conn.1      ] Using NXCP version 5
    [agent.conn.1      ] Sending message CMD_REQUEST_SESSION_KEY (1) to agent at 127.0.0.1
    [agent.conn.1      ] Received message CMD_SESSION_KEY (1) from agent at 127.0.0.1
    [agent.conn.1      ] Sending message CMD_SET_SERVER_CAPABILITIES (2) to agent at 127.0.0.1
    [agent.conn.1      ] Received message CMD_REQUEST_COMPLETED (2) from agent at 127.0.0.1
    [agent.conn.1      ] Sending message CMD_GET_PARAMETER (3) to agent at 127.0.0.1
    [agent.conn.1      ] Received message CMD_REQUEST_COMPLETED (3) from agent at 127.0.0.1
    [agent.conn.1      ] Sending message CMD_GET_TABLE (4) to agent at 127.0.0.1
    [agent.conn.1      ] Received message CMD_REQUEST_COMPLETED (4) from agent at 127.0.0.1
    [agent.conn.1      ] Sending message CMD_GET_LIST (5) to agent at 127.0.0.1
    [agent.conn.1      ] Received message CMD_REQUEST_COMPLETED (5) from agent at 127.0.0.1
    404: Unknown metric
    [agent.conn.1      ] Receiver loop terminated
    [agent.conn.1      ] Receiver cleanup completed

    What am I doing wrong?


  • [NetXMS v3.6.252] nxagentd.exe - Entry Point Not Found
    G GiHe
    Support

    Installing the new agent package on a fully-patched Windows 10 machine produced this error:

    The procedure entry point CRYPTO_clear_free could not be located in the dynamic link library
    bin\libssl.dll
    

    I have replaced the agent's installation directory with the [...] for clarity, but it is the correct path.

    Other symbols not found:

    • X509_get0_pubkey in bin\libnxagent.dll
    • OPENSSL_sk_free in bin\libnetxms.dll

  • Symbol characters (▼▲) in Alert Mail subjects
    G GiHe
    Support

    I wanted to use symbols in the subjects of Alert Mail in order to have a faster view of things like up/down status.  Using characters like these (▼▲) works well in Management Console notifications, but I have not been able to configure the server to send them so they appear in the subject line in e-mail clients.  Note that I am able to paste these symbols into e-mail subjects and send them with the characters intact.

    I have tried changing the value of the "MailEncoding" server parameter to utf-8, but I suspect (from looking at the email.cpp source code) that I need to make use of the "MailBase64Subjects" parameter.  This parameter does not appear in the Server Configuration page in the Management Console, however, and setting it in netxmsd.conf did not seem to make a difference.

    Can anyone tell me how to make this work?


  • Agent data push (firewall-friendly)
    G GiHe
    Feature Requests

    Correct me if I am wrong, but I believe that the server currently connects to the agents to pull data. 

    Has anyone implemented a push mechanism that would be more firewall-friendly, with all the agents connecting to the server ?

    If not, would the NetXMS developers like to suggest a strategy for modifying the code to achieve this topology ?

    Thanks !

  • 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