NetXMS Support Forum

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

ah ok. I found a solution that works great, running webui version in Edge and saving it as app shortcut to taskbar.

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

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.

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

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.

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

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?

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.

Ah it is the "INSERT INTO event_log" for the issue i see in the trace that explains the "=?"

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?

Quote from: Alex Kirhenshtein on September 15, 2023, 10:38:19 AM

Quote from: MarcusH on September 15, 2023, 10:36:51 AMI have a core dump but it gives a lot of reference error and shows no stack trace.

Have you installed netxms-dbg package? It contains all debug symbols for the product.

I have not i will have look at this on the test VM

Quote from: Alex Kirhenshtein on September 15, 2023, 10:31:49 AM

Quote from: MarcusH on September 15, 2023, 10:03:20 AMRunning server on docker making core dump a challange.

it's rather straighforward if you can control host's core pattern

Code Select Expand

sysctl -w kernel.core_pattern='/core/core.%e.%p.%t'
docker volume create core_vol
docker run --ulimit core=-1 --mount source=core_vol,target=/core container
sysctl -w kernel.core_pattern=core # reset it back to the default

I have a core dump but it gives a lot of reference error and shows no stack trace.