Added missing error massage ::)
Meandmybrain
Posts
-
Error using package manager for agent update -
Error using package manager for agent updateHi,
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. -
WebUI V4.4.0 mismatch communication protocoll /Ubuntu/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.
-
WebUI V4.4.0 mismatch communication protocoll /Ubuntu/@lhpaladin said in WebUI V4.4.0 mismatch communication protocoll /Ubuntu/:
Hello,
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. -
WebUI V4.4.0 mismatch communication protocoll /Ubuntu/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. -
Database export errorHi Victor,
I was a little busy last week.
Here's what debug lvl 6 shows:
2020.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 -
Database export errorHi 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 -
Database export error@victor said in Database export error:
Hi,
what exact version you are using? Please show content of table "metadata".
Best regards,
VictorHi 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_83292And 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 -
Database export error@woody said in Database export error:
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
WoodyUpgrade works but error is still there
-
Database export errorHi,
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? -
Database export errorHi 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! -
Centralized agent upgradeHi,
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 -
Centralized agent upgradeHi,
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 -
solved -- netxmsd not working after Update@meandmybrain said in solved -- netxmsd not working after Update:
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,
SebastianProblem 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 -
solved -- netxmsd not working after UpdateHi 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 -
solved -- netxmsd not working after UpdateHi,
here are some other, maybe helpful things I figured out:
Bevor the update there was a "libnetxms.so.2" at /usr/lib/x86_64-linux-gnu; now there is a file "libnetxms.so.31".
It seems that libnxddr_pgsql.so is looking for a wrong file...? -
solved -- netxmsd not working after UpdateHi,
dpkg -l | grep netxms:
ii netxms-agent:amd64 3.1.242-2 amd64 NetXMS agent
ii netxms-base:amd64 3.1.242-2 amd64 NetXMS core libraries
ii netxms-dbdrv-pgsql:amd64 3.1.242-2 amd64 PostgreSQL driver for netxms-server
ii netxms-dbdrv-sqlite3:amd64 3.1.242-2 amd64 SQLite3 driver for netxms-server
ii netxms-release 1.6 all Package to install apt source and gpg keyring
iF netxms-server:amd64 3.1.242-2 amd64 meta packagenetxmsd.conf:
DBDriver = /usr/local/lib/libnxddr_pgsql.so
DBServer = localhost
DBName = netxms
DBLogin = xxxx
DBPassword = xxxxxxxx
LogFile = /var/log/netxmsd
LogFailedSQLQueries = yes -
solved -- netxmsd not working after UpdateHi,
I updated my netxms server today to version 3.1.242 using apt-get update && apt-get upgrade on Ubuntu 18.04 LTS.
While upgrading I get the following error-massage:"~$ sudo apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] j
netxms-server:amd64 (3.1.242-2) wird eingerichtet ...
NetXMS Database Manager Version 3.1.242 Build 3.1-242-g2c0fcdb3de (UNICODE)Unable to load and initialize database driver "/usr/local/lib/libnxddr_pgsql.so"
dpkg: Fehler beim Bearbeiten des Paketes netxms-server:amd64 (--configure):
installed netxms-server:amd64 package post-installation script subprocess returned error exit status 3
Trigger für libc-bin (2.27-3ubuntu1) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
netxms-server:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)"Netxmsd-service doesn`t came up.
debug 9 shows:
" sudo netxmsd -D 9
Using configuration file "/etc/netxmsd.conf"
2019.12.03 13:08:46.554 *D* [ ] LIB directory set to /usr/lib/x86_64-linux-gnu/netxms
2019.12.03 13:08:46.554 *I* [ ] Code page set to ISO8859-1
2019.12.03 13:08:46.555 *D* [dload ] DLOpen: file="/usr/lib/x86_64-linux-gnu/netxms/linux.nsm", module=0x7ff1e5078e00
2019.12.03 13:08:46.555 *D* [dload ] DLGetSymbolAddr: module=0x7ff1e5078e00, symbol=__NxSubAgentGetIfList, address=0x7ff1e476ef90
2019.12.03 13:08:46.555 *D* [dload ] DLGetSymbolAddr: module=0x7ff1e5078e00, symbol=__NxSubAgentGetArpCache, address=0x7ff1e476efc0
2019.12.03 13:08:46.556 *I* [ ] Platform subagent "/usr/lib/x86_64-linux-gnu/netxms/linux.nsm" successfully loaded
2019.12.03 13:08:46.556 *D* [dload ] DLOpen: file="/usr/local/lib/libnxddr_pgsql.so", module=(nil)
2019.12.03 13:08:46.556 *E* [db.drv ] Unable to load database driver module "/usr/local/lib/libnxddr_pgsql.so": libnetxms.so.2: cannot open shared object file: No such file or directory"
I tried reinstalling the pgsql driver but it didn`t help.I found some hint in another thread.
Using "ldd /usr/local/lib/libnxddr_pgsql.so"
I get the following massage:"linux-vdso.so.1 (0x00007ffe763d0000)
libnetxms.so.2 => not found
libpq.so.5 => /usr/lib/x86_64-linux-gnu/libpq.so.5 (0x00007f50249c5000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f50247c1000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f50245a2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f50241b1000)
libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f5023f24000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f5023a59000)
libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f502380e000)
libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007f50235bc000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5024e15000)
libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f50232e6000)
libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007f50230b4000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f5022eb0000)
libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f5022ca5000)
liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x00007f5022a97000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f502287c000)
libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007f5022661000)
libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 (0x00007f5022420000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f50220bb000)
libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007f5021eb7000)
libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 (0x00007f5021cae000)
libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 (0x00007f5021a21000)
libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 (0x00007f502177f000)
libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 (0x00007f5021549000)
libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 (0x00007f5021333000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f5021116000)
libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007f5020de7000)
libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 (0x00007f5020bca000)
libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 (0x00007f502084c000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f5020639000)
libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x00007f5020403000)
libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x00007f50201cf000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x00007f501ff4e000)
libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 (0x00007f501fd25000)
libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 (0x00007f501fb16000)
libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 (0x00007f501f8cc000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f501f5c3000)
libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f501f38b000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f501f183000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f501ede5000)"Unfortunatly I`m not a linux-expert, so I don`t know how this file is gone and how I can get it back.
Does anyone have some suggestions to solve this problem?
Thanks
Sebastian -
Wrong time on linechartsHi Victor,
netxms server and webserver are on the same machine, web console is opened from various windows 10 clients.
Tomcat:
Server version: Apache Tomcat/8.5.39 (Ubuntu)
Server built: Apr 10 2019 04:45:09 UTC
Server number: 8.5.39.0
OS Name: Linux
OS Version: 4.15.0-51-generic
Architecture: amd64
JVM Version: 11.0.3+7-Ubuntu-1ubuntu218.04.1Java version:
openjdk version "11.0.3" 2019-04-16
OpenJDK Runtime Environment (build 11.0.3+7-Ubuntu-1ubuntu218.04.1)
OpenJDK 64-Bit Server VM (build 11.0.3+7-Ubuntu-1ubuntu218.04.1, mixed mode, sharing)Best,
Sebastian -
Wrong time on linechartsHello,
when using netxms web-console, the time displayed in linecharts etc. is UTC, while on my clients it is CEST (UTC+2).
Both server and client are using ntp from the same timeserver.I searched the forum and found some suggestions, but nothing didn´t work for me. Maybe I did something wrong and can´t find this error.
Here are the time settings for my netxms server:Local time: Di 2019-06-11 09:50:25 CEST
Universal time: Di 2019-06-11 07:50:25 UTC
RTC time: Di 2019-06-11 07:50:25
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: noSettings on windows clients:
(UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien
settings for summertime are "automatic" and time is correct CEST
I also checked browsertime for IE11, Firefox and Chrome. It´s always CEST and at all of them the linecharts are showing UTC.
Netxms version is 2.2.13 on Ubuntu server 18.04 LTS.Has anyone a helpful hint for me to solve this problem?
Thanks and greetings
M.