NetXMS Support Forum

Added missing error massage

Hi,

in 4.4.0 I tried to update NetXMS agents on my Windows nodes.
Using the "new" web interface I get the following error:
"Cannot start package deployment: The parameter 'display' must not be null."
Using the old legacy interface, everything works correctly.
Any thougts on this?

Thanks
M.

Hi,

it works with Java 17. Thanks.
Also thanks to troffasky for his post in https://www.netxms.org/forum/announcements/netxms-4-4-released/

Thread is closed.

M.

Quote from: lhpaladin on July 16, 2023, 10:38:46 PMHello,
The latest version of the client requires Java 17, maybe it's the 404 error failure.

Hi,
I'll give it a try. Could you please tell me where you found this information? In the admin guide it says ,,Supported Java version is 11 or 15."

Edit: found it.

Thanks
M.

Hello,

today I updated NetXMS server and legacy web interface from 4.0 to 4.4.
Now I'm getting an communication protokoll missmatch error. (server=[60, 4, 1, 1, 1, 45, 1, 2] client=[60, 4, 1, 1, 1, 41, 1, 2])
Server: Ubuntu 18.04 LTS
NetXMS Server version:  NetXMS server version 4.4.0 build tag 4.4-416-ge31433b0b1
nxmc-legacy-4.4.0.war from here: https://netxms.org/download/releases/4.4/nxmc-legacy-4.4.0.war
As usual, tomcat8 service was stopped and nxmc directory + nxmc.war deleted from ./webapps before deploying the new nxmc version. (Tried this a few times.)
Has anyone some helpfull ideas to solve this problem?

