SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-08-04 19:45:24 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Pulse v4.0.0 Breaking update #1640

New Issue
Closed
opened 2025-11-20 05:13:59 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:13:59 -05:00
Owner
Copy Link

Originally created by @sydhenry on GitHub (Aug 5, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Pulse

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pulse.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.

As per the release, v4 is a rewrite in go that used a single binary

https://github.com/rcourtman/Pulse/releases/tag/v4.0.0

One specific breaking script change is the release pulled has a different file structure so when npm can't find the package.json (because it is no longer a nodeJS package but a go bin)

🔄 Steps to reproduce the issue.

  1. run the command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pulse.sh)"
  2. LXC should say it is successfully created
  3. web application will not work
  4. Logging into the LXC will show that application has not be installed properly, and service fails to start.

❌ Paste the full error output (if available).

$ journalctl -u pulse
Aug 04 23:20:30 pulse systemd[1]: Started pulse.service - Pulse Monitoring Application.
Aug 04 23:20:31 pulse npm[11578]: npm error code ENOENT
Aug 04 23:20:31 pulse npm[11578]: npm error syscall open
Aug 04 23:20:31 pulse npm[11578]: npm error path /opt/pulse/package.json
Aug 04 23:20:31 pulse npm[11578]: npm error errno -2
Aug 04 23:20:31 pulse npm[11578]: npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/>
Aug 04 23:20:31 pulse npm[11578]: npm error enoent This is related to npm not being able to find a file.
Aug 04 23:20:31 pulse npm[11578]: npm error enoent

this is how /opt/pulse ends up, without install.sh being ran

root@pulse:~# ls -al /opt/pulse
total 15416
drwxr-xr-x 4 pulse pulse      15 Aug  4 23:20 .
drwxr-xr-x 4 root  root        5 Aug  4 23:20 ..
-rw-r--r-- 1 pulse pulse       0 Aug  4 23:20 .env
-rw-r--r-- 1 pulse pulse       0 Aug  4 16:07 .first-run-cleanup
drwxr-xr-x 3 pulse pulse       3 Aug  4 16:07 frontend-modern
-rw-r--r-- 1 pulse pulse    8742 Aug  4 16:07 install.sh
-rw-r--r-- 1 pulse pulse    1065 Aug  4 16:07 LICENSE
-rw-r--r-- 1 pulse pulse    1262 Aug  4 16:07 pulse
-rw-r--r-- 1 pulse pulse 9089024 Aug  4 16:07 pulse-linux-amd64
-rw-r--r-- 1 pulse pulse 8650752 Aug  4 16:07 pulse-linux-arm64
-rw-r--r-- 1 pulse pulse 8716288 Aug  4 16:07 pulse-linux-armv7
-rw-r--r-- 1 pulse pulse    1262 Aug  4 16:07 pulse-wrapper.sh
-rw-r--r-- 1 pulse pulse    8264 Aug  4 16:07 README.md
drwxr-xr-x 2 pulse pulse       3 Aug  4 16:07 server
-rw-r--r-- 1 pulse pulse       6 Aug  4 16:07 VERSION

🖼️ Additional context (optional).

I haven't been able to look too much into it, but here is how to migrate https://github.com/rcourtman/Pulse/blob/main/docs/MIGRATION_V3_TO_V4.md

Not sure if the script system can be set up to successfully upgrade from a v3 to v4 install, or if there should be a Pulse V3 and a Pulse v4

Originally created by @sydhenry on GitHub (Aug 5, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Pulse ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pulse.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. As per the release, v4 is a rewrite in go that used a single binary https://github.com/rcourtman/Pulse/releases/tag/v4.0.0 One specific breaking script change is the release pulled has a different file structure so when npm can't find the package.json (because it is no longer a nodeJS package but a go bin) ### 🔄 Steps to reproduce the issue. 1. run the command `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pulse.sh)"` 2. LXC should say it is successfully created 3. web application will not work 4. Logging into the LXC will show that application has not be installed properly, and service fails to start. ### ❌ Paste the full error output (if available). ``` $ journalctl -u pulse Aug 04 23:20:30 pulse systemd[1]: Started pulse.service - Pulse Monitoring Application. Aug 04 23:20:31 pulse npm[11578]: npm error code ENOENT Aug 04 23:20:31 pulse npm[11578]: npm error syscall open Aug 04 23:20:31 pulse npm[11578]: npm error path /opt/pulse/package.json Aug 04 23:20:31 pulse npm[11578]: npm error errno -2 Aug 04 23:20:31 pulse npm[11578]: npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/> Aug 04 23:20:31 pulse npm[11578]: npm error enoent This is related to npm not being able to find a file. Aug 04 23:20:31 pulse npm[11578]: npm error enoent ``` this is how /opt/pulse ends up, without install.sh being ran ``` root@pulse:~# ls -al /opt/pulse total 15416 drwxr-xr-x 4 pulse pulse 15 Aug 4 23:20 . drwxr-xr-x 4 root root 5 Aug 4 23:20 .. -rw-r--r-- 1 pulse pulse 0 Aug 4 23:20 .env -rw-r--r-- 1 pulse pulse 0 Aug 4 16:07 .first-run-cleanup drwxr-xr-x 3 pulse pulse 3 Aug 4 16:07 frontend-modern -rw-r--r-- 1 pulse pulse 8742 Aug 4 16:07 install.sh -rw-r--r-- 1 pulse pulse 1065 Aug 4 16:07 LICENSE -rw-r--r-- 1 pulse pulse 1262 Aug 4 16:07 pulse -rw-r--r-- 1 pulse pulse 9089024 Aug 4 16:07 pulse-linux-amd64 -rw-r--r-- 1 pulse pulse 8650752 Aug 4 16:07 pulse-linux-arm64 -rw-r--r-- 1 pulse pulse 8716288 Aug 4 16:07 pulse-linux-armv7 -rw-r--r-- 1 pulse pulse 1262 Aug 4 16:07 pulse-wrapper.sh -rw-r--r-- 1 pulse pulse 8264 Aug 4 16:07 README.md drwxr-xr-x 2 pulse pulse 3 Aug 4 16:07 server -rw-r--r-- 1 pulse pulse 6 Aug 4 16:07 VERSION ``` ### 🖼️ Additional context (optional). I haven't been able to look too much into it, but here is how to migrate https://github.com/rcourtman/Pulse/blob/main/docs/MIGRATION_V3_TO_V4.md Not sure if the script system can be set up to successfully upgrade from a v3 to v4 install, or if there should be a Pulse V3 and a Pulse v4
saavagebueno added the bug label 2025-11-20 05:13:59 -05:00
saavagebueno commented 2025-11-20 05:14:00 -05:00
Author
Owner
Copy Link

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

There is already an PR, why create an issue for Things that are already fixed (but Not merged yet)?? #6574

@MickLesk commented on GitHub (Aug 6, 2025): There is already an PR, why create an issue for Things that are already fixed (but Not merged yet)?? #6574
saavagebueno commented 2025-11-20 05:14:00 -05:00
Author
Owner
Copy Link

@sydhenry commented on GitHub (Aug 6, 2025):

Apologies, I didn't mean to - I thought I did due diligence. I looked for all recent commits to the pulse files and found none, I must have missed that there was a branch ahead. I also didn't realize that there might be a pull request for it without an issue.

@sydhenry commented on GitHub (Aug 6, 2025): Apologies, I didn't mean to - I thought I did due diligence. I looked for all recent commits to the pulse files and found none, I must have missed that there was a branch ahead. I also didn't realize that there might be a pull request for it without an issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1640
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?