No Device Log Updates, No Updates After Push

raspberrypi3

#1

This is not a new project, I have been able to push to it in the past and have had no problems seeing logs before this. No error logs while issuing the command ‘git push resin master’ and I am able to see when the device is online or not successfully. I am also still able to SSH into and restart the device.

ResinOS Version: Resin OS 2.3.0+rev1 (prod)
Device: RaspberryPI 3


#4

Would you mind trying to use our resin-cli to see if there are really no logs for that app?
https://docs.resin.io/tools/cli/#logs-60-uuid-62-


#5

@telphan, I have installed resin-cli and ran logs with my device uuid as you suggested. Unfortunately, no logs were returned from the command and even adding the --tail option resin-cli returns

Missing uuid

If you need help, don't hesitate in contacting us at:

  GitHub: https://github.com/resin-io/resin-cli/issues/new
  Forums: https://forums.resin.io

Here is the full transcript with resin-cli:

infining@infining-galliumos:~$ resin devices
ID     UUID    NAME          DEVICE TYPE  APPLICATION NAME STATUS IS ONLINE SUPERVISOR VERSION OS VERSION          DASHBOARD URL
671907 5099b1b green-voice   raspberrypi3 re4son           Idle   false     6.1.2              Resin OS 2.2.0+rev1 https://dashboard.resin.io/apps/538142/devices/671907/summary
665807 e4aa03d quiet-water   raspberrypi3 gitlab           Idle   false     6.1.2              Resin OS 2.2.0+rev1 https://dashboard.resin.io/apps/580467/devices/665807/summary
823695 ee49121 snowy-firefly raspberrypi3 resinOMV         Idle   true      6.1.3              Resin OS 2.3.0+rev1 https://dashboard.resin.io/apps/738676/devices/823695/summary
infining@infining-galliumos:~$ resin logs ee40121
infining@infining-galliumos:~$ resin logs --tail ee40121
Missing uuid

If you need help, don't hesitate in contacting us at:

  GitHub: https://github.com/resin-io/resin-cli/issues/new
  Forums: https://forums.resin.io

#6

Maybe the supervisor is not running. The supervisor collects the logs and sends them to the cloud. Could you try to restart the device? Are you able to reboot the device? If so the supervisor is running and we need to look at other options.