NetXMS Support Forum

Great advice Alex, that worked Thank you!

For others reference I ran the command:

apt-get install netxms-server netxms-dbdrv-mariadb
Then changed my /etc/netxmsd.conf to reference mariadb (replaced mysql on line DBDriver)
Restarted the netxmsd service and now all running

After updating netxms, the service would not load.
i noticed the mysql.ddr file is missing in the /usr/lib/x86_64-linux-gnu/netxms/dbdrv directory.

I tried to reinstall Netxms with the command: 

    apt-get install netxms-server netxms-dbdrv-mysql 

This resulted in an error the netxms-dbdrv-mysql had no  installation candidate.

I then tried  netxms-dbdrv-mysql-dbg, this installed but did not work.

I tried building NetXMS on a new fresh server with the same results.

Not sure if the new compiled version is missing the mysql package?

This suggests the Server is one version ahead of the client. I would suggest fully uninstalling the client, then reinstall the new version.
I have seen this myself where the original version is installed in a different file path.

Quote from: ChrisM on July 28, 2021, 03:49:39 PM
Hi Victor

I am struggling to upgrade my Ubuntu 20.04 Netxms-server (3.8 version ) to the latest version (3.9 )  it fails saying missing mysql.ddr (I have confirmed and the file is missing)

This was built previously with Mysql and worked fine (3.8 )

I have tried to upgrade via the "get-apt" process and it fails.

I think the issue may stem from upgrading the Ubuntu OS from 18 to 20 previously. Although the OS upgrade (Months ago) was successful and Netxms 3.8 continued to function, the upgrade to 3.9 ultimately failed. Having rolled back my server to a previous snapshot (OS 18.04) the upgrade to Netxms 3.9 was now successful.

Hi Victor

I am struggling to upgrade my Ubuntu 20.04 Netxms-server (3.8 version ) to the latest version (3.9 )  it fails saying missing mysql.ddr (I have confirmed and the file is missing)

This was built previously with Mysql and worked fine (3.8 )

I have tried to upgrade via the "get-apt" process and it fails.

I have removed the netxms-server via apt-get remove and tried to reinstall:

apt-get install netxms-server netxms-dbdrv-mysql

Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package netxms-dbdrv-mysql

If i try: apt-get install netxms-server

The following NEW packages will be installed:
  netxms-server
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/12.3 MB of archives.
After this operation, 127 MB of additional disk space will be used.
Selecting previously unselected package netxms-server:amd64.
(Reading database ... 193273 files and directories currently installed.)
Preparing to unpack .../netxms-server_3.9.156-1_amd64.deb ...
Unpacking netxms-server:amd64 (3.9.156-1) ...
Setting up netxms-server:amd64 (3.9.156-1) ...
NetXMS Database Manager Version 3.9.156 Build 3.9-156-g8c36cbe353 (UNICODE)

Unable to load and initialize database driver "mysql.ddr"
dpkg: error processing package netxms-server:amd64 (--configure):
installed netxms-server:amd64 package post-installation script subprocess returned error exit status 3
Processing triggers for systemd (245.4-4ubuntu3.11) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
Errors were encountered while processing:
netxms-server:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have also tried to build via binaries using the --with-mysql command, but locks up during the Make process.

Any suggestions? Is anybody else experiencing an issue with upgrading?

Thank you Victor.

I completely missed the Zoning concept. Setup with Zoning and proxy as you suggested and working well.

I am looking to utilise a remote Agent which connects back to the NetXMS server via an agent tunnel, to discover active network devices/Map used IP addresses etc at the remote site.

After some investigating and research, I believe I have found previous requests for this feature a number of years ago, but no confirmation it has been released.

From my testing, I can see the Network discovery on the server looking for devices and although they see the MAC details via ARP (From the remote agent?), no ICMP or SNMP response is received. I assume this is because the ICMP/SNMP requests are not utilising the tunnel agent:

2021.01.08 12:32:51.285 *D* [                   ] GetOldNodeWithNewIP: ip=192.168.0.63 mac=70:18:8B:51:86:3A
2021.01.08 12:33:03.220 *D* [agent.conn.620     ] Cannot establish connection with agent at 192.168.0.63:4700
2021.01.08 12:33:03.220 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.0.63): starting check (proxy=0, originalPort=0)
2021.01.08 12:33:03.220 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.0.63): checking port 161
2021.01.08 12:33:03.221 *D* [snmp.discovery     ] SnmpCheckV3CommSettings(192.168.0.63): failed
2021.01.08 12:33:03.221 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.0.63): trying version 1 community 'public'
2021.01.08 12:33:07.726 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.0.63): trying version 1 community '*******'
2021.01.08 12:33:12.228 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.0.63): trying version 0 community 'public'
2021.01.08 12:33:16.730 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.0.63): trying version 0 community '*******'
2021.01.08 12:33:21.231 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.0.63): failed
2021.01.08 12:33:21.231 *D* [obj.poll.node      ] AcceptNewNode(192.168.0.63): host is not reachable

I have set the network discovery to utilise the remote agent but this fails.

If I manually add the node and address the proxy via this agent, the device communicates successfully and functions as expected.

Which leads me to believe currently it is not possible to utilise Network Discovery via a tunnelled agent, Is this correct?

If so, i see a great use case for this scenario, would it be possible to add to the development roadmap?

Alternatively, please can you point me in the correct direction.

Thank you!