Hey everyone,
after updating to the latest release i can’t start jobs via UI or SSH anymore. Any ideas? I power-cycled. The jobs are not even failing, they are not starting at all.
Leo
Hi @LeoKleym,
(Sorry I missed this post)
Hm, so when you run pio run stirring on the command line, nothing happens?
Can you tell me what
which pio
returns?
Edit: also, how did you update? Via the release.zip or over the internet?
I’m having an issue with running jobs from the UI as well. Error code in pio logs is:
2025-07-24T12:24:22+0100 [pioreactorui-pioreactor01] ERROR Exception on /unit_api/jobs/run/job_name/dosing_automation [POST]
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 1511, in wsgi_app
response = self.full_dispatch_request()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 919, in full_dispatch_request
rv = self.handle_user_exception(e)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 917, in full_dispatch_request
rv = self.dispatch_request()
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 902, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args) # type: ignore[no-any-return]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/var/www/pioreactorui/pioreactorui/unit_api.py", line 283, in run_job
body = current_app.get_json(request.data, type=structs.ArgsOptionsEnvsConfigOverrides)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/var/www/pioreactorui/pioreactorui/__init__.py", line 268, in loads
return loads(obj, type=type)
^^^^^^^^^^^^^^^^^^^^^
msgspec.ValidationError: Expected `str`, got `null` - at `$.env[...]`
2025-07-24T12:24:22+0100 [huey.consumer] ERROR Could not post to pioreactor01's address='100.77.93.20'/endpoint='/unit_api/jobs/run/job_name/dosing_automation', sent json={'args': [], 'options': {'automation_name': 'chemostat', 'skip_first_run': 0, 'max_working_volume_ml': 10, 'initial_volume_ml': 10, 'duration': 20, 'exchange_volume_ml': 0.5}, 'config_overrides': [], 'env': {'EXPERIMENT': '2025-07-23Test', 'JOB_SOURCE': 'user', 'MODEL_NAME': None, 'MODEL_VERSION': None, 'ACTIVE': '1'}} and returned HTTP response returned error code 500. Check connection? Check port?
I updated from 25.5.22 to 25.7.2 yesterday incrementally by uploading .zip files.
pioreactor@pioreactor01:~ $ which pio
/usr/local/bin/pio
Works fine via CLI:
pioreactor@pioreactor01:~ $ pio run dosing_automation --automation-name chemostat --exchange_volume_ml 10
2025-07-24T12:28:19+0100 DEBUG [dosing_automation] Init.
2025-07-24T12:28:19+0100 INFO [dosing_automation] Starting chemostat.
2025-07-24T12:28:19+0100 WARNING [dosing_automation] It's recommended to have stirring on to improve mixing during dosing events.
2025-07-24T12:28:19+0100 INFO [dosing_automation] Ready.
2025-07-24T12:28:19+0100 DEBUG [dosing_automation] dosing_automation is blocking until disconnected.
Can you post the output of pio version -v on both the leader and the worker (pioreactor01)?
Pioreactor app: 25.7.2
Pioreactor HAT: 1.2
Pioreactor firmware: 0.5
Model name:
HAT serial number: 2a6c6146-289c-4260-8dfd-f6579d0f112b
Operating system: Linux-6.12.25-v8+-aarch64-with-glibc2.36
Raspberry Pi: Raspberry Pi 4 Model B Rev 1.1
Image version: 1f4d3b37a567ee988d191d4ce8fcfaf3cc06c7d5
Pioreactor UI: 25.6.22
I think in your case, it’s the 'MODEL_NAME': None, 'MODEL_VERSION': None.
Can you try giving your Pioreactor some model on the Inventory page?
I need to handle the edge case where you aren’t using a traditional Pioreactor model, like yourself.
1 Like
Oh yes that fixed it thanks!