Conduit Gateway hung on Check-in

Home Forums Device HQ Conduit Gateway hung on Check-in

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #23971
    William Laing
    Participant

    Good Day –

    We’re running acceptance testing with a client and was hoping to install a new app on the gateway using DeviceHQ.

    However, we just noticed the check-in started over three hours ago. In the duration column on DeviceHQ->Devices->ourDevice->Check-Ins, for duration, it says “Connected”.

    The DeviceHQ info area on the left side show “Connected” for Last check-in and for Next check-in.

    We’d prefer not to recycle power on the gateway during these tests. Any ideas will be appreciated! Thank you.

    #23972
    Jeff Hatch
    Keymaster

    William,

    Do you have access to the device? It would be good to determine what is causing this “hang”. If you can, it would be good to do a top, free, and ps auxww on the device and get the output of those three commands. We could at least tell how much memory there is, what is eating the CPU (if anything), and what the status of the annexcd process is.

    Jeff

    #23974
    William Laing
    Participant

    Hi Jeff –

    Thanks for the response.

    No, we don’t have access to the device.

    If the connection to DeviceHQ is hung, we’re guessing the device->schedule->reboot option on DeviceHQ probably won’t work?

    We have a Node-RED application running to push LoRa data to the cloud.

    William

    #23975
    William Laing
    Participant

    Thanks again, Jeff, it cleared after almost four hours connected.

    Next time we’re connected, we’ll take a look at top, free and ps.

    Best Regards,
    William

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.