From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2018.02 Mosquitto v1.4.15 : no CONNECT/CONNACK on libmosquitto
Date: Tue, 27 Mar 2018 21:02:32 +0200 [thread overview]
Message-ID: <20180327210232.4692d68a@windsurf.home> (raw)
In-Reply-To: <CALmdmcBazaBmEVUiCL3N6kCV4AgSp2Duqv2=iPzy1uUSTyCYyQ@mail.gmail.com>
Hello,
On Tue, 27 Mar 2018 17:46:57 +0200, Alexis Lothor? wrote:
> I have been using libmosquitto in C for quite some time in buildroot (used
> in an EFL mainloop) and it works well. Here are some quick details about
> how I currently use it :
> * C API to create a client
> * I use callbacks API to set callbacks on logs, connect/disconnect events,
> publish/susbscribe events and so on
> * connection uses TLS (certificate provided to API)
> * once connected, Mosquitto file descriptor is provided and integrated to
> EFL main loop
>
> I recently switched to buildroot 2018.02 (it has upgraded mosquitto from
> v1.4.14 to v1.4.15), and I am now encountering a new issue with the lib.
> Trying to establish a new connection to my broker (using the
> mosquitto_connect API), I can see that a new TCP connection is opened onto
> the broker, but it seems that no MQTT data is transfered (i.e. no CONNECT
> event), so the broker, of course, does not answer the usual CONNACK
> (observed with tcpdump).
> I have made sure that the issue only happens in v1.4.15. Quickly taking a
> look on Eclipse Github, I saw no specific issue directly linked to this
> problem.
> Before diving more in depth in this issue on mosquitto code, I would like
> to ask here : is there anyone encountering the same issue with this new
> mosquitto version ? I did not see any comment about this in the mailing
> list, but maybe the release is too young so it has not been detected yet ?
> Or anyone can confirm that this new version, used as client with C API,
> works on its side ?
Did you try reverting commit f4df4a18e5dd4702f842e61ee815f13afd93c366,
to bring back mosquitto to the 1.4.14 version ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-27 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 15:46 [Buildroot] Buildroot 2018.02 Mosquitto v1.4.15 : no CONNECT/CONNACK on libmosquitto Alexis Lothoré
2018-03-27 19:02 ` Thomas Petazzoni [this message]
2018-04-02 10:19 ` Peter Korsgaard
2018-04-02 12:00 ` Thomas Petazzoni
2018-04-02 12:41 ` Peter Korsgaard
2018-04-02 21:11 ` Alexis Lothoré
2018-04-02 21:42 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180327210232.4692d68a@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.