Hello everyone, I did the instructions for the UseCase above exactly as it's stated but it just does not work. I want a single Node from an OPC-UA Testserver to be visible in my UNS. The error output looks like the following: --- [Bridge] [4:36:10 PM] - [left: 29 s] read flow config not yet applied. State: starting_redpanda, Status reason: starting: redpanda: starting: no success message found in logs; re-applying config: ReadDFC: Input config differences: - Input.opcua: exists in desired but missing in observed Output config differences: - Output.uns: exists in desired but missing in observed Pipeline config differences: - Processors differ (desired 2, observed 0) desired: [map[tag_processor:map[advancedProcessing:return msg; defaults:msg.meta.location_path = ... --- And this keeps repeating itself over and over again. Seems like there's some issue with Redpanda or whatever. What are possible mistakes or other flaws that lead to the issue?

We look into it!

Hey @Nils! Thanks you for the log. The real problem seems to be that Redpanda never fully starts. Because of that, your OPC-UA read flow can never be applied. It's not an OPC-UA problem yet, Redpanda seems to block everything. You could try these steps real quick: - Do a full restart of the umh-core container, not just a redeploy in the UI. This is the most common fix when Redpanda gets stuck like this. - Check how much CPU and RAM your container has. Redpanda needs a full CPU core and some extra memory. Give it at least 2 CPUs and 4GB RAM if you can. - If it's still stuck, open the Redpanda component itself and check its logs. Does it ever turn green, or does it stay grey/starting forever? - If Redpanda does turn green but the bridge still won't apply, check that your OPC-UA server is actually reachable from inside the container. "localhost" won't work if the test server runs on your host machine. Try host.docker.internal or your machine's real IP instead. If restarting doesn't help, please send us whether you run Docker or bare metal, which OS you are running, how much CPU/RAM you gave it. The logs from right when it starts (anything mentioning redpanda) would be helpful aswell. Then we can tell quickly if it's the Redpanda issue or something else.

Hey @Marius thanks for all the suggestions. I applied every single step from above (at first there were no resource restrictions for the container, now i set them to the designated values). The Redpanda broker might be the problem. The logs are full of messages. I am not sure if i want to share that. it's a lot. But Redpanda does never turn green. Also the host machine of the OPC-UA server can be reached from the container. I run umh in Docker on Ubuntu. CPU/RAM as mentioned above (4GB, 2 CPUs) Any other ideas? I can try to share part of the logs. And i will try to recreate the instance again and check the logs of Redpanda right from the beginning.

Recreating the instance is a good Idea aswell. You could send me the logs via DM, so you don't need to post everything in here :).