NetXMS Support Forum

How the IP of DB server is configured in netxmsd.conf? Is it like this:
DBServer=127.0.0.1

If so, try
mysql -u root -p -h 127.0.0.1

Try connecting from the machine where your netxms server is running by giving the IP address of your database server:

mysql -u root -p -h 1.2.3.4

1.2.3.4 should be replaced by IP address of your database server.

Well, this line gives the answer:
2022.06.07 13:06:12.175 *E* [db                 ] Unable to establish connection with database (Access denied for user 'netxms'@'localhost' (using password: NO))
NetXMS was not able to connect to the database. Check your login and password and that the database accepts connection from that IP address.

Descovery debugging was a bit improved. Fix will be included in next patch release. Please try the new version when it will be available and share the log.

Can you check in Audit Log in netxms if there are any unsuccessful logins happening?

Ok, so looks that the event about the SQL error is generated showing the server as source.

This error happens due to old version netxms agent - it cropped name of software package and it could happen that remaining part of name for two packages was the same. So the solution is to upgrade agents on all nodes.
You can try to find the node

select from software_inventory where name like '6733-Cisco AnyConnect Secure Mobility Client%' and version = '4.7.04056';

Are there also lines like this in the log:

2022.06.06 11:41:35.641 *I* [comm.listener      ] SocketListener/Clients: listening on 0.0.0.0:4701
2022.06.06 11:41:35.641 *I* [comm.listener      ] SocketListener/Clients: listening on [0.0.0.0]:4701

It is planned to rework file upload mechanism in the near future - when this will be done, we will double-check that all issues like this one are fixed.

Authentication was recently added to nxadm and is turned on by default. It can be turned off by server configuration variable Server.Security.RestrictLocalConsoleAccess.

Or
nxadm -u username -P password -i

We will try to make the error message more human-friendly.

try
sudo systemctl start netxmsd
instead of
systemctl start netxms-server

range 192.168.139.1 - 192.168.135.254  - this was incorrect debug message, was just fixed will be in next patch release.

What exactly version you currently use?

But how it goes currently, it gets detected with CISCO-GENERIC driver?

You can actually force CISCO-SB by setting custom attribute snmp.driver to CISCO-SB. If so, would all information get collected correctly or would there be any issues?

It uses 16 out of max 16 threads which means that at some point they were needed and were populated. And avg wait time of about 0.5 second tells that there are moments when it's doing something.
Graph of current load for 24 hours could tell more, but looks like it's not too busy. It definitely had been busy when discovering this network for the first time, but now addresses for which nodes are already created are not polled in this thread pool any more.

You can add another active discovery range that would include just on of these switches that are not getting added, turn on 6 debug level for poll.discovery and do a scan manually only for this specific range. This way log would have just the information we need.

Actually this is a bug - in last values it should be displayed the same way as in history. This will be fixed.

In the future custom formatting will be implemented - you can follow this issue: https://track.radensolutions.com/issue/NX-2265

Is there any chance that you could provide remote access to such a device to our developers? That would be the easiest way to develop the driver.