Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - MarcusH

#1
Moved SQL queries to use ExternalMetric instead more control over connections and errors that way so in general better way so far.
#2
General Support / Re: NetXMS Grafana Plugin
March 26, 2024, 10:32:07 AM
Also looking forward to new grafana connector.
It is normal for current one to eat up sessions, every panel and query you have that has some DCI reference will create session on page load. when page has loaded the sesssions slowly die and if you leave the page with only panel refreshes it keeps sessions low but as soon as you do side refresh in browser it start all sessions again.

Been strugling for a long time with grafana eating up over 128 sessions making server unconnectable until sessions die off.
#3
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
#4
General Support / Re: Client icons
March 08, 2024, 10:41:58 AM
ah ok. I found a solution that works great, running webui version in Edge and saving it as app shortcut to taskbar.
#5
General Support / Re: Client icons
March 05, 2024, 09:37:04 AM
Quote from: Victor Kirhenshtein on February 29, 2024, 06:04:13 PMHi,

on what operating system and what client (standalone jar, from installer)? Also, Do you have dark theme in the OS?

Best regards,
Victor

Windows 11 23H2 installed with installer and i have dark theme in OS
#6
General Support / Client icons
February 28, 2024, 08:14:53 AM
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?
#7
General Support / Polling
February 15, 2024, 09:22:37 AM
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?
#8
Feature Requests / state aware maintenance scheduled tasks
September 25, 2023, 08:32:00 AM
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.
#9
General Support / Re: 4.4.2 Crash
September 20, 2023, 02:43:09 PM

Quote from: Alex Kirhenshtein on September 20, 2023, 02:29:27 PMDo you have any non-Ethernet interfaces there with MAC address longer than 6 bytes?
not that i can see
#10
General Support / Re: 4.4.2 Crash
September 20, 2023, 02:27:56 PM
Had some time today to look at this issue and it is very illusive.
My knowledge on debugging is limited and the core dump that is saved shows nothing, a few addresses that points to ??

I have tried running with debug 6 and see if i can see anything in the logs but no errors there but i see a trend.

Line before "Log file opened" is always "NetworkDeviceDriver::getInterfaces"

example:
2023.09.20 09:45:19.570 *D* [ndd.common         ] NetworkDeviceDriver::getInterfaces(0x7f0dae84c740): completed, ifList=0x7f0db5c81300

2023.09.20 09:45:21.466 *I* [logger             ] Log file opened (rotation policy 2, max size 16777216)
2023.09.20 09:45:21.466 *I* [startup            ] Starting NetXMS server version 4.4.2 build tag 4.4-568-g3a9a8aa557

if i search for  0x7f0dae84c740 in the log i found witch node it was

2023.09.20 09:45:18.722 *D* [node.iface         ] Node::getInterfaceList(node=TPFIBSW02 [10402]): calling driver (useIfXTable=true)
2023.09.20 09:45:18.722 *D* [ndd.common         ] NetworkDeviceDriver::getInterfaces(0x7f0dae84c740,true)

I started server and quickly unmanaged  TPFIBSW02 and now server has been running for a while without crashing.
Since nothing is output to the log even with level 6 i guess this needs core dump to get why it crashes on this node on poll for interfaces but there i am at a loss.
#11
General Support / Re: 4.4.2 Crash
September 20, 2023, 09:29:54 AM
Scratch that server still crashes now without any obvious error.
Might not have time to trace this error and revert again to 4.2.395
#12
General Support / Re: 4.4.2 Crash
September 20, 2023, 09:18:43 AM
Removed the node that caused the faulty query on poll and now 4.4.2 server is stable.

Noticed that there is another thread that also restarted server on "SQL query failed" is this intended behavior now or bug?
#13
General Support / Re: 4.4.2 Crash
September 15, 2023, 05:06:06 PM
Think i found it

exec sp_prepexec @p1 output,N'@P1 varchar(15),@P2 varchar(15),@P3 int,@P4 int,@P5 int,@P6 varchar(7),@P7 int,@P8 varchar(1),@P9 varchar(567)
@P9 varchar(567), P9 is snmp_oid and it is max 255

this is has been strange i removed it and will see if the issue is gone.
#14
General Support / Re: 4.4.2 Crash
September 15, 2023, 04:49:33 PM
Ah it is the "INSERT INTO event_log" for the issue i see in the trace that explains the "=?"
#15
General Support / Re: 4.4.2 Crash
September 15, 2023, 04:45:21 PM
Quote from: Alex Kirhenshtein on September 15, 2023, 10:40:07 AM
Quote from: MarcusH on September 15, 2023, 10:30:30 AMAny way to figure out what creates this query?
It's executed by object syncer thread, which saves node changes back into the database.

From the error message it's unclear which field is not accepted by the SQL server, this link might help with tracing it: https://stackoverflow.com/a/62905763
I though all the =? values was for log obfuscation but even the trace on the SQL server only shows =? i guess that would cause this issue since a lot of the columns are int and it tries to update ? into that.

Any idea on what could generate this type of node update?