Mariner3D fails to start, with exit-code "ModuleNotFoundError: No Module named 'mariner'"

[Jax-The-Fox]

Description
After following the installation guide, I get to the point where I need to restart the Pi and then run 'sudo systemctl status mariner3d', which shows the status as 'loaded' and 'enabled' but fails to activate with the errors found below in the journalctl:

Reproduction Steps
Steps to reproduce the behavior:

1. Install using the guide from the provided documentation (manually or with the helper script)
2. run 'sudo systemctl status mariner3d'
3. See error

Expected Behavior
The Mariner3D service to start

Screenshots / Logs
Apr 19 21:40:15 elegoo-boron systemd[1]: Started mariner3d.service - mariner3d Printer Controller.
Apr 19 21:40:15 elegoo-boron mariner[1733]: Traceback (most recent call last):
Apr 19 21:40:15 elegoo-boron mariner[1733]: File "/usr/bin/mariner", line 5, in
Apr 19 21:40:15 elegoo-boron mariner[1733]: from mariner.server import main
Apr 19 21:40:15 elegoo-boron mariner[1733]: ModuleNotFoundError: No module named 'mariner'
Apr 19 21:40:16 elegoo-boron systemd[1]: mariner3d.service: Main process exited, code=exited, status=1/FAILURE
Apr 19 21:40:16 elegoo-boron systemd[1]: mariner3d.service: Failed with result 'exit-code'.

Details:

• Mariner 2 Version: 0.5.0-1
• Printer Model: Elegoo Saturn S
• Raspberry Pi Model: RPi 3B v1.2 (I know it doesn't support OTG or USB Gadget Mode. I am just trying to get the webUI up so I can see the features it has. I have a Zero 2 W ordered that will arrive April 21st. If it turns out Mariner just doesn't work on the 3B, I can wait until then.)

[Jax-The-Fox]

Confirmed the same error is present on my RPi 4B that I borrowed from another printer to test.

I also tried the install script found at https://github.com/dprossner/Mariner-Autoinstaller/tree/amd989 with a variety of other errors.

As it is, I am going to wait for my Zero to arrive, so that when I get it working it'll be on the final hardware.

In the mean time, would you be able to tell me a) what I'm doing wrong and b) what hardware and RPi OS version (if you are even using a Pi at all) it's working for you on?

I have been trying the latest, but that clearly isn't working.

[Jax-The-Fox]

Confirmed the same error with my new Pi Zero 2 W, both with the newest release of Trixie, and also an install of 64 bit Bullseye Lite.

What version of everything should I be running, and is something going wrong with the venv setup?

[amd989]

Hi there! Thank you for trying to get this project to work! Let me see if we can solve this problem.

So far, I've confirmed this working in both armbian and raspberrypiOS under Bookworm. But let me go through the process with Trixie and will report back if I find any issues.

[amd989]

I went through the process, got same result. Let me look into it.

[Jax-The-Fox]

That was the entire error that was printing out to journalctl. If I restarted the service, it just repeated those same lines with a different timestamp.

I was able to get it working late last night, but had to make major changes to several of the files to get things working.

I ended up getting it working on the Bullseye install after installing Python 3.11.8 specifically and then cloning the entire repo with git instead of using the install instructions in the docs.

That got the backend working and fixed the 'module not found' error, but the Flask frontend still wasn't working until I built that manually and changed some paths in the files.

I think I was running into some serious issues with parts of the project installing globally and others into a venv.

I will save that Bullseye SD card image now as a fallback and try Trixie again tonight with the changes you made and see what happens. I guess I could also try with Bookworm.

[amd989]

Give me a minute, I think I managed to get to the root cause. Just trying to get a build to work and should be able to retry to validate the problem is gone.

You are right on the reasoning, I was basically only building for bookworm, and that only cares about python 3.11. Trixie uses 3.13. And all that venv stuff would not work right in there.

[amd989]

Ok run the installer script again, overwrite when asked.

curl -fsSL https://amd989.github.io/mariner/setup.sh | sudo bash

then

sudo apt install mariner3d

Should install the Trixie version now and work out of the box without any problems.

Thanks for taking the time trying the app, and reporting the issue!