NetXMS Support Forum

Quote from: Dawid Kellerman on January 23, 2023, 09:32:49 AMHi Alex,
is the Fedora packages still in the pipeline or has it moved to a back burner?

Best Regards
Dawid

I've built and published fc36 and 37 packages to https://packages.netxms.org/fedora/, please try.

Repo file: https://packages.netxms.org/fedora/netxms.repo

I haven't tested it thoroughly, but I assume that it should work just fine.

Hi!

Yes, it's still in the pipeline, next patch release will include them.

I've published libexosip2-11_4.1.0-2.2 to our repository for Ubuntu 22 (jammie).
This package is not available in official Ubuntu repos since version 18(?) so we built it and keep in our repo. Forgot to publish it during initial setup.

UPDATE: it was not indexed due to dpkg changes in Ubuntu (repository is on Debian). Will take a while to rebuild package. In a meantime you can install it manually using attached deb file.

Hello.

Since 4.2 web UI require servlet API version 4 (but not version 5!), and jetty9 does not support that. Looks like we forgot to update it in windows installer.

Simplest solution is to install either Jetty10 or Tomcat9 as a standalone product and deploy war file there.

Hello!

Since latest release (4.2.395) we are releasing RPMs as well.
Right now we released packages for *EL (RHEL, Rocky, CentOS8, etc.), Fedora packages will follow.

Repository location: https://packages.netxms.org/epol/
Repository configuration file: https://packages.netxms.org/epel/netxms.repo

Simplest way to install: dnf config-manager --add-repo https://packages.netxms.org/epel/netxms.repo

All packages are build for both amd64 and aarm64.

There are no external dependencies except netxms-agent-mqtt, which requires EPEL repo to be enabled.

I've uploaded https://netxms.org/download/releases/4.1/nxmc-4.1.420-aarch64.dmg

Fixed in ee84926388, will be included in upcoming 4.2 release

I just realised that we do not support Variant in the responce - we'll add support in future releases

You need to define section "OPCUA" and add one or more "Server" parameters. Format for server record is "name:[login[/password]@]url" (parts in square brackets are optional)
You can also change timeout from defaul 5 seconds (parameter "Timeout", in ms).

Example:

[OPCUA]
Timeout=5000 # timeout for network operations
Server=s1:opc.tcp://milo.digitalpetri.com:62541/milo # anonymous connection
Server=s2:[email protected]://milo.digitalpetri.com:62541/milo # login "user1", empty password
Server=s3:user1/[email protected]://milo.digitalpetri.com:62541/milo # login "user1", password "password"

Once configured, you can collect metric OPCUA.NodeValue(server name, node id), where "server name" is s1, s2, etc. (values from configuration).

Example:
❯ nxget 127.0.0.1 'OPCUA.NodeValue(s1,ns=0;i=2257)'
Variant{value=DateTime{utcTime=133058236247170000, javaDate=Wed Aug 24 17:07:04 EEST 2022}}


What kind of error?

Hi

Yes, it's supported. You need to install new packages, then run "nxdbmgr upgrade". Don't forget to backup first.

Error is quite unexpected, but to be honest - we never tried such jump with packages. Which distro and version you are running?

You can upgrade this way:
mkdir ~/nx-backup
cp -R /etc/netxmsd.conf /etc/nxagentd.conf /var/lib/netxms ~/nx-backup
systemctl stop netxms-server
nxdbmgr check
apt-get --purge netxms\*
apt-get install netxms-server netxms-dbdrv-pgsql # select correct DB driver, additional packages if needed
systemctl stop netxms-server
cp ~/nx-backup/nxagentd.conf ~/nx-backup/netxmsd.conf /etc/
nxdbmgr upgrade
nxdbmgr check
systemctl enable --now netxms-server

Also I found an issue with plugin packaging, so bundled jar might not work.
Replace $NETXMS_HOME/lib/netxms/java/opcua.jar with this version: https://cloud.radensolutions.com/s/WazFQAC3KrnJpTM.

Check agent's log on debug level 1 or higher, there should be lines like
2022.09.19 15:47:54.074 *D* [                  ] Initializing Java subagent
2022.09.19 15:47:54.074 *D* [                  ] JAVA: Default JVM: /Users/alk/.asdf/installs/java/zulu-17.32.13/zulu-17.jdk/Contents/Home/lib//server/libjvm.dylib
2022.09.19 15:47:54.074 *D* [                  ] JAVA: using JVM /Users/alk/.asdf/installs/java/zulu-17.32.13/zulu-17.jdk/Contents/Home/lib//server/libjvm.dylib
2022.09.19 15:47:54.095 *D* [                  ] Java SubAgent created

If JVM is not found, you can set it with parameter "JVM=..." in "JAVA" section.

You can execute any action which is provided by the ageng (e.g. System.Restart). Also you need to select target object (where action will be executed).

List of actions can be queried from the agent, either with "nxget -l AGENT_IP Agent.ActionList" or in the GUI - right click on the node, then select Tools -> Info->Agent->Supported actions

Hi.

"pass" should be "password" in your config. Also debug tag "nc.*" should be "nc".

Correct confiration:

host=10.0.0.1
secondaryHost=10.0.0.2
login=user1
password=password1
mode=TEXT
mode can be either "TEXT" or "PDU". Secondary host is optional.

Sample session attached (added new notification channel and tried to send message to non-existing device):