NetXMS Support Forum

Добрый день. Как я могу продиагностировать долгий старт сервера?
В log-е крайней записью как правило
[db.drv             ] Database driver "sqlite.ddr" loaded and initialized successfully
висит.
В это время по серверу гуляет нагрузка на единичные ядра до 100% от команды /usr/bin/netxmsd -S, IO по накопителям в покое
16 потоков
20Gb ОЗУ
SSD накопителем
На ВМ находится база, ядро netxms и веб-морда с tomcat.
При этом полный прогруз произошел после почти 2-ух часов с момента старта. До этого момента попытки коннекта на веб-морду\клиент ловили refuse

Hi,

is this feature in active development?
I'm not able to provide remote access but maybe some snmpwalks can help?


Kind regards

I went back to look at this again and continued to have the same issue. 

I checked for error messages in the nxmc.log file as you suggested, and checked again after using the buttons, but saw no errors that looked like they were related to buttons, or launching a browser, or anything. 

Since it had been a while since I had worked on this, and at the time I was doing a number of other things, I decided to go back and double check everything from the beginning.  I checked the Object Tools to ensure they were there and looked correct, and then I removed the buttons from the dashboard, and re-added them.   I then saved, and tried this dashboard under the device, and the buttons worked correctly for the device's context. 

So, this does/did seem to be something wrong with my dashboard or object tools, somehow.    I have no idea what I did, but it does seem to work correctly.   Sorry for the hassle. 

Hi

I have a network map where some map links between nodes configured with Set peer option just disappeared, even one FDB auto link disappeared as well. I tried clearing and set peer again but no luck.
While all other links work fine.
How can I troubleshoot this?
I tried setting "Debug level for tag "obj.netmap" set to 9" but that doesn't produce any extra logs.

Thanks

Kind regards
Sid

I'm a novice user at NetXMS, so bear with me about technical terms, but link/binding or not, should not limit the ability to add discovered nodes.

Here is the log from a node with 192.168.1.205, which does not get added.

root@netxms01:~# tail /var/log/netxmsd -n 2000 | grep 192.168.1.205
2025.10.23 12:07:23.989 *D* [poll.discovery    ] Active discovery - node 192.168.1.205 responded to ICMP probe via proxy TEST-TEST-DESKTOP-4VOF9D3 [74588]
2025.10.23 12:07:23.989 *D* [poll.discovery    ] Checking address 192.168.1.205 in zone 8 (source: Active Discovery)
2025.10.23 12:07:23.990 *D* [poll.discovery    ] New node queued: 192.168.1.205/24
2025.10.23 12:07:23.991 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): MAC address is not known, will lookup in ARP caches
2025.10.23 12:07:24.010 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): found MAC address F0:9F:C2:C3:43:E0
2025.10.23 12:07:24.010 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): filter flags=0000
2025.10.23 12:07:33.540 *D* [poll.discovery    ] HostIsReachable(192.168.1.205): agent connection check failed with error 910 (Connect failed)
2025.10.23 12:07:39.982 *D* [poll.discovery    ] Active discovery - node 192.168.1.205 responded to SNMP probe via proxy TEST-TEST-DESKTOP-4VOF9D3 [74588]
2025.10.23 12:07:39.982 *D* [poll.discovery    ] Checking address 192.168.1.205 in zone 8 (source: Active Discovery)
2025.10.23 12:07:39.983 *D* [poll.discovery    ] New node queued: 192.168.1.205/24
2025.10.23 12:07:39.983 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): MAC address is not known, will lookup in ARP caches
2025.10.23 12:07:40.118 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): found MAC address F0:9F:C2:C3:43:E0
2025.10.23 12:07:40.118 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): filter flags=0000
2025.10.23 12:07:45.212 *D* [poll.discovery    ] Active discovery - node 192.168.1.205 responded to SNMP probe via proxy TEST-TEST-DESKTOP-4VOF9D3 [74588]
2025.10.23 12:07:45.212 *D* [poll.discovery    ] Checking address 192.168.1.205 in zone 8 (source: Active Discovery)
2025.10.23 12:07:45.213 *D* [poll.discovery    ] New node queued: 192.168.1.205/24
2025.10.23 12:07:45.213 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): MAC address is not known, will lookup in ARP caches
2025.10.23 12:07:45.301 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): found MAC address F0:9F:C2:C3:43:E0
2025.10.23 12:07:45.301 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): filter flags=0000
2025.10.23 12:07:49.696 *D* [poll.discovery    ] HostIsReachable(192.168.1.205): agent connection check failed with error 910 (Connect failed)
2025.10.23 12:07:54.848 *D* [poll.discovery    ] HostIsReachable(192.168.1.205): agent connection check failed with error 910 (Connect failed)
2025.10.23 12:08:19.293 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): host is not reachable
2025.10.23 12:08:19.293 *D* [poll.discovery    ] ProcessDiscoveredAddressStage1(192.168.1.205): address discarded
2025.10.23 12:08:35.267 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): host is not reachable
2025.10.23 12:08:35.267 *D* [poll.discovery    ] ProcessDiscoveredAddressStage1(192.168.1.205): address discarded
2025.10.23 12:08:40.513 *D* [poll.discovery    ] AcceptNewNodeStage1(192.168.1.205): host is not reachable
2025.10.23 12:08:40.513 *D* [poll.discovery    ] ProcessDiscoveredAddressStage1(192.168.1.205): address discarded


Добрый день

Наблюдаю по запросу sh disc ranges вот такую картину

Active discovery poller is RUNNING
Address ranges:
   192.168.16.1-192.168.16.254          completed
   10.3.1.1-10.3.254.254                completed
   10.6.1.1-10.6.254.254                processing
   10.8.1.1-10.8.254.254                pending
   192.168.1.1-192.168.36.254           pending

Не меняется его состояние этак с момента установки ренджей, т.е. пару месяцев точно. При этом разные ноды добавляются. Как мне понять на чем он споткнулся и можно ли перезапустить вручную этот процесс? Debug 6 на poll.discovery около нечитаем, спам безбожнейший

Не дочитал сразу статью про апгрейд, а ведь там была эта инфа, спасибо!

Found the issue, docker ran with POSIX had to add

ENV LANG=C.UTF-8
ENV LC_ALL=C.UTF-8

Now it works with åäö

Tested with agent running on full debian 12 VM and no issue with åäö in action making this something with my docker setup it seems like.

it is the official docker setup from github though, will see if i have messed something up.

#!/bin/sh
# /agent/script/ping.sh
LOG=/agent/script/logs
mkdir -p "$LOG"

TS="$(date -u +%Y%m%dT%H%M%SZ)"
{
  echo "----- $TS -----"
  echo "PWD: $(pwd)"
  echo "USER: $(id)"
  echo "ARGV_STR: $*"
} >> "$LOG/ping.txt"

printf '%s\n' "$@" | od -An -t x1 >> "$LOG/ping-bytes.hex" 2>/dev/null || true

i tried Action=debug:echo "$1" >> /agent/script/a.txt also to have it as simple as possible and
$node.executeAgentCommand("debug","test") creates a.txt containing test
$node.executeAgentCommand("debug","testå") does not create a.txt, not error in agent log just "Execution of external action debug (echo "testå" >> /agent/script/a.txt) started"

If i run echo "testå" >> /agent/script/a.txt manually in same docker agent is running a.txt is created as utf8 and containing testå