NetXMS Support Forum

Trying to create an action that runs a script but as soon as i have char åäö in parameter it seems like it fails to run the process, have agent in debuglevel 6 and no error shows up it runs process and it shows PID for it.

I have verified that everything i can think of is utf8

made debug script that logs to file if run Action=debug:/agent/script/ping.sh --message "$1"

$node.executeAgentCommand("debug","test") runs fine and log files are created
$node.executeAgentCommand("debug","testå") is executed according to agent log and gets PID but no logs are created and i can't figure any more deeper way to debug

Running agent 5.2.6 on Debian 12 in docker

if i run script in docker cli it works with åäö only fails when agent runs the script.

Any tips or known issues?

Hi,

Started migrating our Grafana to Infinity and new server api.
Saw the techtalk video on youtube and the blog post nice work.

One thing i noticed was that you use $__from/1000 and $__to/1000 for seconds and was having issue it not working, found that Grafana has these variables i guess they are cleaner to use ${__from:date:seconds} and ${__to:date:seconds}

Also trying to get relative time to work, i have dashboard on last 30min beacuse they are used on TV screens but some DCI just collects once a day and i have 12h relative on them, tried ${__from:date:seconds}-43200 but does not seem to work i get all 3 days that are in history.

is it supposed to calc before query or send it to api? URL is ?timeFrom=1760509472-43200&timeTo=1760511272

Running 5.2.6 and latest Inifinity

Hi,

Any news on new NetXMS connector for Grafana?

Hi,

Time to renew this?

Hi,

Any known issues with connecting to snmp v3 agents?
Have odd issue where some nodes work and some don't with the exact same auth configuration.

The node that netxms can't connect to agent with v3 is verified that the agent is running and v3 auth information works in other snmp explorer software.

The node can connect with v2c if enabled, just v3 having issues.

Tried debug logs but since it is the server very hard with spammed debug log, set snmp.discovery to level 6 and it shows SnmpCheckV3CommSettings trying then fail.

When i do full config poll on a node that V3 works on there is no SnmpCheckV3CommSettings in logs it just connects and polls.

The nodes that V3 work on and the nodes that does not have exact same config no question since the snmp is set with nxshell script on all nodes in the container.

Hi,

Are there any known issues with mssql driver in agent for windows server 2022?

