starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Cronicle update command fails updating npm #1776

New Issue
Closed
opened 2026-02-05 02:14:27 +03:00 by OVERLORD · 10 comments
OVERLORD commented 2026-02-05 02:14:27 +03:00
Owner
Copy Link

Originally created by @de666 on GitHub (Oct 11, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Cronicle Primary

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-3-pve)

📝 Provide a clear and concise description of the issue.

I receive error messages about npm when I update cronicle with the update command within the container console

🔄 Steps to reproduce the issue.

  • Run update command inside the LXC container

❌ Paste the full error output (if available).

Reading package lists... Doneeplacing with 22
Building dependency tree... Done
Reading state information... Done
Package 'nodejs' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@11.6.2
npm ERR! notsup Not compatible with your version of node/npm: npm@11.6.2
npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"}
npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v16.20.1"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2025-10-10T10_46_03_389Z-debug-0.log
   ✖️   Failed to update npm to latest version
  ✔️   Setup Node.js 22
  ⏳   Updating Cronicle
Cronicle Installer v1.5
Copyright (c) 2015 - 2022 PixlCore.com. MIT Licensed.
Log File: /opt/cronicle/logs/install.log

Fetching release list...
Upgrading Cronicle from v0.9.90 to v0.9.95...
Updating dependencies...
Running post-install script...
Upgrade complete.

  ✔️   Updated Cronicle

🖼️ Additional context (optional).

Container created about 7 months ago and updated several times without any issue (before now)

Discord post
https://discord.com/channels/1302816934508630047/1426161956603039805/1426161956603039805

Originally created by @de666 on GitHub (Oct 11, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Cronicle Primary ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-3-pve) ### 📝 Provide a clear and concise description of the issue. I receive error messages about npm when I update cronicle with the update command within the container console ### 🔄 Steps to reproduce the issue. - Run update command inside the LXC container ### ❌ Paste the full error output (if available). ``` Reading package lists... Doneeplacing with 22 Building dependency tree... Done Reading state information... Done Package 'nodejs' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. npm ERR! code EBADENGINE npm ERR! engine Unsupported engine npm ERR! engine Not compatible with your version of node/npm: npm@11.6.2 npm ERR! notsup Not compatible with your version of node/npm: npm@11.6.2 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} npm ERR! notsup Actual: {"npm":"8.19.4","node":"v16.20.1"} npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2025-10-10T10_46_03_389Z-debug-0.log ✖️ Failed to update npm to latest version ✔️ Setup Node.js 22 ⏳ Updating Cronicle Cronicle Installer v1.5 Copyright (c) 2015 - 2022 PixlCore.com. MIT Licensed. Log File: /opt/cronicle/logs/install.log Fetching release list... Upgrading Cronicle from v0.9.90 to v0.9.95... Updating dependencies... Running post-install script... Upgrade complete. ✔️ Updated Cronicle ``` ### 🖼️ Additional context (optional). Container created about 7 months ago and updated several times without any issue (before now) Discord post https://discord.com/channels/1302816934508630047/1426161956603039805/1426161956603039805
OVERLORD added the bug label 2026-02-05 02:14:27 +03:00
OVERLORD commented 2026-02-05 02:14:39 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 11, 2025):

You need to update nodejs on the container

@michelroegl-brunner commented on GitHub (Oct 11, 2025): You need to update nodejs on the container
OVERLORD commented 2026-02-05 02:14:43 +03:00
Author
Owner
Copy Link

@de666 commented on GitHub (Oct 11, 2025):

You need to update nodejs on the container

Can you tell me the correct/best way to do it?
I see nodejs seems already be installed from apt (version 22).

@de666 commented on GitHub (Oct 11, 2025): > You need to update nodejs on the container > Can you tell me the correct/best way to do it? I see nodejs seems already be installed from apt (version 22).
OVERLORD commented 2026-02-05 02:14:48 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 11, 2025):

