I assume that by "terminate event" you mean "terminate alarm". Short answer is no - once terminated, alarm will remain only in alarm log. However, you can repeat threshold activation events (you can set that in threshold editor) and therefore recreate alarms, if threshold is still active. Everything else will not be repeated. Another way - revoke "terminate alarms" permission from user (leave only "Resolve"), then terminate with separate user (or even another person after verification that issue was solved).

Most likely it is caused by bug we have fixed recently in development branch. Fix should be included into upcoming 3.7 release. Best regards, Victor

Currently client does not have built-in terminal emulation to run interactive command line tools like putty inside GUI. It is quite complex task to implement (especially on Windows). Best regards, Victor

Looks like the following query fails silently: ALTER TABLE event_log RENAME TO event_log_v35_2; Which is very strange. You can try to run nxdbmgr upgrade with -t option, it will print all SQL statements being executed. This particular upgrade procedure is indeed TimescaleDB specific. Best regards, Victor

I managed to make it work by adding env variables, also my server and console containers was in different network spaces. Thanks for help! 

Hi Filipp, thank you so much, it works like a charm. Regards, Roberto

@pvo, thanks that did the trick.

After adding ping agent + all changes you suggested, all devices started to show.  Thank you very much, it is now working perfectly!

Hi, Filipp. I got it. Thanks !

Most likely you have broken gcc installation or some packages are missing. Make sure that you have installed: binutils, make, gcc-c++, bison, flex, openssl-devel, expat-devel, libcurl-devel, sqlite-devel, pcre-devel. Usually you do not need to specify location for openssl, pcre, etc. Best regards, Victor

I would restart the agent just to make sure, but you probably already did that. There could be a few ways for the agent to read another config then the default one running it with -c <config_file_name> running it with -M <server_ip> - it would get config file from server configuration policies that add up to the config - they reside in system32/config/systemprofile/appdata/local/nxagentd/config_ap/  (or other user home folder, if agent is started under other user, not system one).

Please add to the NXSL documentation on how to get array size. For those wondering, it's size attribute: array dataArray; dataArray = %(1, 2, 3); println dataArray->size; 3 Also, can we get the old NetXMS Wiki pages on NXSL functions moved over to the new NXSL documentation? A number of functions are still missing documentation.

Ethernet/IP is a protocol used on some industrial controllers, this message informs that netxms was not able to connect via this protocol. PDH error is related to windows performance counters. On configuration poll netxms is trying to read the list of performance counters. If this was successful, when adding a DCI of type "Windows performance counters" under "Select" button there will be a list of available counters. In node properties -> Polling it's possible to turn this off - "Disable reading of Windows performance counters metadata" checkbox. Here's an old post that mentions same PDH error: https://www.netxms.org/forum/general-support/problem-with-windows-performance-counters/

Thank You, noe I understood the way it works. That was a good tip. Best regards Stefan

Did you open User Manager recently? From the same netxms console, or from another machine? If you open Tools-> Server console, what is the output of show sessions command there? Does this error stays, if you close netxms management console and start it again? Most probably it will go away if you restart netxms server process.

Hi, I may not have clearly defined the issue but I have managed to solve this message filtering problem in the meantime through Event processing policy. I set up a script to filter by event content in a filtering script. if ($event->message ~= "something to filter") { return true; } I used regular expresions to filter the content of the event and thus run server actions only for messages that contain post text. For now, everything works so I hope I did it correctly Tomislav

MariaDB [(none)]> show status where variable_name = "innodb_page_size"; +------------------+-------+ | Variable_name    | Value | +------------------+-------+ | Innodb_page_size | 16384 | +------------------+-------+ The database was old. I upgraded to debian 10. I just did a dump, drop, create and restored of the database and known nxdbmgr upgrade is working and netxmsd is running again.

According this: https://www.netxms.org/forum/general-support/invalid-network-mask-4369/ and this: https://www.netxms.org/forum/general-support/invalid-network-mask/ The network mask on first device found in certain subnet is considered as correct one, but I didn't test it, I have these alarms disabled in my installation.

  [image: 179.jpg] BIG HUG FOR Filipp Sudanov NetXMS on CentOS 8 MariaDB Data was not written in the history. I was able to see "last values" but no history, no graphs. netxms data collection was not working (i add this for google searches) Thanks to Filipp : i learned to look for datas in "idata_xxx" tables i recompiled with mariadb options i changed netxmsd.conf to "DBDriver = mariadb.ddr" God bless you Filipp ! for the records : ./configure --with-server --with-mariadb --with-mariadb-compat-headers --with-agent /usr/local/etc/netxmsd.conf DBDriver = mariadb.ddr

If tables are already created - run "nxdbmgr upgrade"