Azure / iot-edge-opc-proxy

OPC Proxy Module
34 stars 19 forks source link

Failed to create iothub registry #77

Closed lcao8 closed 6 years ago

lcao8 commented 7 years ago

I did a docker build on the latest and when I ran it against an IoT Hub in the azure cloud, I am getting the following error and proxyd terminated. I am running it on centos 7. I don't see the error if I run older builds from docker hub.

docker run -it --network=host proxyd -c "HostName=sch-cf805a3.azure-devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=****"

=== Azure iot-edge-reverse-proxy 1.0.3. ===

[Pid=1:Tid=0xf543db48 15:30:36.548] root NOTICE Pal does not provide credential storage support. Ensure you properly safeguard all secrets on this device! [pal_cred_init:21] ERROR: Failed to create iothub registry from --connection-string supplied connection string.

Operation failed.

JuergenKosel commented 7 years ago

You need to avoid, that the shell interprets the special characters in the connection string! Use ' instead of " Or provide the connection string in a file.

lcao8 commented 7 years ago

Thanks for the quick response!

I changed " around the connection string to ', still got the same error.

docker run -it --network=host proxyd -c 'HostName=sch-cf805a3.azure-devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=****'

marcschier commented 7 years ago

Were you able to debug this? If not I suggest using 1.0.2 for now. It is what we use in our connected factory simulation.

lcao8 commented 7 years ago

I haven't got a chance to debug this. I switched to 1.0.2 for the azure connected factory. It does work much better. Thanks!

marcschier commented 6 years ago

I reproduced this with ", or ' quoting on windows. I fixed this by trimming quotes from the connection string passed through command line. Fix will be in 1.0.4, and is currently in 1.0.4 branch

gasherma commented 6 years ago

This is fixed in the latest version. If you still see the issue, please reopen it.