• State Not Answered
  • Replies 10 replies
  • Subscribers 26 subscribers
  • Views 192 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 290563
Options

Failure in creating device certificate & provisioning it

user116928

I am creating device certificate as per steps mentioned at 

https://nordicsemiconductor.github.io/asset-tracker-cloud-docs/saga/docs/azure/GettingStarted/DeviceCredentials.html

Create root & intermediate certificates works fine, 

But when we issue 

node cli create-and-provision-device-cert

to create device certificate & provision it, it results in failure as follows:

node cli create-and-provision-device-cert --dk --debug --delete-private-key
Flasing certificate /dev/ttyACM0
Connecting to /dev/ttyACM0
Inactivity timeout 10 seconds
ERROR create-and-provision-device-cert failed!
ERROR Readline is not a constructor

Using Ubunto 20.x lts, using asset tracker 1.9x , firmware is created fine, it also works if I generate certificate using microsoft method for testing. 

@oys Let me know if you need more information

Parents
  • 0

    Hi Pramond,

    Ok, looks correct. Could you run the following commands and share the logs printout?

    # reinstall dependencies
npm ci

# Compile code
npx tsc

# Run the command again
node cli create-and-provision-device-cert --dk --debug --delete-private-key

    Best regards,

    Charlie

  • 0 in reply to user93921

    npm ci
    npm WARN deprecated [email protected]: flatten is deprecated in favor of utility frameworks such as lodash.
    npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
    npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
    npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
    npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
    npm WARN deprecated @azure/[email protected]: Please note, versions of this package with version numbers 3.0.0 and below have been deprecated as of 31-March-2022. We strongly encourage you to upgrade to version 4.0.0 or above to continue receiving updates. Refer to our deprecation policy: azure.github.io/.../policies_support.html for more details.
    npm WARN deprecated @azure/[email protected]: Please note, versions of this package with version numbers 9.0.0 and below have been deprecated as of 31-March-2022. We strongly encourage you to upgrade to version 10.0.0 or above to continue receiving updates. Refer to our deprecation policy: azure.github.io/.../policies_support.html for more details.

    > @nordicsemiconductor/[email protected] postinstall
    > husky install && check-node-version --package

    husky - Git hooks installed

    added 1289 packages, and audited 1290 packages in 9s

    120 packages are looking for funding
    run `npm fund` for details

    found 0 vulnerabilities
    npm notice
    npm notice New minor version of npm available! 8.11.0 -> 8.12.1
    npm notice Changelog: github.com/.../v8.12.1
    npm notice Run npm install -g [email protected] to update!
    npm notice

    Is this fine OR do we need to fix anything in this before generating certificate ?

Reply
  • 0 in reply to user93921

    npm ci
    npm WARN deprecated [email protected]: flatten is deprecated in favor of utility frameworks such as lodash.
    npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
    npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
    npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
    npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
    npm WARN deprecated @azure/[email protected]: Please note, versions of this package with version numbers 3.0.0 and below have been deprecated as of 31-March-2022. We strongly encourage you to upgrade to version 4.0.0 or above to continue receiving updates. Refer to our deprecation policy: azure.github.io/.../policies_support.html for more details.
    npm WARN deprecated @azure/[email protected]: Please note, versions of this package with version numbers 9.0.0 and below have been deprecated as of 31-March-2022. We strongly encourage you to upgrade to version 10.0.0 or above to continue receiving updates. Refer to our deprecation policy: azure.github.io/.../policies_support.html for more details.

    > @nordicsemiconductor/[email protected] postinstall
    > husky install && check-node-version --package

    husky - Git hooks installed

    added 1289 packages, and audited 1290 packages in 9s

    120 packages are looking for funding
    run `npm fund` for details

    found 0 vulnerabilities
    npm notice
    npm notice New minor version of npm available! 8.11.0 -> 8.12.1
    npm notice Changelog: github.com/.../v8.12.1
    npm notice Run npm install -g [email protected] to update!
    npm notice

    Is this fine OR do we need to fix anything in this before generating certificate ?

Children
Related
Terms of service