NetXMS 3.9 released

[Spheron]

Hello Victor,

thanks for the fast help. But now i had another problem at install. Please take a look here:

https://www.netxms.org/forum/general-support/install-server-3-9-156-fails-with-db-error/

Greetings
Marco

[ChrisM]

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?

[CURuser]

Hi,
updating from 3.8.366 to 3.9.156 works fine here (updated Windows package from 28-07-2021, 10:35).

Many Thanks for ongoing improvements.

But there are 2 'Problems':

1. The SMTP check via Network service is not longer working.
2. Trying to install any Agent-Version over version 3.9.156, via Package Deployment, fails with 'File transfer failed'  :-
   This might be a little desaster, when a new version has to be installed ..

[ChrisM]

@chrism said in NetXMS 3.9 released:

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.

[tanero]

After upgrade from 3.8.x to 3.9.156 web console can not login and shows an error message about incompatible protocol versions. (attachment included.)

Downloaded new version web console from https://netxms.org/download/releases/3.9/nxmc-3.9.156.war  but after installing cannot login and  version shows below right corner, still 3.8.405.

---

[ChrisM]

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.

[tanero]

@chrism said in NetXMS 3.9 released:

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.

Not exactly, server and client versions are the same on the server.

ii  netxms-agent:amd64                   3.9.156-1                     amd64        NetXMS agent
ii  netxms-base:amd64                    3.9.156-1                     amd64        NetXMS core libraries
ii  netxms-dbdrv-pgsql:amd64             3.9.156-1                     amd64        PostgreSQL driver for netxms-server
ii  netxms-server:amd64                  3.9.156-1                     amd64        meta package

The error message comes from the webconsole. I think the webconsole (war package) somehow could not be upgraded to the latest version.

[tanero]

@victor said in NetXMS 3.9 released:

Hi,

it's packaging error. I just uploaded updated installers for agent and server, please try to download again.

Best regards,
Victor

the webconsole also has a problem with protocol and older then the server.

[tanero]

Today, downloaded the webconsole from the https://netxms.org/download/releases/3.9/nxmc-3.9.156.war again.

And this time, it seems version changed to the latest one, and worked without any problem.

[lweidig]

I believe the fix NX-2073 may be overzealous or not working as expected.  Since upgrading to this release many of our Cambium ePMP devices have started reporting this on the wireless interface and there definitely is not an issue that I can determine.  If there is some information we can collect to help let us know.  Thanks as always!

[victor]

Could you please provide screenshot of "Interfaces" tab for few such devices?

Best regards,
Victor

[lweidig]

I had cleared them all, but will as new ones pop up.  Here is one and the error message is on the wireless interface MAC.

---

[victor]

Do you also have access point object under this node? It could be that there is logical flaw in duplicate MAC detection as AP object will of course have same MAC as interface object.

Best regards,
Victor

[lweidig]

Yes, the access point object exists under this node.

[victor]

Then this is the case. We will fix it in next patch release.

Best regards,
Victor