search

UCBerkeleySETI / commensal-automator

Automation for Breakthrough Listen's commensal observing
MIT License
1 stars 1 forks source link

Stop for debugging does not seem to actually stop for debugging #2

Closed lacker closed 2 years ago

lacker commented 2 years ago 
[2022-10-18 06:33:15,327 - ERROR - proc_hpguppi.py:124] Timeout of 600 seconds exceeded
[2022-10-18 06:33:15,327 - ERROR - proc_hpguppi.py:74] Timed out, processing has not started.
[2022-10-18 06:33:15,327 - ERROR - automator.py:432] hpguppi_proc timed out. Stopping automator for debugging.
[2022-10-18 06:33:16,417 - INFO - automator.py:113] Starting Automator:
Redis endpoint: 127.0.0.1:6379
Processing script: /home/obs/bin/processing_example.sh

[2022-10-18 06:34:29,844 - INFO - automator.py:198] New state: configure
[2022-10-18 06:34:29,844 - INFO - automator.py:264] Ignoring irrelevant state for array_1
[2022-10-18 06:35:31,356 - INFO - automator.py:198] New state: conf_complete
[2022-10-18 06:35:31,357 - INFO - subarray.py:38] New subarray object for array_1
[2022-10-18 06:35:31,357 - INFO - automator.py:249] Initialised new subarray object: array_1 in state conf_complete

Maybe circus is restarting it? I also wonder whether we should be ignoring the conf_complete state, it doesn't appear like we currently do anything with that at all.

lacker commented 2 years ago

Changed to go into "pause" mode which just does nothing in response to new messages, so circus won't restart it. https://github.com/UCBerkeleySETI/commensal-automator/commit/524a9cd1f7e545c4f7aacc4a51bbe5b0f7a91b91