aws_iot_shadow and aws_iot_mqtt _connect

[POOVARASAN784]

I successfully received an AWS IoT MQTT Job on my ESP32 device and sent the required data to AWS IoT Shadow. After completing this process, I disconnected from AWS IoT Shadow. However, the AWS IoT Job remains in a pending state and does not transition to 'SUCCEEDED' or 'FAILED'
I (45764) aws_iot_mqtt_jobs: Sending JOB_EXECUTION_SUCCESS TO AWS
I (45774) mbedtls: ssl_tls.c:8985 => write

I (45774) mbedtls: ssl_tls.c:3617 => write record

I (45774) mbedtls: ssl_tls.c:1543 => encrypt buf

I (45774) mbedtls: ssl_tls.c:1920 <= encrypt buf

I (45784) mbedtls: ssl_tls.c:3019 => flush output

I (45784) mbedtls: ssl_tls.c:3038 message length: 182, out_left: 182

I (45794) mbedtls: ssl_tls.c:3043 ssl->f_send() returned 182 (-0xffffff4a)

I (45804) mbedtls: ssl_tls.c:3071 <= flush output

I (45804) mbedtls: ssl_tls.c:3750 <= write record

I (45814) mbedtls: ssl_tls.c:9013 <= write

I (45814) aws_iot_mqtt_jobs: Update Status Sent to AWS
I (60824) aws_iot_mqtt_jobs: UnSubscribing AWS_MQTT_JOBS
I (60844) mbedtls: ssl_tls.c:8985 => write

I (60844) mbedtls: ssl_tls.c:3617 => write record

I (60844) mbedtls: ssl_tls.c:1543 => encrypt buf

I (60854) mbedtls: ssl_tls.c:1920 <= encrypt buf

I (60854) mbedtls: ssl_tls.c:3019 => flush output

I (60864) mbedtls: ssl_tls.c:3038 message length: 66, out_left: 66

I (60864) mbedtls: ssl_tls.c:3043 ssl->f_send() returned -80 (-0x0050)

W (60874) mbedtls: ssl_tls.c:3746 mbedtls_ssl_flush_output() returned -80 (-0x0050)

W (60884) mbedtls: ssl_tls.c:8932 mbedtls_ssl_write_record() returned -80 (-0x0050)

I (60894) mbedtls: ssl_tls.c:9013 <= write

E (60894) aws_iot: failed! mbedtls_ssl_write returned -0x50 I (60904) mbedtls: ssl_tls.c:8569 => read

I (60904) mbedtls: ssl_tls.c:4591 => read record

I (60914) mbedtls: ssl_tls.c:2800 => fetch input

I (60924) mbedtls: ssl_tls.c:2961 in_left: 0, nb_want: 5

I (60924) mbedtls: ssl_tls.c:2985 in_left: 0, nb_want: 5

I (60934) mbedtls: ssl_tls.c:2986 ssl->f_recv(_timeout)() returned 5 (-0xfffffffb)

I (60944) mbedtls: ssl_tls.c:3006 <= fetch input

I (60944) mbedtls: ssl_tls.c:2800 => fetch input

I (60954) mbedtls: ssl_tls.c:2961 in_left: 5, nb_want: 112

I (60954) mbedtls: ssl_tls.c:2985 in_left: 5, nb_want: 112

I (60964) mbedtls: ssl_tls.c:2986 ssl->f_recv(_timeout)() returned 107 (-0xffffff95)

I (60974) mbedtls: ssl_tls.c:3006 <= fetch input

I (60974) mbedtls: ssl_tls.c:2086 => decrypt buf

I (60984) mbedtls: ssl_tls.c:2640 <= decrypt buf

I (60994) mbedtls: ssl_tls.c:4665 <= read record

I (60994) mbedtls: ssl_tls.c:8861 <= read

I (61004) mbedtls: ssl_tls.c:8569 => read

I (61004) mbedtls: ssl_tls.c:8861 <= read

I (61014) mbedtls: ssl_tls.c:8569 => read

I (61014) mbedtls: ssl_tls.c:8861 <= read

I (61014) aws_iot: JOB_UPDATE_TOPIC / accepted callback
I (61024) aws_iot: topic: $aws/things/CN0008/jobs/bwcn0008_data/update/accepted
I (61034) aws_iot: payload: {"timestamp":1740505924}
I (61034) mbedtls: ssl_tls.c:8569 => read

I (61044) mbedtls: ssl_tls.c:4591 => read record

I (61044) mbedtls: ssl_tls.c:2800 => fetch input

I (61054) mbedtls: ssl_tls.c:2961 in_left: 0, nb_want: 5

I (61064) mbedtls: ssl_tls.c:2985 in_left: 0, nb_want: 5

I (61064) mbedtls: ssl_tls.c:2986 ssl->f_recv(_timeout)() returned 5 (-0xfffffffb)

I (61074) mbedtls: ssl_tls.c:3006 <= fetch input

I (61084) mbedtls: ssl_tls.c:2800 => fetch input

I (61084) mbedtls: ssl_tls.c:2961 in_left: 5, nb_want: 31

I (61094) mbedtls: ssl_tls.c:2985 in_left: 5, nb_want: 31

I (61094) mbedtls: ssl_tls.c:2986 ssl->f_recv(_timeout)() returned 26 (-0xffffffe6)

I (61104) mbedtls: ssl_tls.c:3006 <= fetch input

I (61114) mbedtls: ssl_tls.c:2086 => decrypt buf

I (61114) mbedtls: ssl_tls.c:2640 <= decrypt buf

I (61124) mbedtls: ssl_tls.c:5450 got an alert message, type: [1:0]

I (61134) mbedtls: ssl_tls.c:5465 is a close notify message

W (61134) mbedtls: ssl_tls.c:4649 mbedtls_ssl_handle_message_type() returned -30848 (-0x7880)

W (61144) mbedtls: ssl_tls.c:8634 mbedtls_ssl_read_record() returned -30848 (-0x7880)

E (61154) aws_iot: Error Unsubscribing JOB_GET_PENDING_TOPIC: -12
E (61164) aws_iot_mqtt_jobs: Unable to Unsubscribe AWS_MQTT_JOBS ---> -12
I (61184) mbedtls: ssl_tls.c:8985 => write

I (61184) mbedtls: ssl_tls.c:3019 => flush output

I (61184) mbedtls: ssl_tls.c:3038 message length: 66, out_left: 66

I (61194) mbedtls: ssl_tls.c:3043 ssl->f_send() returned -78 (-0x004e)

W (61194) mbedtls: ssl_tls.c:8915 mbedtls_ssl_flush_output() returned -78 (-0x004e)

I (61204) mbedtls: ssl_tls.c:9013 <= write

E (61214) aws_iot: failed! mbedtls_ssl_write returned -0x4e I (61214) mbedtls: ssl_tls.c:9028 => write close notify

I (61224) mbedtls: ssl_tls.c:3019 => flush output

I (61234) mbedtls: ssl_tls.c:3038 message length: 66, out_left: 66

I (61234) mbedtls: ssl_tls.c:3043 ssl->f_send() returned -78 (-0x004e)

I (61244) mbedtls: ssl_tls.c:9237 => free

I (61244) mbedtls: ssl_tls.c:9302 <= free

I (61254) aws_iot_mqtt_jobs: Disconnected from AWS_MQTT_JOBS
E (61264) ESP: Unable to Disconnect AWS_MQTT_JOBs ---> -12
I (71284) aws_iot_mqtt_jobs: UnSubscribing AWS_MQTT_JOBS
E (71284) aws_iot: Error Unsubscribing JOB_GET_PENDING_TOPIC: -13
E (71294) aws_iot_mqtt_jobs: Unable to Unsubscribe AWS_MQTT_JOBS ---> -13
E (71304) aws_iot_mqtt_jobs: Error unable to disconnect from AWS_JOBS -13

[xuelix]

Could you share your code on how the mqtt connection was established?

[aggarg]

Did you update the job status - https://docs.aws.amazon.com/iot/latest/developerguide/jobs-mqtt-api.html?