No, you have NodeJS 16, thats outdated since ages

apt remove -y nodejs npm
curl -fsSL https://deb.nodesource.com/setup_22.x | bash -
apt install -y nodejs

And then Run Update again

@MickLesk commented on GitHub (Oct 11, 2025): No, you have NodeJS 16, thats outdated since ages apt remove -y nodejs npm curl -fsSL https://deb.nodesource.com/setup_22.x | bash - apt install -y nodejs And then Run Update again
OVERLORD commented 2026-02-05 02:14:52 +03:00
Author
Owner
Copy Link

@de666 commented on GitHub (Oct 11, 2025):

No, you have NodeJS 16, thats outdated since ages

apt remove -y nodejs npm
curl -fsSL https://deb.nodesource.com/setup_22.x | bash -
apt install -y nodejs

And then Run Update again

Sure you are right but that's what the script installed months ago when I first create the container and I'm pretty sure I run the update command multiple times in these months and it never update nodejs. I'm wondering if it should be handled automatically by the update or not.

@de666 commented on GitHub (Oct 11, 2025): > No, you have NodeJS 16, thats outdated since ages > > apt remove -y nodejs npm > curl -fsSL https://deb.nodesource.com/setup_22.x | bash - > apt install -y nodejs > > And then Run Update again Sure you are right but that's what the script installed months ago when I first create the container and I'm pretty sure I run the update command multiple times in these months and it never update nodejs. I'm wondering if it should be handled automatically by the update or not.
OVERLORD commented 2026-02-05 02:14:56 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 11, 2025):

The system automatically upgrades nodejs with our tools, but it didn't work on your system because apt appears to be locked. Therefore, you have to fix it yourself. They've been using it since the last release > 20, which is why the error is now occurring.

@MickLesk commented on GitHub (Oct 11, 2025): The system automatically upgrades nodejs with our tools, but it didn't work on your system because apt appears to be locked. Therefore, you have to fix it yourself. They've been using it since the last release > 20, which is why the error is now occurring.
OVERLORD commented 2026-02-05 02:15:00 +03:00
Author
Owner
Copy Link

@de666 commented on GitHub (Oct 11, 2025):

The system automatically upgrades nodejs with our tools, but it didn't work on your system because apt appears to be locked. Therefore, you have to fix it yourself. They've been using it since the last release > 20, which is why the error is now occurring.

Ok thanks, but unfortunately the trick didn't work, I get the same error messages after giving the command suggested and running the update again.
Is that some other way to fix it?
Just for the record, as I said, nodejs was already installed from apt at version 22

root@cronicle:~# apt list --installed | grep nodejs
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
nodejs/nodistro,now 22.20.0-1nodesource1 amd64 [installed]
@de666 commented on GitHub (Oct 11, 2025): > The system automatically upgrades nodejs with our tools, but it didn't work on your system because apt appears to be locked. Therefore, you have to fix it yourself. They've been using it since the last release > 20, which is why the error is now occurring. Ok thanks, but unfortunately the trick didn't work, I get the same error messages after giving the command suggested and running the update again. Is that some other way to fix it? Just for the record, as I said, nodejs was already installed from apt at version 22 ``` root@cronicle:~# apt list --installed | grep nodejs WARNING: apt does not have a stable CLI interface. Use with caution in scripts. nodejs/nodistro,now 22.20.0-1nodesource1 amd64 [installed] ```
OVERLORD commented 2026-02-05 02:15:03 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 11, 2025):

its impossible to get the same issue, if you posted in post 1. Deliver an new verbose

@MickLesk commented on GitHub (Oct 11, 2025): its impossible to get the same issue, if you posted in post 1. Deliver an new verbose
OVERLORD commented 2026-02-05 02:15:07 +03:00
Author
Owner
Copy Link

@de666 commented on GitHub (Oct 11, 2025):

its impossible to get the same issue, if you posted in post 1. Deliver an new verbose

after giving you command and then the update command

