Aws-iot-device-sdk-python-v2: message='Koneksi terputus tiba-tiba.', code=5134 region us-west-1

Dibuat pada 1 Feb 2021 · 7Komentar · Sumber: aws/aws-iot-device-sdk-python-v2

Konfirmasikan dengan mengubah [ ] menjadi [x] di bawah ini untuk memastikan bahwa itu adalah bug:

[X] Saya telah mencari masalah serupa sebelumnya dan tidak menemukan solusi apa pun

Masalah yang Diketahui

[X] Saya menggunakan titik akhir tipe data ATS: titik akhir akan terlihat seperti <prefix>-ats.iot.<region>.amazonaws.com
xxxxxxxxx-ats.iot.us-west-1.amazonaws.com

Jelaskan bugnya
Pergi melalui "Memulai - dan Daftarkan Perangkat"
Mendapat sertifikat, kunci pribadi, kunci publik, dan CA

Nomor versi SDK
2 (python3)

Platform/OS/Perangkat
Apa yang Anda menjalankan SDK pada?
Ubuntu

Mereproduksi (perilaku yang diamati)
Langkah-langkah untuk mereproduksi perilaku (harap bagikan kode)
Sampel pub/sub sederhana
python3 pubsub.py --endpoint xxxxxxxxxx-ats.iot.us-west-1.amazonaws.com --root-ca root-CA.crt --cert zztest.cert.pem --key zztest.private.key -- debug verbositas

 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [penjadwal tugas] - id=0x7fc744013750: Menjadwalkan tugas socket_handler_close untuk segera dieksekusi
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [penjadwal tugas] - id=0x7fc7440021b0: Menjalankan tugas epoll_event_loop_unsubscribe_cleanup denganstatus
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [penjadwal tugas] - id=0x7fc744013750: Menjalankan tugas socket_handler_close denganstatus
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [channel] - id=0x7fc744002770: handler 0x7fc7440136b0 shutdown di dir tulis selesai.
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [penjadwal tugas] - id=0x7fc744002798: Menjadwalkan tugas (null) untuk segera dieksekusi
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [penjadwal tugas] - id=0x7fc744002798: Menjalankan tugas (null) denganstatus
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [channel] - id=0x7fc744002770: selama shutdown, membatalkan tugas 0x7fc744013920
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [penjadwal tugas] - id=0x7fc744013920: Menjalankan tugas tls_timeout denganstatus
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [channel] - id=0x7fc744002770: selama shutdown, membatalkan tugas 0x7fc74402de40
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [penjadwal tugas] - id=0x7fc74402de40: Menjalankan tugas mqtt_connack_timeout denganstatus
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [channel-bootstrap] - id=0x10f7550: channel 0x7fc744002770 shutdown dengan kesalahan 0.
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [saluran] - id=0x7fc744002770: menghancurkan saluran.
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75343a700] [channel-bootstrap] - id=0x10f7550: melepaskan referensi bootstrap
 Traceback (panggilan terakhir terakhir):
 File "pubsub.py", baris 130, di
 connect_future.result()
 File "/usr/lib/python3.6/concurrent/futures/_base.py", baris 432, dalam hasil
 kembalikan diri.__get_result()
 File "/usr/lib/python3.6/concurrent/futures/_base.py", baris 384, di __get_result
 angkat diri._pengecualian
 awscrt.exceptions.AwsCrtError: AwsCrtError(name='AWS_ERROR_MQTT_UNEXPECTED_HANGUP', message='Koneksi ditutup tiba-tiba.', kode=5134)
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75814b740] [mqtt-client] - id=0x12fbb80: pengguna disebut disconnect.
 [ERROR] [2021-02-01T06:03:41Z] [00007fc75814b740] [mqtt-client] - id=0x12fbb80: Koneksi tidak terbuka, dan mungkin tidak ditutup
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75814b740] [mqtt-client] - id=0x12fbb80: Refcount terakhir pada koneksi telah dirilis, mulailah menghancurkan koneksi.
 [DEBUG] [2021-02-01T06:03:41Z] [00007fc75814b740] [mqtt-client] - id=0x12fbb80: Menghancurkan koneksi

