In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:654) DeprecationWarning: Unhandled promise rejections are deprecated. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with. (node:654) UnhandledPromiseRejectionWarning: Unhandled promise rejection. (node:654) UnhandledPromiseRejectionWarning: Error: 3 INVALID_ARGUMENT: The device credential in position 0 contains an invalid key format.Īt Object.callErrorFromStatus Object.onReceiveStatus Object.onReceiveStatus Object.onReceiveStatus process.nextTick processTicksAndRejections (internal/process/task_queues.js:79:9) Writing new private key to 'rsa-priv.pem' Device with name balena-0p6hjw2f1cizer8yacntj809xtsdew74 not registered. ![]() Device ID: balena-0p6hjw2f1cizer8yacntj809xtsdew74 Now what I’m facing is the following (pasting the log output): Connecting to Google IoT Core. I have managed to solve the previous issue with the /bin/busybox no such file or directory, I have decided to use the already build docker image and pull that in my docker template file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |