Is anyone familiar with these "
# umh-support
d
Is anyone familiar with these "connection refused" errors? My custom data bridges are working when testing in Node-RED, but the UMH infrastructure seems to be struggling with something https://cdn.discordapp.com/attachments/984083100520808478/1328805842786586715/image.png?ex=67880a60&is=6786b8e0&hm=8cd303274a7d4c9979baeb25cfe818f692735f49fd191ba388c6385291325809&
I think I found the cause of this problem because I manage to reproduce it with the following mistake: The problem occurred when I was recreating my bridges by manually copy-pasting code from GitHub. Sometimes, when I created a new Custom Component, I would mistakenly type the name of the bridge into the "Version Overwrite (expert mode)" field: https://cdn.discordapp.com/attachments/1328805843118067804/1328853412887924817/image.png?ex=678836ae&is=6786e52e&hm=9abfae4296ed2bfc4b9b9aa0c4e75e6e817d4c43ce2dd1b3622d2cf5b2b88e65&
This brings down Redpanda and seemingly the whole UMH. (My bad... I guess that's why there's an "expert mode" warning 😅 ) @Jermuk @Ferdinand you may want to have a look at this. CC @Luke van Enkhuizen
j
How can this being down redpanda? If at all, it should result in an unstable DFC
Let us check
d
Yes, but that unstable DFC leads to the Warning and Error in the second image
Can you recommend a blog/video explaining how to dig deeper into issues like this? More specifically, how to read log files from k3s
By the way, everything works now. So I'm 99% positive that the issues were caused by me abusing the Version Overwrite feature
f
These are from redpanda, but they look fine. Most services output a couple of warnings on startup
2 Views