Perilaku yang diharapkan
Deskripsi yang jelas dan ringkas tentang apa yang Anda harapkan terjadi.
pesan terus diterbitkan

Log/keluaran
Jika berlaku, tambahkan log atau keluaran kesalahan.

INGAT UNTUK SANITASI INFORMASI PRIBADI ANDA

awscrt.io.init_logging(awscrt.io.LogLevel.Warn, 'stderr')

konteks tambahan
Tambahkan konteks lain tentang masalah di sini.

Ini tampaknya agak konyol dan membingungkan ...

Mengapa ada 2 hal berbeda yang disebut IoT Core di konsol manajemen?
Saat ini saya bekerja di wilayah us-west-1 (N. California) ...
Dikatakan untuk salah satu dari mereka IoT Core tidak didukung - lalu Jika saya mengklik ikon lainnya dikatakan demikian, dapatkah Anda menjelaskannya?

dan inilah yang berfungsi di us-west-1

Atau tidak berhasil? apakah itu akar masalahnya ... berhasil tetapi tidak berhasil ... : P

closed-for-staleness guidance

Sumber

supertick

Komentar yang paling membantu

Saya merasa sangat bodoh sekarang, kesalahan bagi saya adalah saya belum mengaktifkan sertifikat di konsol IoT. Ini adalah sesuatu yang bodoh tetapi bisa membantu orang lain

hackaprende pada 18 Feb 2021

🚀1 ❤1 👍1

Semua 7 komentar

Versi python3 dan Ubuntu apa yang Anda gunakan? Juga izin apa yang Anda gunakan untuk kebijakan IAM? Sepertinya Anda mengalami masalah dengan koneksi, jadi saya sarankan memulai dengan AWSIoTFullAccess untuk mengesampingkan masalah kebijakan Anda. Pastikan untuk membatasinya hanya pada tindakan dan sumber daya yang benar-benar Anda butuhkan nanti.

AWSIoTAkses Penuh:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "iot:*"
            ],
            "Resource": "*"
        }
    ]
}

Adapun konten tambahan yang Anda sebutkan salah satunya memiliki iot di url sementara yang lain memiliki iotv2 . Yang mana yang bekerja untuk Anda?

jmklix pada 2 Feb 2021

Terima kasih atas tanggapannya jmklix.
Apa yang Anda sarankan khusus untuk MQTT?
Saya membuat soket web berfungsi tetapi hanya dengan kredensial .aws yang menurut kasus penggunaan kami tidak diinginkan.
Bisakah soket web mengautentikasi dan memberi otorisasi menggunakan file sertifikat (xxxx.pem xxx.private.key xxx.public.key) yang digunakan mqtt?

Ya saya menangkap url iot/iot2 ... apakah ada beberapa dokumentasi yang menjelaskan perbedaan antara dua versi inti iot?
Ada juga 2 klien python sdks afaik - satu untuk python 2.7 yang lain untuk python 3, apakah ada lebih banyak perbedaan? apakah mereka dipasangkan erat dengan versi inti iot & iot2? Apakah mereka kompatibel lintas atau belakang? Apakah ada dokumentasi untuk ini?

supertick pada 3 Feb 2021

Ya, itu untuk MQTT. Tidak, Anda tidak dapat menggunakan file sertifikat dengan soket web

Anda dapat mengedit kebijakan untuk IoT things yang sudah dibuat di konsol AWS. Pilih thing dan pilih keamanan pada bilah sub-sisi. Di sana Anda akan melihat sertifikat dan Anda ingin memilih sertifikat itu. Setelah itu terbuka pilih kebijakan di bilah sub-sisi. Kemudian pilih kebijakan itu dan terakhir klik Edit policy document dan rekatkan AWSIoTFullAccess yang saya cantumkan sebelumnya. Kebijakan default tidak berfungsi dengan sdk v2. Tolong beri tahu saya jika Anda membutuhkan penjelasan tambahan.

Url iot adalah yang ingin Anda gunakan karena iotv2 seharusnya tidak lagi terlihat dan akan segera dihapus. Python dan iot sdk tidak tergantung satu sama lain dan tidak memiliki hubungan. iot v1 mendukung python 2 dan 3 sedangkan iot v2 hanya mendukung python 3. iot sdk tidak kompatibel lintas atau belakang dan dokumentasi untuk v2 api dapat ditemukan di sini .

jmklix pada 3 Feb 2021

Saya memiliki masalah yang sama, saya menggunakan kebijakan @jmklix yang disertakan di atas, membuat sertifikat baru secara manual, menautkannya ke IoT Thing dan Kebijakan dan mengunduh .pem, kunci pribadi, dan root-CA seperti ini:

python3 shadow.py --endpoint xxxxxxxxxx-ats.iot.us-east-2.amazonaws.com --root-ca root-CA.crt --cert 726290b105-certificate.pem.crt --key 726290b105-private.pem.key --thing-name MyThingName

Contoh shadow.py mengatakan bahwa --cert harus dalam format .pem, jadi saya juga mencoba dengan 726290b105-certificate.pem

Kesalahan yang sama terjadi dengan contoh pubsub.py.

Saya menggunakan pi Raspberry dengan Python 3.

Mencoba menginstal dengan PyPI dan menginstal dengan sumber.

Kesalahan terjadi di connected_future.result() dalam contoh shadow.py.

Saya memiliki komponen yang diterbitkan menggunakan MQTT mirip dengan sampel ipc_greengrass.py dan berfungsi dengan baik.

Kecurigaan saya adalah saya melakukan sesuatu yang salah ketika memasukkan kunci, sertifikat dan --rood-ca. Meskipun saya memeriksa ulang format file. Saya mendapatkan kesalahan ini:

Traceback (most recent call last):
  File "shadow.py", line 275, in <module>
    connected_future.result()
  File "/usr/lib/python3.7/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/usr/lib/python3.7/concurrent/futures/_base.py", line 384, in __get_result
    raise self._exception
awscrt.exceptions.AwsCrtError: AwsCrtError(name='AWS_ERROR_MQTT_UNEXPECTED_HANGUP', 
message='The connection was closed unexpectedly.',
code=5134)

Berjalan dengan --verbosity --debug

