Hi, that is the solution, thank you very much! Sincerely, Frank

Great, thank you Victor!

Thanks, would be great if this was prioritized as this will massively enhance the potential of NetXMS. One of its greatest strengths for us is the ability to very rapidly run summary DCI's to get all sorts of useful information in a simple clean page. Being able to then select multiple nodes out of compliance and simply right click->tools->run SSH script to resolve issues or push mass config updates is very powerful Ideally i'd like to see further updates to SSH down the track, such as credentials list, config backups, diff notifications (against last, or template baseline). But for now a simple working SSH command execution would be nice  ;D

Currently it is not possible. I think we should add SSH probe as part of configuration poll and handle it in a same way as SNMP credentials. It will also allow to generate relevant event when SSH is no longer responding. You may also try SSH authentication with private key - depending on your procedures it could be easier to just distribute key for NetXMS server once. Best regards, Victor

Hi, make sure that you have automake, autoconf, and libtool installed on your system. Also, 3.3 is fairly old version, I really recommend going with 3.9. Best regards, Victor

This is perfect. Node, MAC and IP are now back to normal! Thanks a lot! BB

Hi, isLocalManagement flag is set automatically. I suggest to find node that currently holds management server flag using object query or NXSL script, delete it, then set server configuration parameter RoamingServer to true and change primary IP address on node that should be local management server to 127.0.0.1. That way management node will be fixed. Best regards, Victor

Try DCF_DISABLE_CONF_POLL  instead

@filipp-sudanov said in Android Console doesn't show any dashboards: Android client was not updated for quite a long time, so some things may not work. Rewrite of android app is planned to start soon, so hopefully there will be a new version in the beginning of 2022. Hello, do you have an information about rewriting app? Is it still in plan to have a "new" version of app at beginning of 2022? I think it will be very pleased for a lot of users. Thank you verry much Tomas

Thank you. This Manual page helped immensely: https://wiki.netxms.org/wiki/NXSL:SNMPWalk The following works perfectly: // Call this function with the following parameters: // $1 = port number (eg 5900 for VNC) // $2 = IP address (xxx.xxx.xxx.xxx) transport = CreateSNMPTransport($node); if (transport == null) return -1; oid = ".1.3.6.1.2.1.6.13.1.4." . $2 . "." . $1 ; // IP connections vars = SNMPWalk(transport, oid); if (vars == null) return -2; // SNMPWalk failed count = 0; foreach (v: vars) { //trace(1, "SNMP WALK ".v->name."=".v->value); count = count +1; } return count;

Excellent!  I suspected that was the case as well and appreciate you confirming this.

I have termianted manually the alarm, and things look ok. I did this to make sure I get alarms in case something happens with that box, but the issue is still there status poll shows the node Normal now: [09.12.2021 17:11:14] Node is connected [09.12.2021 17:11:15] Finished status poll for node Dolion [09.12.2021 17:11:15] Node status after poll is NORMAL [09.12.2021 17:11:15] **** Poll completed successfully ****

So it's not that easy after all. Ubuntu changed compression inside deb files to zst, which is not (yet?) supported by Debian tools (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664). As a result I can't publish using existing tools (we run Debian for that). I will take another look at the problem later. DEBs temporary available here: https://netxms.org/tmp/impish/

You can use https://regex101.com/ to test your regular expressions. Currently your regex is not matching your example.

Support for Jira cloud is currently in development and should be available after some time.

Ticket was created, you can monitor the progress there: https://track.radensolutions.com/issue/NX-2177

There are some objects besides nodes that also have configuration poll, e.g. Clusters, which may not have the attributes that node objects have. You can check if the object is node in the beginning of your script, e.g. if (classof(p) == "Node") { ... }

If you open server log at debug level 6, do you see anything there when agent is trying to connect?

Victor, Thanks for the code correction!  Seems now that we are seeing this issue: https://www.netxms.org/forum/general-support/no-peer-in-object-details/ I looked at the switch of the device I was testing with and only 3 of the 15+ ports that have devices attached were showing a peer node.  Will wait for a release that addresses that issue and the do further testing.  Thanks!

Thank You Victor, after sqlite db modification update procedure continues and done successfully. Ok then i will create new base image and put it on dockerhub for other to use version with this manual fix. But upgrade from old image will still be not possible because after docker start i begin upgrading db schema, and if user have old sqlite db it will not upgrade correctly, nxdbmgr hangs and because it is in entry point of docker image, docker image will not start up netxms service and agent. Please it is possible make fix it into nxdbmgr, to do same manual fix? If it will be in new version i will release docker image with this fix, upgrade procedure will be automatic. @victor said in Database schema upgrade, sqlite: Next it tries to open second connection to database, which I suppose is not working for SQLite. Do you have any network maps configured? If you DO NOT have any network maps, you can do this step manually by executing the following queries (it will delete any configured links on network maps): DROP TABLE network_map_links; CREATE TABLE network_map_links ( map_id integer not null, link_id integer not null, element1 integer not null, element2 integer not null, link_type integer not null, link_name varchar(255) null, connector_name1 varchar(255) null, connector_name2 varchar(255) null, element_data varchar null, flags integer not null, color_source integer not null, color integer not null, color_provider varchar(255) null, PRIMARY KEY(map_id,link_id) ); CREATE INDEX idx_network_map_links_map_id ON network_map_links(map_id); UPDATE metadata SET var_value='9' WHERE var_name='SchemaVersionMinor'; And then run nxdbmgr upgrade again - it should continue from next step. Best regards, Victor