-
Notifications
You must be signed in to change notification settings - Fork 30
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
Code debug #100
Comments
@FRDavid , could you please post the example of the device that you are trying to provision? I will try to find where is the problem. |
Same problem here. It appears when executing a "connect" command from the client. For example:
All OK
It never shows a "connected succesfully" message. In fact, after 247 seconds, a timeout message araises. The agent log shows this:
Tested with docker Orion versions 0.26 and latest version. Mongodb docker version and non-docker versions, 3.2 and latest versions. Always the same result. Thanks in advance. |
This should be fixed once #105 is merged. |
Tested after the merge. Client log:
Agent log:
The error has gone :) |
Thanks for the feedback! Closing |
Hi Daniel, I am having this same problem please. May I know how to figure it out please. Timeout message raised after 247 seconds. Thank you |
Is the one already reported at #114 (comment) or a different one? |
Yes, it is.
Many thanks,
Akil
…On Tue, Sep 18, 2018 at 12:24 PM Fermín Galán Márquez < ***@***.***> wrote:
I am having this same problem please.
Is the one already reported at #114 (comment)
<#114 (comment)>
or a different one?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#100 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Aocds71SAcsHVqOQxgUbGcT5S85BXdEuks5ucNfSgaJpZM4QpvIu>
.
|
Ok. Let's continue dicussion in #114. |
Hi,
I checked the last changes (inclusion of last version of iotagent-node-lib) using my custom static mapping configuration already working with previous versions.
When the IOTAgent receives the registration from the device, it raises the following error:
I wonder know if there is some way to obtain debug information from errors in a deeper way (stacktrace).
The error appears using both device provisioning or static configuration.
(using device provisioning and mongodb)
(using static configuration and mongodb)
I didn't test with memory storage.
The text was updated successfully, but these errors were encountered: