-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Bridging to AWS IoT keeps failing with "Socket error on client local.xyz.awsiot, disconnecting." #1486
Comments
you look like you're missing "try_private false" |
Thanks, just tried both |
AWS does not support Retained messages but you are publishing a retained message:
https://docs.aws.amazon.com/iot/latest/developerguide/mqtt.html |
This is same with Google IoT, see https://cloud.google.com/iot/docs/requirements#mqtt_bridge. |
Thanks you’re right, publishing without retain flag works. Unfortunately we need the messages retained on the primary broker. Is there any way to clear the flag before forwarding it to AWS or Google? |
@ralight seems like this commit was never merged in the later versions after it. Do you know if there is at this time a workaround? |
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@dengxian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->Hi For me, the problem is that I used the same client ID for different devices script, hence it keep disconnecting. I gave an unique client ID for each of my device and the problem disappear. Regards Sent from Mail for Windows 10 From: Kaj Van der HallenSent: Friday, 16 October 2020 3:37 PMTo: eclipse/mosquittoCc: AikHong; CommentSubject: Re: [eclipse/mosquitto] Bridging to AWS IoT keeps failing with "Socket error on client local.xyz.awsiot, disconnecting." (#1486) @ralight seems like this commit was never merged in the later versions after it. Do you know if there is at this time a workaround?—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.
|
I'm also running into this issue. It would be really useful to have this forgotten feature integrated. |
I just stumbled upon this as well. Given I'm not a developer and there's no released version of this means I'd have to go back to the actual devices to manage retain. The option of turning this off completely or even by topic would be a great addition to the broker. However I'm not sure what's involved or whether there is demand for this. @mludvig are you saying bridging your main broker to (remote) Mosquitto works even with messages containing retain=yes? If yes, my workaround may have to be to run an instance of Mosquitto on say AWS or check out the IBM Watson IoT service. |
As the topic is still open, posting for those who will be looking for similar info about "retain". Changelog for v2.0.0 (https://mosquitto.org/ChangeLog.txt) mentions: |
I'm trying to bridge a local broker to two remote brokers - one is Mosquitto based and the second one is AWS IoT. For some reason the connection to AWS IoT keeps closing all the time with
Socket error on client local.xyz.awsiot, disconnecting.
. The Mosquitto connection works well.Here is my sample
mosquitto.conf
...When I start
mosquitto
with this config it seems to connect to both endpoints:However as soon as I publish a message to the local broker the AWS IoT connection starts crashing:
I'm pretty sure it's not the AWS IoT configuration or the SSL certificates because with
mosquitto_pub
with the same certs I can submit messages to AWS IoT.I'm using the latest mosquitto 1.6.7 on Linux Mint 19.1 and on Ubuntu 18.04, getting the same issue.
The text was updated successfully, but these errors were encountered: