Critical Error

[cyanoalgae]

Hi, We are running the Chi.Bios virtually on the cloud9 server using ethernet connection into the wall. It is working well however, we are running into an issue where the reactors spontaneously stop and the experiment ends, however the controller is still connected can be restarted again. Obviosly this is not ideal as experiments shutting down means we have to rerun. The error is

[2025-11-25 00:26:19 +0000] [1923] [CRITICAL] WORKER TIMEOUT (pid:1927)
[2025-11-25 00:26:19 +0000] [1927] [INFO] Worker exiting (pid: 1927)
[2025-11-25 00:26:20 +0000] [3064] [INFO] Booting worker with pid: 3064

All files are the same however the cb.sh has been modified slightly to allow for the controller to be run on the cloud9

gunicorn -b 10.xx.xx.xx:5000 app:application

I don’t think running the Chi.Bio via the cloud would cause the critical error issue but wanted to know whether you have a fix particularly to the app.py file ?

Thanks

[harrison]

Ah that is a very good question. Is this also happening if connecting via USB?
If I were to guess it might be that when it is outputing the files that normally go to the GUI, it is creating something like a memory leak e.g. the data is stacking up and not being cleared and so eventually there is so much to transmit it doesn’t achieve this within whatever the default timeout is and so crashes. How to fix, not sure. Maybe see if you can monitor memory usage on the beaglebone or that received in your browser on your interface end (can be done in most browsers) and check to see if memory usage is linearly increasing over time?

[cyanoalgae]

Hi Harrison
the problem only occurs when running the reactor remotely via cloud 9 and does not occur when running the controller connected directly to a USB via Putty. We have purchased another laptop so the problem isn’t an issue anymore but it would be cool if we could get the remote cloud 9 working as then I could monitor/control the reactors remotely!

[harrison]

Cool, I am not sure actually how best to have that work. You can remotely run it through an ethernet port into the device which works fine for us. SImilarly, we often remote in to the computer acting as USB host which also is stable. Not sure about the more general Cloud9 route – haven’t really tried it!

[Author]

Posts