[INFO] [2021-02-18T19:57:17Z] [b7b6bec0] [event-loop] - id=0xa4371f0: Initializing edge-triggered epoll
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [event-loop] - id=0xa4371f0: Eventfd not available, falling back to pipe for cross-thread notification.
[INFO] [2021-02-18T19:57:17Z] [b7b6bec0] [event-loop] - id=0xa4371f0: Starting event-loop thread.
[INFO] [2021-02-18T19:57:17Z] [b7b6bec0] [dns] - id=0xa42b310: Initializing default host resolver with 16 max host entries.
[INFO] [2021-02-18T19:57:17Z] [b7050b40] [thread] - id=0xa3eeb8c: a cpu affinity was specified when launching this thread and set_mempolicy() is available on this system. Setting the memory policy to MPOL_PREFERRED
[WARN] [2021-02-18T19:57:17Z] [b7050b40] [thread] - id=0xa3eeb8c: call to set_mempolicy() failed with errno 38
[INFO] [2021-02-18T19:57:17Z] [b7b6bec0] [channel-bootstrap] - id=0xa44d200: Initializing client bootstrap with event-loop group 0xa43ea60
[INFO] [2021-02-18T19:57:17Z] [b684fb40] [event-loop] - id=0xa4371f0: main loop started
[INFO] [2021-02-18T19:57:17Z] [b684fb40] [event-loop] - id=0xa4371f0: default timeout 100000, and max events to process per tick 100
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [tls-handler] - ctx: Certificate and key have been set, setting them up now.
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [tls-handler] - ctx: Setting ALPN list x-amzn-mqtt-ca
Connecting to <endpoint> with client ID 'test-1e0e6e8b-ee1f-441d-8956-69aaedcb937d'...
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - client=0xa4ee030: Initalizing MQTT client
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - id=0xa450e40: Creating new connection
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-topic-tree] - tree=0xa450f94: Creating new topic tree
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - id=0xa450e40: Begin connecting process, switch state to CONNECTING.
[INFO] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - id=0xa450e40: using ping timeout of 3000000000 ns
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [dns] - id=0xa42b310: Host resolution requested for a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [dns] - id=0xa42b310: No cached entries found for a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com starting new resolver thread.
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: resolving host a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: resolved record: 3.131.31.52
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: resolved record: 52.15.119.124
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: resolved record: 13.59.30.89
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: resolved record: 2600:1f00:6000::383:1f34
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: resolved record: 2600:1f00:6000::340f:777c
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: resolved record: 2600:1f00:6000::d3b:1e59
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: new address resolved 3.131.31.52 for host a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com caching
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: new address resolved 52.15.119.124 for host a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com caching
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: new address resolved 13.59.30.89 for host a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com caching
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: new address resolved 2600:1f00:6000::383:1f34 for host a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com caching
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: new address resolved 2600:1f00:6000::340f:777c for host a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com caching
[DEBUG] [2021-02-18T19:57:17Z] [b5754b40] [dns] - static: new address resolved 2600:1f00:6000::d3b:1e59 for host a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com caching
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb4e03050: Scheduling attempt_connection task for immediate execution
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb4e03b50: Scheduling attempt_connection task for immediate execution
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb4e03050: Running attempt_connection task with <Running> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: initializing with domain 1 and type 0
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: setting socket options to: keep-alive 0, keep idle 0, keep-alive interval 0, keep-alive probe count 0.
[WARN] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: setsockopt() for NO_SIGNAL failed with errno 92. If you are having SIGPIPE signals thrown, you may want to install a signal trap in your application layer.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: beginning connect.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: connecting to endpoint 2600:1f00:6000::383:1f34:443.
[ERROR] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: connect failed with error code 101.
[INFO] [2021-02-18T19:57:17Z] [b684fb40] [dns] - id=0xa42b310: recording failure for record 2600:1f00:6000::383:1f34 for a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com, moving to bad list
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [dns] - static: purging address 2600:1f00:6000::383:1f34 for host a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com from the cache due to cache eviction or shutdown
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: is still open, closing...
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: closing
[ERROR] [2021-02-18T19:57:17Z] [b684fb40] [channel-bootstrap] - id=0xa44d200: failed to create socket with error 1049
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb4e03b50: Running attempt_connection task with <Running> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: initializing with domain 0 and type 0
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: setting socket options to: keep-alive 0, keep idle 0, keep-alive interval 0, keep-alive probe count 0.
[WARN] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: setsockopt() for NO_SIGNAL failed with errno 92. If you are having SIGPIPE signals thrown, you may want to install a signal trap in your application layer.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: beginning connect.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: connecting to endpoint 3.131.31.52:443.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01aa0: Scheduling (null) task for future execution at time 8129633861413
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01ae0: Scheduling epoll_event_loop_unsubscribe_cleanup task for immediate execution
[INFO] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: connection success
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: local endpoint 10.0.2.15:39292
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: assigning to event loop 0xa4371f0
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel-bootstrap] - id=0xa44d200: client connection on socket 0xb5d00b70 completed with error 0.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: Beginning creation and setup of new channel.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01e30: Scheduling on_channel_setup_complete task for immediate execution
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01ae0: Running epoll_event_loop_unsubscribe_cleanup task with <Running> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01e30: Running on_channel_setup_complete task with <Running> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: setup complete, notifying caller.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: no message pool is currently stored in the event-loop local storage, adding 0xb5d01f80 with max message size 16384, message count 4, with 4 small blocks of 128 bytes.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel-bootstrap] - id=0xa44d200: channel 0xb5d01c70 setup succeeded: bootstrapping.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket-handler] - id=0xb5d12620: Socket handler created with max_read_size of 16384
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d12718: Scheduling tls_timeout task for future execution at time 8134691976802
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [tls-handler] - id=0xb5d12700: Alpn protocol negotiated as x-amzn-mqtt-ca
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [tls-handler] - id=0xb5d12700: Remote server name is a1ypu7uyt3br9h-ats.iot.us-east-2.amazonaws.com
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel-bootstrap] - id=0xa44d200: tls negotiation result 0 on channel 0xb5d01c70
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [mqtt-client] - id=0xa450e40: Connection successfully opened, sending CONNECT packet
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d2c800: Scheduling mqtt_connack_timeout task for future execution at time 8127847022119
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [mqtt-client] - id=0xa450e40: Adding username ?SDK=PythonV2&Version=0.9.15 to connection
Traceback (most recent call last):
  File "shadow.py", line 275, in <module>
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [tls-handler] - id=0xb5d12700: Alert code 0
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01d88: Scheduling channel_shutdown task for immediate execution
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01d88: Running channel_shutdown task with <Running> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: beginning shutdown process
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: handler 0xb5d12620 shutdown in read dir completed.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [tls-handler] - id=0xb5d12700: Shutting down read direction with error code 0
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: handler 0xb5d12700 shutdown in read dir completed.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: handler 0xa450e54 shutdown in read dir completed.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01c84: Scheduling (null) task for immediate execution
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01c84: Running (null) task with <Running> status
[INFO] [2021-02-18T19:57:17Z] [b684fb40] [mqtt-client] - id=0xa450e40: sending disconnect message as part of graceful shutdown.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [mqtt-client] - id=0xa450e40: failed to send courteous disconnect io message
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: handler 0xa450e54 shutdown in write dir completed.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [tls-handler] - id=0xb5d12700: Shutting down write direction
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: handler 0xb5d12700 shutdown in write dir completed.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [socket] - id=0xb5d00b70 fd=7: closing
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01c40: Scheduling epoll_event_loop_unsubscribe_cleanup task for immediate execution
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d12674: Scheduling socket_handler_close task for immediate execution
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01c40: Running epoll_event_loop_unsubscribe_cleanup task with <Running> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d12674: Running socket_handler_close task with <Running> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: handler 0xb5d12620 shutdown in write dir completed.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01c84: Scheduling (null) task for immediate execution
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d01c84: Running (null) task with <Running> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: during shutdown, canceling task 0xb5d12718
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d12718: Running tls_timeout task with <Canceled> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: during shutdown, canceling task 0xb5d2c800
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [task-scheduler] - id=0xb5d2c800: Running mqtt_connack_timeout task with <Canceled> status
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel-bootstrap] - id=0xa44d200: channel 0xb5d01c70 shutdown with error 0.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel] - id=0xb5d01c70: destroying channel.
[DEBUG] [2021-02-18T19:57:17Z] [b684fb40] [channel-bootstrap] - id=0xa44d200: releasing bootstrap reference
    connected_future.result()
  File "/usr/lib/python3.7/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/usr/lib/python3.7/concurrent/futures/_base.py", line 384, in __get_result
    raise self._exception
