Pioreactor / Pioreactor/pioreactor
Update to Latest Release Over Internet Leads to 500 Errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 149
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
I updated my v1.0 Pioreactor over the internet to the latest version (Latest version available:24.12.10) and can now no longer see any experiments, and I get 500 Internal Server Error when trying to access the routes:
- http://pioreactor.local/unit_api/versions/app
- http://pioreactor.local/api/configs/config.ini
- http://pioreactor.local/api/experiments/assignment_count
(etc)
Otherwise the GUI is partially browseable. What can I do to recover my Pioreactor? I suspect I should try to install a version from a zip, but I do not know which.
I do not particularly care about keeping the experimental data.
The shared config.ini looks like this:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h1>500 Internal Server Error</h1>
</body>
</html>
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the update to version 24.12.10 and checking the listed /unit_api/versions/app, /api/configs/config.ini, and /api/experiments/assignment_count routes. Inspect the shared config.ini response and determine a supported recovery path, including whether installing from a zip is appropriate. Done means the affected routes no longer return 500 errors and the recovery steps are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, raspberry-pi
- Domain
- api, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100