Startup after interrupted run

[mpatterson]

Hi,

I was running Chi.Bio last night and the computer restarted overnight, interrupting the run. Chi.Bio wouldn’t automatically reconnect, so I ejected the USB and plugged it back in, and it looks something timed out and so it tried connecting again (not normal in my experience). This re-attempt was successful, but after initializing all reactors it printed this line ( [1283] [INFO] Handling signal: winch) that I have not seen before. The reactor is running right now without issues but I want to make sure that the control computer was not damaged when the computer was restarted.

login as: root
Pre-authentication banner message from server:
| Debian GNU/Linux 10
|
| BeagleBoard.org Debian Buster IoT Image 2020-08-25
|
| Support: https://bbb.io/debian
|
| default username:password is [debian:temppwd]
|
End of banner message from server
root@192.168.7.2’s password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Oct 4 07:24:46 2022 from 192.168.7.1
cdroot@beaglebone:~# cd chibio/
root@beaglebone:~/chibio# bash cb.sh
[2022-10-04 07:17:42 +0000] [1283] [INFO] Starting gunicorn 20.1.0
[2022-10-04 07:17:42 +0000] [1283] [INFO] Listening at: http://192.168.7.2:5000 (1283)
[2022-10-04 07:17:42 +0000] [1283] [INFO] Using worker: sync
[2022-10-04 07:17:42 +0000] [1498] [INFO] Booting worker with pid: 1498
2022-10-04 07:18:04.425772 Starting watchdog
2022-10-04 07:18:06.919782 Initialising devices
2022-10-04 07:18:07.171941 Initialised M0, Device ID: 38921214501243657614
2022-10-04 07:18:07.872931 Initialised M1, Device ID: 17422214321243657614
2022-10-04 07:18:08.582388 Initialised M2, Device ID: 40980108961243657614
2022-10-04 07:18:09.266278 Initialised M3, Device ID: 22538214021243657614
2022-10-04 07:18:09.957775 Initialised M4, Device ID: 35846214461243657614
2022-10-04 07:18:10.643468 Initialised M5, Device ID: 46094628061728357670
2022-10-04 07:18:11.327779 Initialised M6, Device ID: 50190214001243657614
2022-10-04 07:18:12.015011 Initialised M7, Device ID: 36881626021728357670
[2022-10-04 07:18:12 +0000] [1283] [CRITICAL] WORKER TIMEOUT (pid:1498)
[2022-10-04 07:18:12 +0000] [1498] [INFO] Worker exiting (pid: 1498)
[2022-10-04 07:18:12 +0000] [1887] [INFO] Booting worker with pid: 1887
2022-10-04 07:18:20.303471 Starting watchdog
2022-10-04 07:18:22.786461 Initialising devices
2022-10-04 07:18:23.018985 Initialised M0, Device ID: 38921214501243657614
2022-10-04 07:18:23.701293 Initialised M1, Device ID: 17422214321243657614
2022-10-04 07:18:24.384392 Initialised M2, Device ID: 40980108961243657614
2022-10-04 07:18:25.070686 Initialised M3, Device ID: 22538214021243657614
2022-10-04 07:18:25.754595 Initialised M4, Device ID: 35846214461243657614
2022-10-04 07:18:26.443202 Initialised M5, Device ID: 46094628061728357670
2022-10-04 07:18:27.123514 Initialised M6, Device ID: 50190214001243657614
2022-10-04 07:18:27.806769 Initialised M7, Device ID: 36881626021728357670
2022-10-04 07:18:28.408095 Start Up Complete
[2022-10-04 07:18:35 +0000] [1283] [INFO] Handling signal: winch

[harrison]

The “winch” signal is something to do with the GUI/server presenting data; generally not an important one. If it is giving issues after restart I’d recommend power cycling everything.
In general strongly recommend disabling Windows update or any similar auto-restart functionality on the host computer…

[mpatterson]

Okay, thanks. Yes I usually disable Windows updates, but I thought I had an extra week left before I had to pause them again- it was an oversight on my part.

[Author]

Posts