[Bug]: failire to install

[LindsyTheNeko]

Issue Category

Installation/Setup

Bug Description

im getting 2 different types of failiures to install main one is the mysql is failing claiming is unhealthy and took almost 2 minutes to time out. device is on Unbuntu 25.10, next issue im getting which seems to be more persistant now is files are read only with no way to change them regardless of what i do in the file structure. ive seeked help on the discord and posted my issue there as well and now im posting it here.

Steps to Reproduce

1. use the curl command from the project nomad site to install
2. wait for install.
3. (in my case for whatever reason 2 results typically) nomad mysql fails or file structure read only

Expected Behavior

expected to install with no problems

Actual Behavior

mysql failed and file structure read only after uninstalling nomad and trying to reinstall.

N.O.M.A.D. Version

latest

Operating System

Ubuntu 24.04

Docker Version

No response

Do you have a dedicated GPU?

No

GPU Model (if applicable)

intergrated intel

System Specifications

CPU: Intel core i5 4300m
GPU: Intergrated
RAM: 16gb
storage: 500gb

Service Status (if relevant)

No response

Relevant Logs

Browser Console Errors (if UI issue)

Screenshots

No response

Additional Context

No response

Pre-submission Checklist

• I have searched for existing issues that might be related to this bug
• I am running the latest version of Project N.O.M.A.D. (or have noted my version above)
• I have redacted any personal or sensitive information from logs and screenshots
• This issue is NOT related to running N.O.M.A.D. on an unsupported/non-Debian-based OS

[Tux2]

I too have this bug. Here's what I've debugged:

On slower computers the first boot of mySQL takes longer than the 3 tries timeout that is scripted into the management_compose.yaml. If you change the number of retries on line 85 to 10, it installs successfully in my tests on slower hardware.

My current workaround:

1. Separate the starting command into two and executing this first: sudo apt-get update && sudo apt-get install -y curl && curl -fsSL https://raw.githubusercontent.com/Crosstalk-Solutions/project-nomad/refs/heads/main/install/install_nomad.sh -o install_nomad.sh
2. Edit the install_nomad.sh in your favorite editor (I use nano): nano install_nomad.sh
3. Change line 33 to read as follows to point to my edited management_compose.yaml file: MANAGEMENT_COMPOSE_FILE_URL="https://gist.githubusercontent.com/Tux2/f0ca43967d32ea5c8a85882934f010c2/raw/4d2b77a83fdc06a2e64193abc48a08dd87f73d63/management_compose.yaml"
4. Save install_nomad.sh and exit the editor.
5. Run the command sudo bash install_nomad.sh

[Tux2]

As far as the read-only file system, that sounds like a separate issue that could be related to hardware, not software as that's something I didn't experience while dealing with the mySQL container issue. If you can, I'd re-install the OS from scratch to make sure you're not dealing with any file system issues, and if it keeps re-occurring you may have a bad drive.

[chriscrosstalk]

Thanks for reporting, and thanks Tux2 for the debugging. The MySQL timeout on slower machines is a known issue -- 3 retries isn't enough when first-time initialization takes longer. PR #480 bumps this to 10 retries which should help.

For the read-only filesystem issue -- as Tux2 mentioned, that sounds hardware-related (bad drive or filesystem corruption). A fresh OS reinstall would rule that out.

If you're still stuck on the MySQL side after a fresh attempt, PR #446 also fixes a related issue where reinstalling NOMAD can cause a credential mismatch if the MySQL data directory wasn't fully cleaned up.