(And maybe someone can give me a hint how to move to the non-legacy version? When using nxmc-4.4.0.war I'm not able to open the web interface; Error: "HTTP Status 404 not found". Staus of tomcat service is ok) )

Thanks.
M.

Hi Victor,

I was a little busy last week.

Here's what debug lvl 6 shows:

Quote2020.03.30 02:48:51.256 *D* [poll.conf          ] Primary IP address 1xx.xxx.xxx.21 of node server08.domain.de [279] found on interface Microsoft Network Adapter Multiplexor Driver of node ilo-server08.domain.de [106297]
2020.03.30 02:48:51.256 *D* [poll.conf          ] Node server08.domain.de [279] is a duplicate of node ilo-server08.domain.de [106297]
2020.03.30 02:48:51.256 *D* [poll.conf          ] Removing node ilo-server08.domain.de [106297] as duplicate
2020.03.30 02:48:51.256 *D* [                   ] Deleting object 106297 [ilo-server08.domain.de]

The problem is appearing at all of our ILOs after we decided to monitor their network.
The servers are in a different network than their ILOs. The ILOs get found and then get deleted.
e.g.: server08.domain.de has primary IP 192.111.222.21 an ILO-server08.domain.de has IP 192.111.100.8.

Best regards
Sebastian

Hi Victor,

there are no errors in the log-file, if I checked the right one. (which is set in netxmxd.conf?).
netxmsd.conf is:

"DBDriver = pgsql.ddr
DBServer = localhost
DBName = netxms
DBLogin = xxxxx
DBPassword = xxxxxx
LogFailedSQLQueries = yes
LogFile = /var/log/netxmsd"

In server configuration, "DeleteUnreachableNodesPeriod" is set to 0.

Edit: I added one oft the new nodes manually and after a while this one also disappears.

Kind regards,
Sebastian

Quote from: Victor Kirhenshtein on March 18, 2020, 10:43:09 AM
Hi,

what exact version you are using? Please show content of table "metadata".

Best regards,
Victor

Hi Victor,

now I'm on version 3.2.400.

I played along a little bit with excluding tables until the export worked.
Following tables needed to be skipped:

idata_sc_default
idata_sc_7
idata_sc_30
idata_sc_90
idata_sc_180
idata_sc_other
tdata_sc_default
tdata_sc_7
tdata_sc_30
tdata_sc_90
tdata_sc_180
tdata_sc_other
idata_83292

And here is the metadata-table:

          var_name           |                                                                                              var_value
-----------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
SchemaVersion               | 700
Syntax                      | PGSQL
IDataIndexCreationCommand_0 | CREATE INDEX idx_idata_%d_id_timestamp ON idata_%d(item_id,idata_timestamp DESC)
TDataTableCreationCommand_0 | CREATE TABLE tdata_%d (item_id integer not null,tdata_timestamp integer not null,tdata_value text null)
TDataIndexCreationCommand_0 | CREATE INDEX idx_tdata_%d ON tdata_%d(item_id,tdata_timestamp)
LocationHistory             | CREATE TABLE gps_history_%d (latitude varchar(20), longitude varchar(20), accuracy integer not null, start_timest          var_name           |                                                                                              var_value                                                                                   
-----------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
SchemaVersion               | 700
Syntax                      | PGSQL
IDataIndexCreationCommand_0 | CREATE INDEX idx_idata_%d_id_timestamp ON idata_%d(item_id,idata_timestamp DESC)
TDataTableCreationCommand_0 | CREATE TABLE tdata_%d (item_id integer not null,tdata_timestamp integer not null,tdata_value text null)
TDataIndexCreationCommand_0 | CREATE INDEX idx_tdata_%d ON tdata_%d(item_id,tdata_timestamp)
LocationHistory             | CREATE TABLE gps_history_%d (latitude varchar(20), longitude varchar(20), accuracy integer not null, start_timestamp integer not null, end_timestamp integer not null, PRIMARY KEY(start_timestamp))
ServerID                    | 2E2D7FC5BAC725ED
SingeTablePerfData          | 0
SchemaVersionLevel.30       | 102
SchemaVersionLevel.22       | 59
SchemaVersionLevel.31       | 10
SchemaVersionMajor          | 32
IDataTableCreationCommand   | CREATE TABLE idata_%d (item_id integer not null,idata_timestamp integer not null,idata_value varchar(255) null,raw_value varchar(255) null)
SchemaVersionMinor          | 12
(14 rows)

(END)   

Edit: Now there is another problem, maybe it depends on the "missing-table-problem" an would have appeared befor updating netxms:
We put 4 new devices into our network, which are found via active network discovery. After a while, they disappear in netxms and get found within the next network discovery. This kept repeading.

Kind regards
Sebastian

Quote from: Woody on March 16, 2020, 01:32:50 PM
Hello,
netxms has fixed many bugs with the latest version.
I think you can just upgrade it.
I never had problems oder data loss while upgrading.

Best regards
Woody

Upgrade works but error is still there

Hi,

Yes, I used nxdbmgr export command, giving the specified error.
I know pg_dump, used this and have a dump of my database, but the problem is still the missing table.
I'd like to work with nxdbmgr instead of using pgsql for export/dump.
Maybe it will be created after updating netxms?

Hi Folks,

in order to update netxms to the newest version, I wanted to save my database.
When I'm trying to export it to file,  I get the following error:

"Exporting table idata_sc_default
SQL query failed (42P01 ERROR:  relation "idata_sc_default" does not exist
LINE 1: SELECT * FROM idata_sc_default
                      ^):
SELECT * FROM idata_sc_default
Database export failed."

"Check-data-tables" and "check" using nxdbmgr says everything is fine. Database is PostgreSQL.
I checked the database tables manually and in deed there is no "idata_sc_default" table.
If there has to be this table, how can I get it back or create it new?
If there is no need for this table, how can I export my database before updating?
Thanks for your help!

Hi,

under var/lib/netxms/packages/ is a file called "nxagent-3.1.241-x64.exe" with 0 size.
Filename in npi is exactly the name of the agent upgrade exe.
Additional info: i'm not able to get access to /packages using "cd". Is this a normal behavior? I can only show the content of /packes using "sudo ls -la /var/lib/netxms/packages"
After I copied "nxagent-3.1.241-x64.exe" to /packages via terminal, deployment worked.
So it seems to be a problem while uploading the files using management console (i'm using web console).

Best regards
Sebastian

Hi,

for the first time I'm going to use the centralized agent upgrade, but it won't work.

The upgrade files are uploaded and shown in the packetmanager.
After choosing the node I want to upgrade immediately "Unable to start upgrade process" is shown.
In the destinationfolder at the node (win server 2016), a new file "nxagent-xxx-x64.exe" is created but with zero bytes. (win server 2016/2012R2)
Log says that "nxagent-xxx-x64.exe" could not be executed. -makes sense at this point

So option one is an error while downloading this file to node, option two maybe is an error uploading the file to netxms server.
Could you please tell me where the upgrade file is stored "usually" on netxms server (Ubuntu 18.04 LTS)?
Besides that I'm open for other thoughts.

Best regards
Sebastian

Quote from: Meandmybrain on December 04, 2019, 11:01:20 AM
Hi Victor,

that worked. Thanks a lot.
Now I´ve got the problem, that my version of netxms is 3.1.242-2 (I`m using "netxms-release-latest.deb") but the (newest?) web interface I can find in the download section is nxmc-3.1.241.war. Using this one gives me an error because of a "non-compatible communication protocol". Is the "...latest.deb" for beta-users? I it possible to downgrade netxms to 3.1.241?
Thanks ind advance.

Best regards,
Sebastian

Problem is solved. I deleted the old nxmc.war before copying the new one to /tomcat/webapps, now tomcat deployed the new one correctly.

Thanks for ur help guys.

Best regards
Sebastian

Hi Victor,

that worked. Thanks a lot.
Now I´ve got the problem, that my version of netxms is 3.1.242-2 (I`m using "netxms-release-latest.deb") but the (newest?) web interface I can find in the download section is nxmc-3.1.241.war. Using this one gives me an error because of a "non-compatible communication protocol". Is the "...latest.deb" for beta-users? I it possible to downgrade netxms to 3.1.241?
Thanks ind advance.

Best regards,
Sebastian