-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with Demo "Discovering and Using OPC UA Thermometers" #724
Comments
Hi @PE-29012018, thank you for your question! Can you help us debug by providing the logs on the Akri agent, OPC UA discovery-daemonset and simulated OPC PLC pods? It could possibly be that our image for the OPC PLC may be outdated so I want to make sure. |
Hello @yujinkim-msft, I have tried the following demo. I have used the configuration files as in the demo. With the following input: I will send you a few logs below. If more logs are needed, I can send them to you. kubectl logs opcplc-576cbcdbc8-9vgjc -n default
kubectl logs akri-opcua-discovery-daemonset-2f89h -n default
kubectl get pods
kubectl get crds | grep akri
kubectl logs akri-agent-daemonset-df4lm -n default
kubectl logs akri-webhook-configuration-6b7b8c68-gxpsn -n default
kubectl get akric
kubectl get pods -l app=opcplc
systemctl status containerd
|
@PE-29012018 thank you for providing the logs. can you retry with the latest version of Akri? we have just made a release: v0.13.8 and may help to resolve this issue. When you go through the steps again, try |
Discussed in #723
Originally posted by PE-29012018 November 14, 2024
Hello everyone,
I am currently testing the demo ‘Recognising and using OPC UA thermometers’.
I can set up the OPC UA servers (without security) without any problems.
I can also install Akri as in the example. I can also see the required CRDs.
When I run ‘kubectl get akric’, I also see akri-opcua-monitoring.
However, as soon as I run ‘kubectl get akrii’ as required by the next step, I get no output.
What could be the reason for this?
The text was updated successfully, but these errors were encountered: