You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When starting the opc-publisher in standalone mode in the edge simulator, I get a certificate error (see trace below). The same configuration works on a regular deployed Azure IoT Edge server. Other modules can be simulated.
I tried the latest version as well as the preview 3 version. While the latest version is constantly restarting the opc-publisher module the preview 3 version can connect as a client to an existing opc-server. Outgoing messages (from opc-publisher --> edge runtime) fail.
The following traces are from using the preview version:
The text was updated successfully, but these errors were encountered:
I tried it with different command line arguments. The most basic configuration was the following:
"modules": {
"OPCPublisher": {
"env": {},
"restartPolicy": "always",
"settings": {
"image": "mcr.microsoft.com/iotedge/opc-publisher:2.9.0-preview3",
"createOptions": {
"Hostname": "publisher",
"Cmd": [
"--aa",
"--di=60"
]
}
},
"status": "running",
"type": "docker"
}
}
The whole EdgeSolution is based on the default deployment.json and opcpublisher is the only module running
Describe the bug
When starting the opc-publisher in standalone mode in the edge simulator, I get a certificate error (see trace below). The same configuration works on a regular deployed Azure IoT Edge server. Other modules can be simulated.
I tried the latest version as well as the preview 3 version. While the latest version is constantly restarting the opc-publisher module the preview 3 version can connect as a client to an existing opc-server. Outgoing messages (from opc-publisher --> edge runtime) fail.
The following traces are from using the preview version:
The text was updated successfully, but these errors were encountered: