The hostname is not necessarily unique like the MAC address. That is why the MAC address was originally chosen. Using the hostname would probably be okay for the emulator, it just hasn’t
been priority since the error doesn’t affect the running of the emulator.
Thanks,
--Dave
From:
<kura-dev-bounces@xxxxxxxxxxx> on behalf of Jens Reimann <jreimann@xxxxxxxxxx>
Reply-To: Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Date: Friday, August 11, 2017 at 00:10
To: Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Subject: Re: [kura-dev] Disabling cloud service?
Wouldn't using the systems hostname solve that issue for the emulator?
On Thu, Aug 10, 2017 at 8:16 PM, Woodard, David <david.woodard@xxxxxxxxxxxx> wrote:
Hello,
This is somewhat of a known issue in the emulator. The default client-id is the MAC address of the primary network interface.
The services used to retrieve the MAC information is significantly different in the emulator as compared to Kura running on a physical device. In many cases, the emulator can’t determine the MAC of the primary interface, so you get the clientId error. There
is a more general issue tracking this problem here [1]. It doesn’t affect the emulator, so it is more of an annoyance than anything.
Hope that helps.
[1]
https://github.com/eclipse/kura/issues/823
Thanks,
--Dave
Thanks Benjamin.
Turns out I was actually experiencing a different problem: for some reason unknown to me, on the simulator (on ubuntu
linux64) I get an exception: 'The configuration attribute clientId is required and no value has been set'. I mistook the exception on startup as a connect error without looking closely enough.
This is strange though because it says in the ui that if the client-id field is blank that some network address is
used. When I fill in the client-id field with an explicit value it goes away and so problem solved...but something must be going wrong with the auto client-id generation.
If you do not set the 'auto connect on startup' option of the DataService to true, your Kura instance should remain not connected to the broker unless
you explicitly connect e.g in the UI.
Le 10 août 2017 18:36, "Lewis, ScottX" <scottx.lewis@xxxxxxxxx> a écrit :
Hi,
In Kura 2.1.0...
I would like to temporarily disable the Kura Cloud service....i.e. to prevent the MqttDataTransport from connecting to any broker at all. I don't want to stop or remove the bundles...as they need to be there...but in some deployment situations I would like
to prevent the MqttDataTransport from attempting to connect at all.
I went to the Cloud Services UI /MqttDataTransport tab, but the broker-url can't be empty (which is the thing that I tried). Is there some other way to temporarily disable the MqttDataTransport on start?
Scott
_______________________________________________
kura-dev mailing list
kura-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kura-dev
_______________________________________________
kura-dev mailing list
kura-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kura-dev
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill
|