NetXMS Support Forum

В русском канале https://t.me/netxms_ru есть @me_is_nem0, он занимался драйверами для девайсов специфичных для РФ, попробуйте с ним пообщаться.

Даб там в логе Cannot compile report /var/lib/netxms/nxreportd/definitions/WAN-int-1.0.1/main.jrxml
 net.sf.jasperreports.engine.JRException: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 232; cvc-complex-type.3.2.2: Attribute 'uuid' is not allowed to appear in element 'jasperReport'.

Так что да, директория создалась, но скомпилироваться он не смог и поэтому его и в списке нет.

Я забыл упомянть выше, что нужна версия Jasper Studio 6.20.5 или младше. Тут похоже что версия более новая.

Я в принципе у claude такие вещи спрашиваю, вот его ответ по этой ошбике:
The error is a JRXML schema validation failure: the bundled JasperReports library in nxreportd is validating against an XSD that does
   not allow uuid on the root <jasperReport> element. This usually means the JRXML was produced by a Jaspersoft Studio newer than the
  JR runtime on the reporting server.

  A couple of options to unblock the deploy:

  1. Quick fix — open main.jrxml and delete the uuid="..." attribute from the <jasperReport ...> root tag, then rebuild. If validation then
   complains about uuid on a nested element (e.g. <band>, <textField>), strip those too. A one-shot scrub:
  sed -i 's/ uuid="[^"]*"//g' src/main/resources/main.jrxml
  2. Real fix — design the report in a Jaspersoft Studio version aligned with the JR library shipped with this NetXMS server. The two
  sample JRXMLs in this repo are produced with Jaspersoft Studio 6.16/6.19 (JasperReports Library 6.x), and they're known to deploy.
  Anything noticeably newer (7.x / 9.x) will emit XML features the server's older XSD rejects.

  For context: the samples in this repo (users/src/main/resources/main.jrxml and user-input/src/main/resources/main.jrxml) do carry
  uuid on <jasperReport> and deploy fine, so the user's server is matched to a stricter/older XSD than the one the samples were
  validated against — confirming the version-mismatch diagnosis. Designing with Studio 6.16–6.19 is the safest path.

Same happens on Ubuntu 26, created issue: https://github.com/netxms/netxms/issues/3250

Are you running Qwen locally? Under what tool?

The "XML tool call" output is what Qwen models emit at the raw model layer. Almost all production inference servers convert that into standard OpenAI JSON tool_calls before returning the response — so Qwen normally works fine with NetXMS if the inference server is configured to parse tool calls. For example:

- Ollama — works out of the box for Qwen models that ship with a tool-call template in their Modelfile. Point NetXMS at the Ollama provider and it will receive normal JSON tool_calls.
- vLLM — requires starting the server with --enable-auto-tool-choice --tool-call-parser hermes (or qwen3_coder for the newer parser). Then the OpenAI-compatible endpoint returns JSON tool_calls.
- SGLang / llama.cpp server — similar flags exist.

Which exactly is your NetXMS version?

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