Reading package lists... Doneeplacing with 22
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  nodejs*
0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
After this operation, 237 MB disk space will be freed.
(Reading database ... 34476 files and directories currently installed.)
Removing nodejs (22.20.0-1nodesource1) ...
Processing triggers for man-db (2.11.2-2) ...
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@11.6.2
npm ERR! notsup Not compatible with your version of node/npm: npm@11.6.2
npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"}
npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v16.20.1"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2025-10-11T19_52_55_577Z-debug-0.log
   ✖️   Failed to update npm to latest version
  ✔️   Setup Node.js 22
  ⏳   Updating Cronicle
Cronicle Installer v1.5
Copyright (c) 2015 - 2022 PixlCore.com. MIT Licensed.
Log File: /opt/cronicle/logs/install.log

Fetching release list...

Version 0.9.96 is already installed, and is the latest.

  ✔️   Updated Cronicle

here is the content of
/root/.npm/_logs/2025-10-11T19_52_55_577Z-debug-0.log

https://privatebin.net/?2ac11accb6e0d5a8#D8ohCxA6BXc4JMiA6UBgm678E77SXbn7gMW4KvJGan68

@de666 commented on GitHub (Oct 11, 2025): > its impossible to get the same issue, if you posted in post 1. Deliver an new verbose after giving you command and then the update command ``` Reading package lists... Doneeplacing with 22 Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: nodejs* 0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded. After this operation, 237 MB disk space will be freed. (Reading database ... 34476 files and directories currently installed.) Removing nodejs (22.20.0-1nodesource1) ... Processing triggers for man-db (2.11.2-2) ... npm ERR! code EBADENGINE npm ERR! engine Unsupported engine npm ERR! engine Not compatible with your version of node/npm: npm@11.6.2 npm ERR! notsup Not compatible with your version of node/npm: npm@11.6.2 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} npm ERR! notsup Actual: {"npm":"8.19.4","node":"v16.20.1"} npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2025-10-11T19_52_55_577Z-debug-0.log ✖️ Failed to update npm to latest version ✔️ Setup Node.js 22 ⏳ Updating Cronicle Cronicle Installer v1.5 Copyright (c) 2015 - 2022 PixlCore.com. MIT Licensed. Log File: /opt/cronicle/logs/install.log Fetching release list... Version 0.9.96 is already installed, and is the latest. ✔️ Updated Cronicle ``` here is the content of /root/.npm/_logs/2025-10-11T19_52_55_577Z-debug-0.log https://privatebin.net/?2ac11accb6e0d5a8#D8ohCxA6BXc4JMiA6UBgm678E77SXbn7gMW4KvJGan68
OVERLORD commented 2026-02-05 02:15:11 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 11, 2025):

Your system has NodeJS 16 installed. Not 22. Check your apt packages or purge all Node

Maybe remove NodeJS folder too ad then

npm cache clean -f
npm install -g npm@latest

@MickLesk commented on GitHub (Oct 11, 2025): Your system has NodeJS 16 installed. Not 22. Check your apt packages or purge all Node Maybe remove NodeJS folder too ad then npm cache clean -f npm install -g npm@latest
OVERLORD commented 2026-02-05 02:15:15 +03:00
Author
Owner
Copy Link

@de666 commented on GitHub (Oct 11, 2025):

just for the record if someone has the same issue, I did the following step to solve the problem

  • remove nodejs package with apt
  • delete /root/.nvm folder
  • delete /root/.npm folder
  • reboot
  • install nodejs back with the command suggested by @MickLesk
  • npm cache clean -f
  • npm install -g npm@latest
@de666 commented on GitHub (Oct 11, 2025): just for the record if someone has the same issue, I did the following step to solve the problem - remove nodejs package with apt - delete /root/.nvm folder - delete /root/.npm folder - reboot - install nodejs back with the command suggested by @MickLesk - npm cache clean -f - npm install -g npm@latest
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1776
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?