Non blocking issue report

support

#1

Hi,

Here are the steps I did to get this situation :

  1. I’ve pushed some new Dockerfile with an java app not able to startup. So the logs were looping on “Unable to access jarfile” every 10 sec for ever.
  2. I’ve “shutdown” via the web UI button my only test device, because I had no time to fix the problem
  3. I fix the problem and push the new fixed Dockerfile.
  4. I start the device manually (unplug, re-plug alim).

And after this I had 15 min of this strange message looping (it finally stopped and the new app got deployed) :

18.05.17 19:33:07 (+0200)
18.05.17 19:33:07 (+0200) Frames:
18.05.17 19:33:07 (+0200) ---
18.05.17 19:33:07 (+0200) 0: setupRootfs
18.05.17 19:33:07 (+0200) Package: github.com/opencontainers/runc/libcontainer
18.05.17 19:33:07 (+0200) File: rootfs_linux.go@40
18.05.17 19:33:07 (+0200) ---
18.05.17 19:33:07 (+0200) 1: Init
18.05.17 19:33:07 (+0200) Package: github.com/opencontainers/runc/libcontainer.(*linuxStandardInit)
18.05.17 19:33:07 (+0200) File: standard_init_linux.go@57
18.05.17 19:33:07 (+0200) ---
18.05.17 19:33:07 (+0200) 2: StartInitialization
18.05.17 19:33:07 (+0200) Package: github.com/opencontainers/runc/libcontainer.(*LinuxFactory)
18.05.17 19:33:07 (+0200) File: factory_linux.go@240
18.05.17 19:33:07 (+0200) ---
18.05.17 19:33:07 (+0200) 3: initializer
18.05.17 19:33:07 (+0200) Package: github.com/docker/docker/daemon/execdriver/native
18.05.17 19:33:07 (+0200) File: init.go@35
18.05.17 19:33:07 (+0200) ---
18.05.17 19:33:07 (+0200) 4: Init
18.05.17 19:33:07 (+0200) Package: github.com/docker/docker/pkg/reexec
18.05.17 19:33:07 (+0200) File: reexec.go@26
18.05.17 19:33:07 (+0200) ---
18.05.17 19:33:07 (+0200) 5: main
18.05.17 19:33:07 (+0200) Package: main
18.05.17 19:33:07 (+0200) File: docker.go@18
18.05.17 19:33:07 (+0200) ---
18.05.17 19:33:07 (+0200) 6: main
18.05.17 19:33:07 (+0200) Package: runtime
18.05.17 19:33:07 (+0200) File: proc.go@183
18.05.17 19:33:07 (+0200) ---
18.05.17 19:33:07 (+0200) 7: goexit
18.05.17 19:33:07 (+0200) Package: runtime
18.05.17 19:33:07 (+0200) File: asm_arm.s@998
18.05.17 19:33:38 (+0200) Timestamp: 2017-05-18 17:33:38.237879002 +0000 UTC
18.05.17 19:33:38 (+0200) Code: System error
18.05.17 19:33:38 (+0200)
18.05.17 19:33:38 (+0200) Message: stat /tmp/resin-supervisor/377605: no such file or directory

So that’s it, I prefer to report it if there is something to fix, even if it finally recovered by itself in my case.

And I humbly suggest the “shutdown” button should be red because it’s an irreversible action if you are not in the same location as the device, not like other actions.


#2

Thanks a lot for the feedback Tristan. The shutdown button is indeed red - It also asks for the device name as a confirmation - Are you referring to some other button?


#3

Btw, it looks to be the same looping error stack as in Error restarting the app

And yes, I’m referring to the OTHER shutdown button, the one which is NOT red :wink:
(so not the one you can see clicking “Actions” in the left menu, but the one you can see by clicking “Actions” in the upper right corner, in the device summary screen).


#4

That makes sense. Let me log a ticket for the Action to be Red :slight_smile:


#5

yes, it is the same error. it seems to be something in the supervisor.

In my case, the device was online for two days and for other reasons my internal app watchdog restarted the app but it did not came up again.