issue while generating the image and the mender artifact about aws-iot-jobs-full-system-update HOT 14 CLOSED

Thanks for reporting this. Apparently the mender-convert tool has changed.

from aws-iot-jobs-full-system-update.

You can try cloning again the mender-convert repo using

git clone -b 1.2.2 https://github.com/mendersoftware/mender-convert.git

The 1.2 version should be compatible with the current script. I'll provide a fix for using the latest mender-convert.

from aws-iot-jobs-full-system-update.

Thanks massi now from

You can try cloning again the mender-convert repo using

git clone -b 1.2.2 https://github.com/mendersoftware/mender-convert.git

The 1.2 version should be compatible with the current script. I'll provide a fix for using the latest mender-convert.

Thanks massi .... I am able to bulid image now and other steps ...
but if you could help with this the agent Failed with exit code

and goagent logs are

from aws-iot-jobs-full-system-update.

I cannot reproduce the issue as it works fine on my device. Is the certificate status "ACTIVE" in AWS IoT Core? Does it have a policy allowing the device to connect? Can you ping the aws iot endpoint you have specified in the /etc/goagent/goagent.conf file?

from aws-iot-jobs-full-system-update.

Yes certificate is Active in Aws IoT core. Policy is there and I am able to ping the endpoint that i have specified in goagent.conf file.

from aws-iot-jobs-full-system-update.

I see that now it is working fine. Have you found out why you were getting the error?

from aws-iot-jobs-full-system-update.

I see that now it is working fine. Have you found out why you were getting the error?

No it is not working stuck there and logs are same as mentioned.

from aws-iot-jobs-full-system-update.

I see. As I cannot reproduce the issue, I need your help to get to the root cause of the problem.

Can you try to connect to the same endpoint, using the same certificates using another MQTT client? You can use the pubsub.py sample in https://github.com/aws/aws-iot-device-sdk-python-v2/tree/master/samples.

Usage : https://github.com/aws/aws-iot-device-sdk-python-v2/tree/master/samples#pubsub

Let me know if you can connect with that.

from aws-iot-jobs-full-system-update.

I see. As I cannot reproduce the issue, I need your help to get to the root cause of the problem.

Can you try to connect to the same endpoint, using the same certificates using another MQTT client? You can use the pubsub.py sample in https://github.com/aws/aws-iot-device-sdk-python-v2/tree/master/samples.

Usage : https://github.com/aws/aws-iot-device-sdk-python-v2/tree/master/samples#pubsub

Let me know if you can connect with that.

Yes massi, I am able to connect with same certs and same endpoint with another MQTT client.

from aws-iot-jobs-full-system-update.

I found the issue and fixed it.
Checkout the repo again using the -b mender-1.2 switch (see README) and then try generating the image again.
Make a copy files folder with your changes before doing a new checkout or use a different folder and then copy those files back

from aws-iot-jobs-full-system-update.

I found the issue and fixed it.
Checkout the repo again using the -b mender-1.2 switch (see README) and then try generating the image again.
Make a copy files folder with your changes before doing a new checkout or use a different folder and then copy those files back

Hello Massi,
Thanks for your time .Now device is connected and subscribed successfully using
git clone -b 2.2.0 https://github.com/mendersoftware/mender-convert.git.

While Monitoring the progress of AWS IoT Jobs it stucks in queued.

from aws-iot-jobs-full-system-update.

I found the issue and fixed it.
Checkout the repo again using the -b mender-1.2 switch (see README) and then try generating the image again.
Make a copy files folder with your changes before doing a new checkout or use a different folder and then copy those files back

Hi Massi need your help with this jobs stuck in queued state.

Thanks

from aws-iot-jobs-full-system-update.

The job is waiting for the thing that you targeted to receive it.

Check that clientId and thingName in the /etc/goagent/goagent.conf file match the thingName selected for the job.

from aws-iot-jobs-full-system-update.

Thanks for giving me your valuable time.

from aws-iot-jobs-full-system-update.