Mariner module not found

[jman1o1]

Description
Installed deb file from the release page over top of a working Mariner install. Checking the the status of via "sudo systemctl status mariner3d" produces the following error:

Apr 23 23:05:46 mariner systemd[1]: Started mariner3d Printer Controller.
Apr 23 23:05:46 mariner mariner[787]: Traceback (most recent call last):
Apr 23 23:05:46 mariner mariner[787]: File "/usr/bin/mariner", line 5, in
Apr 23 23:05:46 mariner mariner[787]: from mariner.server import main
Apr 23 23:05:46 mariner mariner[787]: ModuleNotFoundError: No module named 'mariner'
Apr 23 23:05:47 mariner systemd[1]: mariner3d.service: Main process exited, code=exited, status=1/FAILURE
Apr 23 23:05:47 mariner systemd[1]: mariner3d.service: Failed with result 'exit-code'.

Details:

• Mariner Version: 0.2.0-1
• Printer Model: Elegoo Mars 2 Pro on 4.4.3
• Raspberry Pi Model: RPi Zero W

[sammers230]

I'm also having the same issue.
I've even removed mariner completely from my pi and having the same problem. Currently running on a raspberry pi 3b or not as having the same issue as above.

[Life-Imaging-Services]

same problem here (RPi Zero 2). I guess were missing something...

[bludin]

ok, here's as far as I got: I've started with a fresh install of RaspberryPi OS Lite 32bit on a RPi Zero 2.
If downloaded the package with wget https://github.com/BlueFinBima/mariner/releases/download/v0.2.0-1/mariner3d_0.2.0-1_armhf.deb and installed it using sudo dpkg -i mariner3d_0.2.0-1_armhf.deb . The installer reported a missing dependency libxslt1.1 which I installed with sudo apt install libxslt1.1. After that, the mariner installer resumed and completed automatically. I completed the set up according to https://mariner.readthedocs.io/en/latest/software-setup.html . sudo systemctl status mariner3d reports that the service is up and running and serving. When I copy a file to /mnt/usb_share/ via SSH, the printer sees it. But connecting to http://<rpi_ip>:5000 yields a blank page but no error...

[LeJoker]

I didn't have the Module not Found error, but I am seeing the service running with the blank page that @bludin saw. Running it on a Pi 4B.

Anyone able to resolve this one yet?

[Daendaralus]

I happened to go through the exact same steps as bludin. I also seem to have the same blank page problem. Seems like the server runs fine, serving files and I can access the API too (api/list_files, api/print_status <- actually shows the printers status, layer, print time etc of an ongoing print).

Edit: After building the frontend with yarn from source of the last release (But NOT the current repository state) and moving the created main.js to /opt/venvs/mariner3d/dist/ and then restarting the service the frontend seems to work again. The webpage is no longer blank. No idea what is wrong, I see 2 errors in the dev console when the webpage loads on the blank page. I assume there's some incompatibility introduced with version upgrades on some of the dependencies in the frontend. I guess one may need to enabled source-maps to debug it and see what the source of the error is.

[BlueFinBima]

Thanks for the issue and the comments. I have not touched this code for a while and I have not used my SLA printer for an equally long time so I'm probably not qualified to comment on your experiences so for this I apologise.

[bludin]

Thanks for the issue and the comments. I have not touched this code for a while and I have not used my SLA printer for an equally long time so I'm probably not qualified to comment on your experiences so for this I apologise.

There's really no need to apologize. Thanks for the work you've done. I hope somebody competent can pick up on it in the future and make it accessible to a broader audience since it would be really useful if we could get it to work.
Best wishes to you, where you are and whatever you are up to these days.

[nini57]

Hello,
i've the same problem

[badsmoke]

@BlueFinBima can you please share the functional main.js

EDIT:

ok i have copy the main.js from the original mariner

i have created a gist

https://gist.github.com/badsmoke/e656e589dc49183b2d0eb2e586b4fc9c

[BlueFinBima]

@badsmoke glad you found it. main.js is a generated file for the frontend, and since my fork no longer builds successfully. I do not have access to that file. As @Daendaralus says, the problem is likely to be dependency related,