I am migrating servers and exact same config and agent version fail on new server with error [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

logs from old server with windows server 2016
2024.03.18 10:34:20.066 *I* [db.drv             ] Database driver "mssql.ddr" loaded and initialized successfully
2024.03.18 10:34:20.098 *D* [db.conn            ] New DB connection opened: handle=000002538F7AD490
2024.03.18 10:34:20.098 *I* [dbquery            ] Connected to database "db1"
2024.03.18 10:34:20.113 *I* [subagents          ] Subagent "DBQUERY" (dbquery.nsm) loaded successfully (version 4.4.2)
logs from new server with windows server 2022
2024.03.18 10:40:18.546 *I* [db.drv             ] Database driver "mssql.ddr" loaded and initialized successfully
2024.03.18 10:40:18.546 *W* [dbquery            ] Cannot connect to database "db1" ([Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified)
2024.03.18 10:40:18.546 *I* [subagents          ] Subagent "DBQUERY" (dbquery.nsm) loaded successfully (version 4.4.2)
agent config:
DebugLevel = 6
LogFile = C:\NetXMS\log\log.txt
MasterServers = *.*.*.*
ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
FileStore = C:\NetXMS\var
SubAgent = winperf.nsm

SubAgent = dbquery.nsm
*DBQUERY
Database = id=db1;driver=mssql.ddr;server=server;dbname=db;login=user;password=pwd
I tried latest agent version and same issue.

I have tried adding ODBC DSN same issue

Hi,

After i installed new 4.5.3 client the icons are a strange shade of yellow, tried uninstalling and installing again same issue.
Any tips on how to fix this?

Hi,

I am cleaning up all my nodes and turning off unused polls to remove unused connections.
My idea was to make script for nxshell for this for ease of use since i have trusted nodes active.

When i started gathering data for this i found a discrepancy with modbus, i understand support for this is relatively new.
The issue i found was only option to disable modbus that i can only find is enableModbusTcp in nxsl but there are no GUI option for this or any constant or am i missing something?

Hi,

If you have a scheduled task that runs maintenance.enter and maintenance.leave on a container have an option to make it current status aware, meaning if a node already is in maintenance in the container when maintenance.enter is run do not remove maintenance on that node when task maintenance.leave runs.

Hi,

Upgraded from 4.2.395 to 4.4.2 and now server crashes on some strange sqlquery, we had this query on 4.2.395 also but never caused crash.

Any idea on what this query is?

2023.09.14 16:04:19.220 *E* [db.drv             ] SQL query failed (Query = "UPDATE nodes SET primary_ip=?,primary_name=?,snmp_port=?,capabilities=?,snmp_version=?,community=?,agent_port=?,secret=?,snmp_oid=?,uname=?,agent_version=?,platform_name=?,poller_node_id=?,zone_guid=?,proxy_node=?,snmp_proxy=?,icmp_proxy=?,required_polls=?,use_ifxtable=?,usm_auth_password=?,usm_priv_password=?,usm_methods=?,snmp_sys_name=?,bridge_base_addr=?,down_since=?,driver_name=?,rack_image_front=?,rack_position=?,rack_height=?,physical_container_id=?,boot_time=?,agent_cache_mode=?,snmp_sys_contact=?,snmp_sys_location=?,last_agent_comm_time=?,syslog_msg_count=?,snmp_trap_count=?,node_type=?,node_subtype=?,ssh_login=?,ssh_password=?,ssh_key_id=?,ssh_port=?,ssh_proxy=?,port_rows=?,port_numbering_scheme=?,agent_comp_mode=?,tunnel_id=?,lldp_id=?,fail_time_snmp=?,fail_time_agent=?,fail_time_ssh=?,rack_orientation=?,rack_image_rear=?,agent_id=?,agent_cert_subject=?,hypervisor_type=?,hypervisor_info=?,icmp_poll_mode=?,chassis_placement_config=?,vendor=?,product_code=?,product_name=?,product_version=?,serial_number=?,cip_device_type=?,cip_status=?,cip_state=?,eip_proxy=?,eip_port=?,hardware_id=?,cip_vendor_code=?,agent_cert_mapping_method=?,agent_cert_mapping_data=?,snmp_engine_id=?,snmp_context_engine_id=?,syslog_codepage=?,snmp_codepage=?,ospf_router_id=?,mqtt_proxy=?,modbus_proxy=?,modbus_tcp_port=?,modbus_unit_id=? WHERE id=?"): [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]String or binary data would be truncated.
2023.09.14 16:04:19.220 *D* [event.proc         ] EVENT SYS_DB_QUERY_FAILED [52] at {0} (ID:57617035 F:0x0001 S:4 TAGS:"") FROM netxmsd: Database query failed (Query: UPDATE nodes SET primary_ip=?,primary_name=?,snmp_port=?,capabilities=?,snmp_version=?,community=?,agent_port=?,secret=?,snmp_oid=?,uname=?,agent_version=?,platform_name=?,poller_node_id=?,zone_guid=?,proxy_node=?,snmp_proxy=?,icmp_proxy=?,required_polls=?,use_ifxtable=?,usm_auth_password=?,usm_priv_password=?,usm_methods=?,snmp_sys_name=?,bridge_base_addr=?,down_since=?,driver_name=?,rack_image_front=?,rack_position=?,rack_height=?,physical_container_id=?,boot_time=?,agent_cache_mode=?,snmp_sys_contact=?,snmp_sys_location=?,last_agent_comm_time=?,syslog_msg_count=?,snmp_trap_count=?,node_type=?,node_subtype=?,ssh_login=?,ssh_password=?,ssh_key_id=?,ssh_port=?,ssh_proxy=?,port_rows=?,port_numbering_scheme=?,agent_comp_mode=?,tunnel_id=?,lldp_id=?,fail_time_snmp=?,fail_time_agent=?,fail_time_ssh=?,rack_orientation=?,rack_image_rear=?,agent_id=?,agent_cert_subject=?,hypervisor_type=?,hypervisor_info=?,icmp_poll_mode=?,chassis_placement_config=?,vendor=?,product_code=?,product_name=?,product_version=?,serial_number=?,cip_device_type=?,cip_status=?,cip_state=?,eip_proxy=?,eip_port=?,hardware_id=?,cip_vendor_code=?,agent_cert_mapping_method=?,agent_cert_mapping_data=?,snmp_engine_id=?,snmp_context_engine_id=?,syslog_codepage=?,snmp_codepage=?,ospf_router_id=?,mqtt_proxy=?,modbus_proxy=?,modbus_tcp_port=?,modbus_unit_id=? WHERE id=?; Error: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]String or binary data would be truncated.)

Hi,

Is functionality to push values to push DCI implemented in current API 4.2.395?

Hi,

When AgentExecuteAction changed name to AgentExecuteCommand in 4.2.395 i was challenged with a problem in that i use AgentExecuteAction alot so is there any way to search script library for content?

If not maybe a good feature to have if there are more script breaking function name changes in the future to make it easier to fix the entire library.

Hi,

Updated to 4.2.395 and now when script runs AgentExecuteAction i get Function not found?

Is this a bug can't see any notes in scripting docs that this is deprecated

Hi,

Working on integration NetXMS with GLPI using RestAPI and web service definitions. Everything is working except i can not get a handle arround the JSON response.

Is there no support for JSON arrays in NXSL functions?

For example i have this response and i want to loop these values and count total


[
   {
      "id": 178
   },
   {
      "id": 179
   },
   {
      "id": 181
   }
]


Hi,

Is there any way to in a script that runs as DCI identify which DCI that started the script?
I am trying to make one script for multiple DCI

Hi,

Are there any ways to manage trusted nodes in bulk or do you need to righ click every single node and add trusted node?

Hi,

I am moving server from windows to linux since i want to run it in docker.
I managed to create a docker image with ODBC driver and and Linux ODBC Driver 17 for SQL Server from Microsoft and i am having problems connecting to database.
I have deduced that my problem is that you cannot have user/password in the DSN setting you can only send password in connection string, the only solution other then this is setting up Kerberos which i have no experience of.

So my question is it in any way possible to set username/password in netxms that is sent to ODBC or is it 100% relying on ODBC internal mechanics?

I would really like to use MS SQL since that is what i have most experience with and already have good backup and maintenance on it.

Hi,

running 3.5.90 and the connection with management is unstable, if i run 'show sessions' in server console the output can stop halfway and then after a while the entire client gets Cannot open server console: Request timed out.
If all the output from sessions is recieved it never returns to prompt need to close the server console tab and open it again to type new command

Hi,

I have a problem that i am trying to understand and see if it is something that can be fixed with config.

When i refresh a dashboard in grafana that has alot of unique DCI values, every tile creates its own session to the server via the webapi meaning you max out available connections to the server and then everything hangs until sessions starts to close.
What i trying to understand if this is how grafana works or is it the netxms datasource plugin or webapi that causes this problem.

If anyone has any knowledge of this i'd be happy to hear it.

Hi,

Upgraded from 3.0 to 3.1 and now grafana can not connect, i have updated both webui and webapi.
The webapi is active but when you save and test in the grafana connector you get "HTTP Error Internal Server Error"

Can not find any logs that shows a description of the error found it

in the webui logs:

INFO: 2019-12-05 09:21:29 192.168.*.* admin 192.168.*.* 8083 GET /webapi/grafana/datacollection
dec 05, 2019 9:21:34 FM org.restlet.resource.ServerResource doCatch
SEVERE: Exception or error caught in server resource
org.restlet.resource.ResourceException: Internal Server Error (500) - The server encountered an unexpected condition which prevented it from fulfilling the request
at org.restlet.resource.ServerResource.doHandle(ServerResource.java:527)
at org.restlet.resource.ServerResource.get(ServerResource.java:723)
at org.restlet.resource.ServerResource.doHandle(ServerResource.java:603)
at org.restlet.resource.ServerResource.doNegotiatedHandle(ServerResource.java:662)
at org.restlet.resource.ServerResource.doConditionalHandle(ServerResource.java:348)
at org.restlet.resource.ServerResource.handle(ServerResource.java:1020)
at org.restlet.resource.Finder.handle(Finder.java:236)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.routing.Router.doHandle(Router.java:422)
at org.restlet.routing.Router.handle(Router.java:641)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.engine.application.StatusFilter.doHandle(StatusFilter.java:140)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.engine.CompositeHelper.handle(CompositeHelper.java:202)
at org.restlet.engine.application.ApplicationHelper.handle(ApplicationHelper.java:77)
at org.restlet.Application.handle(Application.java:385)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.routing.Router.doHandle(Router.java:422)
at org.restlet.routing.Router.handle(Router.java:641)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.routing.Router.doHandle(Router.java:422)
at org.restlet.routing.Router.handle(Router.java:641)
at org.restlet.routing.Filter.doHandle(Filter.java:150)
at org.restlet.routing.Filter.handle(Filter.java:197)
at org.restlet.engine.CompositeHelper.handle(CompositeHelper.java:202)
at org.restlet.Component.handle(Component.java:408)
at org.restlet.Server.handle(Server.java:507)
at org.restlet.engine.connector.ServerHelper.handle(ServerHelper.java:63)
at org.restlet.engine.adapter.HttpServerHelper.handle(HttpServerHelper.java:143)
at org.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:1117)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:499)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.netxms.client.NXCSession.connect(NXCSession.java:1934)
at org.netxms.client.NXCSession.connect(NXCSession.java:1907)
at org.netxms.websvc.handlers.AbstractHandler.login(AbstractHandler.java:402)
at org.netxms.websvc.handlers.AbstractHandler.attachToSession(AbstractHandler.java:218)
at org.netxms.websvc.handlers.AbstractHandler.onGet(AbstractHandler.java:77)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.restlet.resource.ServerResource.doHandle(ServerResource.java:511)
... 61 more

Everything runs on the same server, netxmsd, webui and grafana

Edit:

Downgraded the webapi to "NetXMS web service API version 3.0.2296" then it worked again