NetXMS Support Forum

Для ExternalParameterShellExec подстановку параметров можно делать через $1, $2, и т.д. Например

ExternalParameterShellExec = Test_SMS:php /home/netxms/Documents/sms/sms.php "$1" "$2"

Серверная команда тоже должна работать. Посмотрите лог сервера на уровне 5 - должны быть записи вида "Executing command ..." и "RunCommandThread: failed to execute command ..." при ошибке.

Hi all!

NetXMS version 3.4 is released. Changes since previous release:

- Improved topology based event correlation
- New methods in NXSL class "Node": getInterfaceByIndex, getInterfaceByMACAddress, getInterfaceByName
- Method getInterface in NXSL class "Node" automatically detects if parameter is interface index, name, or MAC address
- Added built-in NXSL constant NXSL::SystemIsBigEndian
- Added NXSL hook for alarm state change (Hook::AlarmStateChange)
- Can pass arguments to NXSL script executed as EPP action
- Implemented agent metrics for available and cache memory on AIX
- New agent parameter WindowsFirewall.State on Windows
- Implemented disk latency parameters in Linux agent (System.IO.WaitTime, System.IO.ReadWaitTime, System.IO.WriteWaitTime)
- User agent tooltip message can be set via policy
- Fixed issues:
        NX-470 (Hooks or events for alarm state change)
        NX-763 (File Tail/Show should not access database directly)
        NX-811 (System.IO.WaitTime unsupported on Linux)
        NX-1043 (Windows installer cannot initialize Oracle database)
        NX-1078 (Event correlation not working)
        NX-1152 (Attempt to upload .npi pointing to non-existing installer lock up package manager on Windows)
        NX-1176 (Handle routing loops during event correlation)
        NX-1524 (Server configuration wizard is not visible on task bar)
        NX-1556 (Add HMAC to every record in audit log table)
        NX-1566 (NXSL Script Action to allow for parameters)
        NX-1739 (When a node goes down and it's upstream port on a switch goes down, do not correlate those events)
        NX-1753 (File downloads from agent and file upload to server should be logged to Audit Log)
        NX-1801 (Strange if condition)
        NX-1832 (Export configuration does not detect referenced NXSL scripts within NXSL scripts)
        NX-1837 (Store out of the box object tools as .xml files, not in database initialization script)
        NX-1846 (Server crash when querying Audit Log)
        NX-1848 (Add getGuid method to org.netxms.client.events.EventTemplate class in Java API)
        NX-1853 (User Agent Notifications view in management console has no means to hide old notifications)
        NX-1854 (When double-clicking a stacked graph in performance tab, it opens in a new view as non-stacked)
        NX-1856 (Text in tooltip for user support application should be configurable)
        NX-1860 (Parameters to get state of each Windows Firewall profile separately)
        NX-1861 (Unable to add USM Credentials when zoning is ON)
        NX-1862 (Lazy object synchronization breaks object-based link status display on maps)
        NX-1865 (Remote Node using TLS Tunnel Added incorrectly if same name is resolvable on local NetXMS network)
        NX-1866 (NXSL GetAvgDCIValue may not work with MySQL database)
        NX-1867 (NXSL GetMaxDCIValue may return incorrect value)

Best regards,
Victor

Похоже на проблему со структурой базы. А если сделать nxdbmgr check перед миграцией, будут какие-то ошибки?
Еще возможный вариант - что теряются права на объекты. Попробуйте после миграции зайти пользователем system - возможно он увидит все объекты.

Hi,

if port names on different links are the same then this is definitely a bug. Could you provide interface list for two nodes connected with excessive links (content of "Interfaces" tab)?

Best regards,
Victor

Looks like coincidence - we didn't make any specific changes in graphs. But let's hope it will stay fixed.

Best regards,
Victor

Hi all!

We just published patch release 3.3.350 for version 3.3. It contains multiple minor fixes accumulated over last few weeks and partially already published for specific components. Full change log since initial 3.3 release:

- Replace backslash and comma as part of host and DCI names normalizing in InfluxDB driver
- Fixed bug in socket error reporting for agent tunnels
- Fixed VMGR subagent crash
- Fixed bug in agent policy deployment in 2.x compatibility mode
- Fixed bug in database export
- Fixed bugs in SIP registration testing in Asterisk subagent
- Fixed memory leak in Asterisk subagent
- Fixed bug in template import on server startup
- Fixed server crash on agent certificate renewal
- Fixed server crash when proxied SNMP device responds with "UDP port unreachable"
- Added driver for Moxa industrial routers
- Fixed issues:
        NX-1575 (Ability to duplicate event configuration)
        NX-1780 (Unable to add file to file delivery policy in management console on MacOS)
        NX-1839 (Show alarm key in Alarm Details)
        NX-1844 ('Get list of agent sessions' error in nxmc and webui)
        NX-1845 (Context menu for Service Root shows Create sensor twice)
        NX-1855 (NETXMS_FILE_STORE environment variable not using FileStore agent setting)
        NX-1868 (Zone SNMP Configuration SNMP v3 "Modify" button spelt incorrectly)
        NX-1869 (Environment variables in file delivery policy expanded on save)

Best regards,
Victor

Есть старый feature request на эту тему: https://track.radensolutions.com/issue/NX-470. По идее добавить несложно, можно будет сделать в 3.4 или 3.5.

Это отдельный war файл который можно так-же как и Web UI поставить на любой Java application server (Jetty, Tomcat, etc.).

How server side log looks like for that tunnel? Also, please try this agent version: https://netxms.org/download/releases/3.3/nxagent-3.3.350-x64.exe - it fixes incorrect error code display in "SSL read error" message so we could see actual socket error code that could provide some clue.
Another thought - could it be that you have some kind of DPI device between agent and server that detects SSL handshake and blocks connection for some reason?

Best regards,
Victor

Yes, this should solve the issue. Duplicate records are definitely a bug, but keeping them will not help in debugging it anyway.

Best regards,
Victor

Hi,

it looks like duplicate records in source table, although it is quite strange because PostgreSQL schema should have timestamp as part of primary key as well. Please try to run query

SELECT * FROM idata_164 WHERE item_id=1227 AND idata_timestamp=1589846471;

on original database - how many records it will produce?

Best regards,
Victor

Please check that your server certificate has CA constraint set to TRUE. You can do that by printing certificate in text form with command like this:

openssl x509 -text -noout -in server.crt

and look for "X509v3 Basic Constraints" section. For example, my test server's certificate looks like this (only relevant part of the output):

        X509v3 extensions:
            X509v3 Basic Constraints:
                CA:TRUE


Best regards,
Victor

Hi,

I did some testing on my system, and I can get this error if TCP/IP is disabled in native client configuration. Check "Client Protocols" section under "SQL Native Client 11.0 Configuration" in "SQL Server Configuration Manager".

Best regards,
Victor

Hi,

all seems going well until this point:

2020.06.02 06:04:06.788 *D* [tunnel             ] 192.168.10.6: SSL_write error (bytes=-1 ssl_err=5 errno=2)

SSL error 5 means underlying socket error, which is strange because SSL negotiation seems to be completed successfully. Are you using server version 3.3.x as well? Can you check what was logged in server log during that attempt?

Best regards,
Victor

Hi,

currently no.

Best regards,
Victor