NetXMS Support Forum

Great, thanks for the update

Something like this was reported due to some dashboard elements leaking resources. Please try upgrading to 6.1

In the original log parser policy editor screenshot you have Level set to 1, but in XMLs you have values 2 and 3.

А в event log, у этого события есть что-нибудь в Root ID? Если есть, то что за событие с таким ID?

Error #1 might be related to cookies on client side - this is an issue when we switch framework version used for nxmc. Clearing cookies should help.

#2 - created https://github.com/netxms/netxms/issues/3236 for this. You can set Server.Color in Configuration->Server Configuration, it will change background under the text

#3 which exactly part of GUI is this?

Just tried to send via Gmail both on Linux and Windows 10, it worked fine. This is the configuration I've used:

Server=smtp.gmail.com
Port=587
TLSMode=STARTTLS
[email protected]
Password="xxxxxxxxxxxxxxxx"
[email protected]
FromName=NetXMS Server
IsHTML=no

Interesting part is Gmail shows app password with spaces, but password should go without spaces.

Is time on your Windows machine correct? What kind of Windows it is? You can try installing NetXMS server on another Win machine and copy notification channel configuration there.

Obviously this is due to https://github.com/netxms/netxms/commit/272d0338b1 commit that went into v. 6.1. - previously server accepted any traps, with this is validates SNMP trap credentials.

Can you please do a tcpdump capture for the IP of that node to see what exactly community string is coming from that node.

Pls try with v. 6.1.2, some fixes were done there.

Hi,

What are these events from, some RAID software?
Pls double-click on the event in Windows Event viewer and show XML View from Details tab.

Open-Source AI Assistant includes the following skills: data-collection, event-processing, inventory, maintenance, incident-analysis, log-analysis, device-backup with approx 70 functions.

Enterprise stuff is accessible via the same AI Assistant and adds a few more skills: network-topology, nxsl (script library + compile/execute), scheduler-management, asset-management, file-management, ssh, file operations via agent and a few more for ATM/banking switch monitoring. scheduler-management allows things like "check this node's DCI values in the morning", etc.

Also things are dynamic here and changes / new skills may be added.

Here's the current list of open-source AI Assistant features:

  Top-level functions:
  - alarm-list — active alarms
  - clear-notification-queue
  - explain-object-status
  - find-objects (name/IP/class/parent/zone)
  - get-notification-channels
  - get-object
  - get-object-ai-data / set-object-ai-data / list-object-ai-data-keys / remove-object-ai-data — persistent per-object AI memory
  - send-notification
  - server-stats
  - snmp-read / snmp-walk

  Skill: data-collection
  - create-metric / edit-metric / delete-metric / get-metric-details / get-metrics
  - get-historical-data (with aggregation)
  - get-thresholds / get-object-thresholds / add-threshold / edit-threshold / delete-threshold

  Skill: event-processing
  - create-event-template / modify-event-template / delete-event-template / get-event-template
  - get-event-processing-policy
  - get-event-processing-action / get-event-processing-actions

  Skill: inventory
  - get-node-hardware-components
  - get-node-interfaces
  - get-node-software-packages

  Skill: maintenance
  - start-maintenance / end-maintenance

  Skill: incident-analysis
  - get-incident-details / get-open-incidents / get-incident-history
  - get-incident-related-events / get-incident-topology-context
  - add-incident-comment
  - link-alarm-to-incident / link-alarms-to-incident
  - assign-incident / suggest-incident-assignee
  - create-incident / create-incident-from-alarms

  Skill: log-analysis
  - list-logs / get-log-schema / search-log
  - search-syslog / search-windows-events / search-snmp-traps / search-events
  - get-log-statistics
  - correlate-logs (cross-source, with L2 neighbors)
  - analyze-log-patterns (frequency/burst/recurring/new)

  Skill: device-backup
  - get-backup-status / get-backup-list / get-backup-content
  - start-backup
  - compare-backups

Looks to be a bug, I've created a ticket for this
https://github.com/netxms/netxms/issues/3219

There are now special custom attributes:

ssh.login
ssh.password
ssh.port

so e.g. %{ssh.port} macro should work

Правой кнопкой по ноде, которая прокси, Change zone... и там выбрать зону.

Текущую зону ноды видно на закладке Overview в разделе Communications. 

В приложении тестовый отчет (он есть на гитхабе: https://github.com/netxms/sample-report, там есть чуток инфы в readme). На Линуксе его надо положить в директорию /var/lib/netxms/nxreportd/definitions, репортинг сервер его должен подцепить - это проявится тем что там должна появится директория users-1.0.0.

В настройках сервера адрес репортинг сервера нужно написать именно в IPv4 виде - 127.0.0.1, потому что localhost может раскрывать в IPv6, а репортинг его не умел.

Если не хочет работать, покажите лог репортинга
journalctl -u netxms-reporting.service

I've created a ticket for this: https://github.com/netxms/netxms/issues/3214