API Key not enabled

[somnium78]

Bug report summary

Log says API Key not enabled after Upgrade

OS / Environment

Ubuntu 18.04

Netdata version (ouput of netdata -V)

netdata v1.14.0-rc0-52-g6c9e8e83

Component Name

stream.conf

Steps To Reproduce

stream.conf on master:
[50db0d35-fdf2-4cd4-af3e-xxxxx]
enabled = yes
allow from = *
default history = 3600
default memory mode = save
health enabled by default = no
default postpone alarms on connect seconds = 60
multiple connections = allow

stream.conf on slave:
[stream]
enabled = yes
destination = xxxxx.de:19999
api key = 50db0d35-fdf2-4cd4-af3e-xxxxx
timeout seconds = 60
default port = 19999
buffer size bytes = 1048576
reconnect delay seconds = 5
initial clock resync iterations = 60

Log on Master:
2019-04-15 13:46:15: STREAM: 5756 '[xxxxx::234]:36086' 'ACCESS DENIED - KEY NOT ENABLED' host 'xxxxx.de' api key '50db0d35-fdf2-4cd4-af3e-xxxxx' machine guid '8de5a5d8-38f5-11e8-ada5-xxxxx'
2019-04-15 13:46:15: 361: 5756 '[xxxxx::234]:36086' 'STREAM' (sent/all = 67/67 bytes -0%, prep/sent/total = 1555328775049.72/1555328775049.75/0.02 ms) 401 'key=50db0d35-fdf2-4cd4-af3e-xxxxx&hostname=xxxxx.de&registry_hostname=yyyyy.de&machine_guid=8de5a5d8-38f5-11e8-ada5-xxxxx&update_every=2&os=linux&timezone=Europe/Berlin&tags='

Log in Slave:
2019-04-15 13:46:35: netdata INFO : STREAM_SENDER[xxxxx.de] : STREAM xxxxx.de [send to xxxxx.de:19999]: connecting...
2019-04-15 13:46:35: netdata INFO : STREAM_SENDER[xxxxx.de] : STREAM xxxxx.de [send to xxxxx.de:19999]: initializing communication...
2019-04-15 13:46:35: netdata INFO : STREAM_SENDER[xxxxx.de] : STREAM xxxxx.de [send to xxxxx.de:19999]: waiting response from remote netdata...
2019-04-15 13:46:35: netdata ERROR : STREAM_SENDER[xxxxx.de] : STREAM xxxxx.de [send to xxxxx.de:19999]: server is not replying properly (is it a netdata?).
2019-04-15 13:46:40: netdata LOG FLOOD PROTECTION too many logs (201 logs in 181 seconds, threshold is set to 200 logs in 1200 seconds). Preventing more logs from process 'netdata' for 1019 seconds.

Expected behavior

[cakrit]

I just looked at this and replicated the issue. Top priority, we're looking into it now.

[cakrit]

I rechecked my configuration and had a wrong key. As soon as it was corrected, it worked fine.

Can you please ensure that the config files you showed in the OP are in the correct places (i.e. /etc/netdata) and that both master and slave have been restarted to read them? It's clearly a case of API key mismatch, so the config you have must work, unless it's not the one actually being used.

[somnium78]

i restarted netdata very often to analyze the problem.

I was able to get it running by deleting my Netdata instances. After the reinstallation everything works with the above configuration.
Maybe there is a problem upgrading from an older version (I haven't installed any updates since March 2018).