NetXMS Support Forum

Hi,

it's more question regarding database engine then NetXMS itself. If you have DB files then most likely you can restore them - you should contact somebody with expertise in your DB engine. As soon as you'll get working database NetXMS server should start.

Best regards,
Victor

Hi,

description looks correct. Please send your nxagentd.conf (from server machine) and check agent log file on debug level 6 for any messages with prefix "SSH".

Best regards,
Victor

Hi,

we did some optimizations in syncer in 2.2.x for environments with lot of changes. I suggest considering upgrade to 2.2.x - there are good chances that those problems will go away.

Best regards,
Victor

Hi,

could you please register ticket in bug tracker for that? Seems it will need some investigation.

Best regards,
Victor

Hi,

packages for Ubuntu 14.04 (trusty) are published. Please check that you have correct source - should be:


deb https://packages.netxms.org/ubutu trusty main


Best regards,
Victor

Quote from: lweidig on February 06, 2018, 03:47:26 PM
Interested in the possibilities this might allow for:

QuoteFile I/O functions in NXSL (disabled by default)

Is there any documentation regarding the functions and their use.  Did a quick search, but have not found anything.  Thanks!

Just added documentation file file I/O functions here: https://wiki.netxms.org/wiki/NXSL_Function_Reference.

Best regards,
Victor

File jansson_private_config.h was not included into distribution package. Please download source package now - it should work.

Best regards,
Victor

Quote from: iGodunoff on February 06, 2018, 08:59:43 AM
nxagent-2.2.3.exe (Windows x86) can't be downloaded - 404 Not Found

Should be fixed now.

Hi,

for server build try to remove files src/server/libnxsrv/messages.c and src/server/libnxsrv/messages.h and re-run make. I'll check jansson build error.

Best regards,
Victor

Hi,

it is supposed to be. You can set listening port on server by changing parameter AgentTunnelListenPort, and on agent side you can specify port after : in ServerConnection parameter. However, due to a bug, agent will always connect to port 4703. It is fixed in current development branch and fix will be included into next release.

Best regards,
Victor

Just to make sure - are you using server from development branch (3.0)? Or your server is from 2.2.x branch? If latter, then I suggest to download matching version of web services API. Also, make sure you install NetXMS datasource for Grafana version 1.1.0.

Best regards,
Victor

Hi,

we just published release 2.2.3 which should include ssh.nsm.

Best regards,
Victor

Hi,

we were able to reproduce this issue on one machine (we never encounter this on our development machines). Will update as soon as we will found a solution.

Best regards,
Victor

Hi all!

NetXMS version 2.2.3 is out! Changes since previous release:

- Additional information about captured Windows Event Log event passed to the server
- Improved server startup time
- Automatic termination of related alarms when DCI is deleted
- Added attribute "isSTP" to NXSL class "Node"
- File I/O functions in NXSL (disabled by default)
- Sub-second interval between packets can be configured in PING subagent (down to 10 milliseconds)
- Fixed issues:
        NX-1149 (Pass EventRecordID with matched Windows event log record)
        NX-1258 (Option to pass event data from Windows event log to NetXMS event)
        NX-1259 (Added NXSL function - FindAlarmByKeyRegex)
        NX-1363 (Automatic deployment of agent policies)
        NX-1364 (Automatically create nodes for unbound agent tunnels)
        NX-1367 (Fix HP aCC compiler warnings)
        NX-1383 (Minimal interval before generating data collection script error events)
        NX-1389 (If library script saved with compilation errors it disappears from script list)
        NX-1392 (Reload log parser without agent restart)
        NX-1393 (PostgreSQL deadlock on updating raw_dci_data table)
        NX-1398 (Windows Server 2016 not detected correctly)
        NX-1399 (Some SQL queries fail when using MariaDB driver because of MariaDB bug CONC-281)

Best regards,
Victor

Hi,

likely old node was not deleted completely. Try to login with user "system", find that node, and delete it.

Best regards,
Victor