awscrt.exceptions.AwsCrtError: AwsCrtError(name='AWS_ERROR_MQTT_UNEXPECTED_HANGUP', message='The connection was closed unexpectedly.', code=5134)
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - id=0xa450e40: user called disconnect.
[ERROR] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - id=0xa450e40: Connection is not open, and may not be closed
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - id=0xa450e40: Last refcount on connection has been released, start destroying the connection.
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - id=0xa450e40: Destroying connection
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-topic-tree] - tree=0xa450f94: Cleaning up topic tree
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [mqtt-client] - client=0xa4ee030: Cleaning up MQTT client
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [channel-bootstrap] - id=0xa44d200: releasing bootstrap reference
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [channel-bootstrap] - id=0xa44d200: releasing bootstrap reference
[DEBUG] [2021-02-18T19:57:17Z] [b7b6bec0] [channel-bootstrap] - id=0xa44d200: destroying

hackaprende pada 18 Feb 2021

Saya merasa sangat bodoh sekarang, kesalahan bagi saya adalah saya belum mengaktifkan sertifikat di konsol IoT. Ini adalah sesuatu yang bodoh tetapi bisa membantu orang lain

hackaprende pada 18 Feb 2021

🚀1 ❤1 👍1

@hackaprende terima kasih telah berbagi solusi di mana Anda terjebak.

jmklix pada 18 Feb 2021

Posting di sini jika ini membantu setiap pencari di masa depan, saya juga mendapatkan kesalahan awscrt.exceptions.AwsCrtError: AWS_ERROR_MQTT_UNEXPECTED_HANGUP: The connection was closed unexpectedly. dan bagi saya, ternyata saya belum _mengaktifkan_ sertifikat hal AWS IoT. Setelah membuatnya, ada langkah lain untuk mengaktifkannya.