[GH-ISSUE #7265] Manage my damn life (MMDL) script is failing #1544

Closed
opened 2026-02-26 12:49:23 +03:00 by kerem · 10 comments
Owner

Originally created by @EpixMan on GitHub (Aug 28, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/7265

Originally assigned to: @vhsdream on GitHub.

Have you read and understood the above guidelines?

Yes

📜 What is the name of the script you are using?

Manage My Damn Life

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/managemydamnlife.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

I am receiving an error when I try to install the script, I think it is just that make is not installed

🔄 Steps to reproduce the issue.

Just using the script:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/managemydamnlife.sh)"

Paste the full error output (if available).

From the MMDL installation script with verbose

npm error gyp ERR! stack Error: not found: make
npm error gyp ERR! stack     at getNotFoundError (/opt/mmdl/node_modules/which/which.js:10:17)
npm error gyp ERR! stack     at /opt/mmdl/node_modules/which/which.js:57:18
npm error gyp ERR! stack     at new Promise (<anonymous>)
npm error gyp ERR! stack     at step (/opt/mmdl/node_modules/which/which.js:54:21)
npm error gyp ERR! stack     at /opt/mmdl/node_modules/which/which.js:71:22
npm error gyp ERR! stack     at new Promise (<anonymous>)
npm error gyp ERR! stack     at subStep (/opt/mmdl/node_modules/which/which.js:69:33)
npm error gyp ERR! stack     at /opt/mmdl/node_modules/which/which.js:80:22
npm error gyp ERR! stack     at /opt/mmdl/node_modules/isexe/index.js:42:5
npm error gyp ERR! stack     at /opt/mmdl/node_modules/isexe/mode.js:8:5
npm error gyp ERR! stack     at FSReqCallback.oncomplete (node:fs:198:21)
npm error gyp ERR! System Linux 6.14.8-2-pve
npm error gyp ERR! command "/usr/bin/node" "/opt/mmdl/node_modules/.bin/node-gyp" "rebuild"
npm error gyp ERR! cwd /opt/mmdl/node_modules/sqlite3
npm error gyp ERR! node -v v20.19.4
npm error gyp ERR! node-gyp -v v8.4.1
npm error gyp ERR! not ok

It appear that the error caused by 'make' not being available

Full error log:
MMDL.txt
npm-output.txt

🖼️ Additional context (optional).

No response

Originally created by @EpixMan on GitHub (Aug 28, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/7265 Originally assigned to: @vhsdream on GitHub. ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Manage My Damn Life ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/managemydamnlife.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. I am receiving an error when I try to install the script, I think it is just that `make` is not installed ### 🔄 Steps to reproduce the issue. Just using the script: `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/managemydamnlife.sh)"` ### ❌ Paste the full error output (if available). From the MMDL installation script with verbose ``` npm error gyp ERR! stack Error: not found: make npm error gyp ERR! stack at getNotFoundError (/opt/mmdl/node_modules/which/which.js:10:17) npm error gyp ERR! stack at /opt/mmdl/node_modules/which/which.js:57:18 npm error gyp ERR! stack at new Promise (<anonymous>) npm error gyp ERR! stack at step (/opt/mmdl/node_modules/which/which.js:54:21) npm error gyp ERR! stack at /opt/mmdl/node_modules/which/which.js:71:22 npm error gyp ERR! stack at new Promise (<anonymous>) npm error gyp ERR! stack at subStep (/opt/mmdl/node_modules/which/which.js:69:33) npm error gyp ERR! stack at /opt/mmdl/node_modules/which/which.js:80:22 npm error gyp ERR! stack at /opt/mmdl/node_modules/isexe/index.js:42:5 npm error gyp ERR! stack at /opt/mmdl/node_modules/isexe/mode.js:8:5 npm error gyp ERR! stack at FSReqCallback.oncomplete (node:fs:198:21) npm error gyp ERR! System Linux 6.14.8-2-pve npm error gyp ERR! command "/usr/bin/node" "/opt/mmdl/node_modules/.bin/node-gyp" "rebuild" npm error gyp ERR! cwd /opt/mmdl/node_modules/sqlite3 npm error gyp ERR! node -v v20.19.4 npm error gyp ERR! node-gyp -v v8.4.1 npm error gyp ERR! not ok ``` It appear that the error caused by 'make' not being available Full error log: [MMDL.txt](https://github.com/user-attachments/files/22029976/MMDL.txt) [npm-output.txt](https://github.com/user-attachments/files/22029975/npm-output.txt) ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:49:23 +03:00
Author
Owner

@vhsdream commented on GitHub (Aug 28, 2025):

Hey @EpixMan I was not able to repro this. Tell me more about your setup. You are on PVE9, aren't you?

Image
<!-- gh-comment-id:3234415739 --> @vhsdream commented on GitHub (Aug 28, 2025): Hey @EpixMan I was not able to repro this. Tell me more about your setup. You are on PVE9, aren't you? <img width="326" height="188" alt="Image" src="https://github.com/user-attachments/assets/f21b9030-c071-498c-9ba5-b908cb440195" />
Author
Owner

@EpixMan commented on GitHub (Aug 28, 2025):

Thanks for your response @vhsdream !, yes, here is my pveversion:

pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.8-2-pve)

I have tried multiple dns resolver (including 8.8.8.8 and 1.1.1.1) but to no avail

<!-- gh-comment-id:3234540684 --> @EpixMan commented on GitHub (Aug 28, 2025): Thanks for your response @vhsdream !, yes, here is my `pveversion`: ``` pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.8-2-pve) ``` I have tried multiple dns resolver (including 8.8.8.8 and 1.1.1.1) but to no avail
Author
Owner

@MickLesk commented on GitHub (Aug 28, 2025):

Add make as dep?

<!-- gh-comment-id:3234560098 --> @MickLesk commented on GitHub (Aug 28, 2025): Add make as dep?
Author
Owner

@vhsdream commented on GitHub (Aug 28, 2025):

@MickLesk Even though our script makes use of mysql, I think it's failing because it's trying to build sqlite so maybe that needs to be installed instead. When I ran the script there was no output about building anything with node-gyp.

@EpixMan can you do a dpkg -l | grep sqlite please?

<!-- gh-comment-id:3234584621 --> @vhsdream commented on GitHub (Aug 28, 2025): @MickLesk Even though our script makes use of mysql, I think it's failing because it's trying to build sqlite so maybe that needs to be installed instead. When I ran the script there was no output about building anything with node-gyp. @EpixMan can you do a `dpkg -l | grep sqlite` please?
Author
Owner

@MickLesk commented on GitHub (Aug 28, 2025):

Strange, ivnt build the Script in Last weeks, i can try it tomorrow on my old and new nodes

<!-- gh-comment-id:3234625589 --> @MickLesk commented on GitHub (Aug 28, 2025): Strange, ivnt build the Script in Last weeks, i can try it tomorrow on my old and new nodes
Author
Owner

@EpixMan commented on GitHub (Aug 28, 2025):

Add make as dep?

I will try to do it manually and find what is exactly the problem, but I am very new to proxmox/debian so I can't promise anything

@EpixMan can you do a dpkg -l | grep sqlite please?

root@managemydamnlife:/# dpkg -l | grep sqlite
ii  libsqlite3-0:amd64             3.40.1-2+deb12u1               amd64        SQLite 3 shared library
<!-- gh-comment-id:3234638922 --> @EpixMan commented on GitHub (Aug 28, 2025): > Add make as dep? I will try to do it manually and find what is exactly the problem, but I am very new to proxmox/debian so I can't promise anything > [@EpixMan](https://github.com/EpixMan) can you do a `dpkg -l | grep sqlite` please? ``` root@managemydamnlife:/# dpkg -l | grep sqlite ii libsqlite3-0:amd64 3.40.1-2+deb12u1 amd64 SQLite 3 shared library ```
Author
Owner

@vhsdream commented on GitHub (Aug 28, 2025):

So for whatever reason, the build script does not see your system as supported, so instead of downloading a precompiled binary it tries to build from source.

I can repro this if I force npm to build from source:

Image

But why is it happening by default for you @EpixMan ? How many times have you tried to install?

<!-- gh-comment-id:3234679203 --> @vhsdream commented on GitHub (Aug 28, 2025): So for whatever reason, the build script does not see your system as supported, so instead of downloading a precompiled binary it tries to build from source. I can repro this if I force npm to build from source: <img width="889" height="639" alt="Image" src="https://github.com/user-attachments/assets/72b24af0-5421-41cc-9b75-832c77af7edc" /> But why is it happening by default for you @EpixMan ? How many times have you tried to install?
Author
Owner

@EpixMan commented on GitHub (Aug 28, 2025):

But why is it happening by default for you @EpixMan ? How many times have you tried to install?

I am a person who love to ensure that he tried everything before asking... around 8 times from github and once from gitea

<!-- gh-comment-id:3234822110 --> @EpixMan commented on GitHub (Aug 28, 2025): > But why is it happening by default for you [@EpixMan](https://github.com/EpixMan) ? How many times have you tried to install? I am a person who love to ensure that he tried everything before asking... around 8 times from github and once from gitea
Author
Owner

@MickLesk commented on GitHub (Aug 28, 2025):

Did you have reboot your Proxmox in Last Time?

Try this, or try an Microcode Update

<!-- gh-comment-id:3234881645 --> @MickLesk commented on GitHub (Aug 28, 2025): Did you have reboot your Proxmox in Last Time? Try this, or try an Microcode Update
Author
Owner

@vhsdream commented on GitHub (Aug 28, 2025):

I wonder if this is simply due to the disconnect between PVE9 being Debian 13 and the container being 12.

<!-- gh-comment-id:3234887242 --> @vhsdream commented on GitHub (Aug 28, 2025): I wonder if this is simply due to the disconnect between PVE9 being Debian 13 and the container being 12.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#1544
No description provided.