Vnodes cannot be registered although they are defined in vnodes.conf. The respective nodes are active and can be “seen” on the agents Windows section.
Hi, @mawashi. Can you elaborate on the issue? Where do you see “Vnodes cannot be registered”? UI? Logs? Can you post a screenshot?
The nodes are active and can be “seen” under the parent agent, there is a vnodes.conf that describes them but when i try to declare the vnode hostname in the dynamic configuration i get an error message.
The corresponding log is :
"…DYNCFG: plugin returned code 400 to user initiated call: config go.d:collector:windows:PCD190381 test PCxxxxxxx
The structure if the vnodes.conf file has been tested with a YAML checker and the same Vnodes.conf file works for vnodes in the lines above
This means that either
- the Vnode value you specified is different from the value in
vnodes.conf vnodes.confis not readable by netdata (no vnodes registered).
Thanks for your reply,
is it possible for the vnodes.conf file to work for lines 1-96 and not work for lines 96 - EOF;
Does it have to be netdata user the owner of the vnodes.conf file;
Is there a limit to the number of nodes per agent; I have deleted and re configured the last batch of 22 nodes that are not ecognized as VNODES and still get the same result
this is the log of the error I get only but for new nodes / Vnodes I configure
netdata
DYNCFG: plugin returned code 400 to user initiated call: config go.d:collector:windows:Pxxxxxxx1 test Pxxxxxxx1
CODE_FILE
/usr/src/netdata/src/daemon/config/dyncfg-intercept.c
CODE_FUNC
dyncfg_function_intercept_result_cb
CODE_LINE
112
INVOCATION_ID
0da6aa95b19045b7aa2c9fb24608dddc
ND_LOG_SOURCE
daemon
ND_MODULE
plugins.d[go.d.plugin]
ND_NIDL_NODE
fxxxxxx.xxx.xx
ND_SRC_TRANSPORT
pluginsd
PRIORITY
3
SYSLOG_IDENTIFIER
netdata
THREAD_TAG
PD[go.d]
TID
111595
_BOOT_ID
837ebab15f534644bf6895dbaacd5d5b
_CAP_EFFECTIVE
0
_CMDLINE
/opt/netdata/bin/srv/netdata -P /run/netdata/netdata.pid -D
_COMM
netdata
_EXE
/opt/netdata/bin/srv/netdata
_GID
983
_HOSTNAME
fsu1236.nll.se
_MACHINE_ID
2e68465314f641efa7812d27a8992892
_PID
111435
_SELINUX_CONTEXT
system_u:system_r:unconfined_service_t:s0
_SOURCE_REALTIME_TIMESTAMP
1726643682130404
_SYSTEMD_CGROUP
/system.slice/netdata.service
_SYSTEMD_INVOCATION_ID
0da6aa95b19045b7aa2c9fb24608dddc
_SYSTEMD_SLICE
system.slice
_SYSTEMD_UNIT
netdata.service
_TRANSPORT
journal
_UID
983
__CURSOR
s=20d3255a70464b1b989d4268a544ed24;i=4224;b=837ebab15f534644bf6895dbaacd5d5b;m=120c628afa;t=6225f8f53c193;x=4c43066ba854d84c
__MONOTONIC_TIMESTAMP
77517196026
__REALTIME_TIMESTAMP
1726643682132371
Maybe this is the reason;
[mqtt_wss] W: client_id provided is longer than 23 bytes, server might not allow that [MQTT-3.1.3-5]