machinaris: Internal Server Error
Internal Server Error The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Fresh installation of Debian 10, Docker 19 and Machinaris (Plotter-only), following the Docker Wiki at https://github.com/guydavis/machinaris/wiki/Docker
Can someone confirm if this is an issue with Machinaris or not? I successfully installed on an exact same VM yesterday.
Update 1: Just tried on a fresh install of Ubuntu 20.04, same issue.
Update 2: Seems to be a Plotter-only issue as running Full-Node works as expected.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (10 by maintainers)
Closing as v0.4.0 has been released. Thanks for the contribution!
While it may still be possible to see the generic Gunicorn web server error page shown above for other reasons such as overloaded server or other error, the specific error being discussed above is no longer possible in v0.4.0 as a plotter is managed via the controller’s WebUI now. It’s no longer possible to WebUI pages on a worker, just a redirect to the controller’s WebUI.
Good day! Machinaris test version
ghcr.io/guydavis/machinaris:test
has re-worked this area of the code as part of adding support for a single WebUI to manage multiple workers on your LAN.If you have the time/inclination, please test out this upcoming release and let me know if it corrects them problem outlined in this issue.
Hi, this exact issue just happened on one my plotters (Windows) tonight. I accidentally pulled the log out from under a running plot job (from in the
.machinaris/plotman/logs/
folder). When I did so, the main page broke due to bad parsing on my part. Theplotman status
CLI command was actually printing error info in its first lines as shown:The second output is after I put the missing log file back, my
plotman status
command no longer had the error and my Machinaris /index page came back. Please check yourplotman status
output from in-container console.Overall the fix for this bug is for me to tighten up the parsing of
plotman status
so web server doesn’t face plant if the output contains a couple of error lines. Thanks for the report!http://IP_ADDR:8926/plotting
shows the Plotman interface as expected, and so doeshttp://IP_ADDR:8926/settings/plotting
.Seems to be a problem related to the summary page.
Logs
Tried to start plotting and it works as expected 😃