-
Notifications
You must be signed in to change notification settings - Fork 61
Device initialization fails after successful provisioning #1757
Comments
Adding below a less detailed summary of the error as well for a quick look.
|
It looks like you are using the Community Edition, which is not very actively supported at the moment. Something must be wrong with your backend. The device thinks it is provisioned yet is getting 405s on
This also looks bad:
If you can't even fetch the first Root metadata from the Director, something is clearly not right with the Director. Note that libaktualizr will always try to fetch newer versions of the Root metadata, and if there isn't a newer one, it will complain, but that isn't necessary a problem. This, however, is the first Root. |
Thanks for the reply @patrickvacek Speaking about the director, the latest version in community edition is using director-v2, however I am still using director. Can I get an idea what's the basic difference ? |
Director was completely reimplemented to be more efficient, to drop unused features, and to make it easier to maintain. I don't know much about the details. I highly recommend using the new version. It also occurs to me that it is possible that you are using an old enough version of Director that still expects libaktualizr to fetch the unnumbered Root metadata. That requirement was dropped months ago (I don't know when exactly), so we removed that: #1661. (See #1501 for some more context.) |
@patrickvacek thanks for the useful input. My Director version is 5 month's old where as aktualizr is the most recent version. I would try to use a more recent version and see how it goes. |
@patrickvacek I upgraded to the latest configuration and now it throws error 400. What does this error code imply ?
|
Sorry, but I've never seen that error before and I don't know much about the backend. Possibly @jochenschneider or @houcros might be able to say more about the device gateway and/or director's behavior here. |
@patrickvacek , thanks for the pointers. As I wait to hear from anyone about any fix to the issue, would it be possible to know anything about the versions of server components (similar to this ) that you use for your test environment. For months I have been struggling to find the best match that can work together with recent version of aktualizr. I donot see any clear information available with aktualizr's release note stating the required versions of server components that must be available to work correctly. |
Unfortunately we do not have a chart of compatible versions. The aktualizr and meta-updater CIs use whatever is running on our production server, and we do most internal testing against an internal instance that is pretty similar. I don't have many details there but @alexhumphreys or @SusVlaAlex might. |
I've added the file |
Hi,
I am getting the following error message
Running at loglevel 0 I get the following logs:
Can I get some idea what's going wrong here ?
The text was updated successfully, but these errors were encountered: