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

Pulse script problems on update version #1996

New Issue
Closed
opened 2025-11-20 05:21:26 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:21:26 -05:00
Owner
Copy Link

Originally created by @ither on GitHub (Oct 2, 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

📈 Which Proxmox version are you on?

pve-manager/8.1.10/4b06efb5db453f29 (running kernel: 6.2.16-20-pve)

📝 Provide a clear and concise description of the issue.

I had problems updating Pulse to the last version. For some reason, the update script tries to execute a chown in the directories /etc/pulse and /opt/pulse at line 43:

...
chown -R pulse:pulse /etc/pulse /opt/pulse
...

When the directory /etc/pulse does not exist. Deleting the reference from that line and leaving only /opt/pulse is enough for the script to run correctly.

🔄 Steps to reproduce the issue.

  • run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pulse.sh)" from the command line of the LXC to update

❌ Paste the full error output (if available).

chown: cannot access ‘/etc/pulse’: No such file or directory

🖼️ Additional context (optional).

No response

Originally created by @ither on GitHub (Oct 2, 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 ### 📈 Which Proxmox version are you on? pve-manager/8.1.10/4b06efb5db453f29 (running kernel: 6.2.16-20-pve) ### 📝 Provide a clear and concise description of the issue. I had problems updating Pulse to the last version. For some reason, the update script tries to execute a `chown` in the directories `/etc/pulse` and `/opt/pulse` at line 43: ```bash ... chown -R pulse:pulse /etc/pulse /opt/pulse ... ``` When the directory `/etc/pulse` does not exist. Deleting the reference from that line and leaving only `/opt/pulse` is enough for the script to run correctly. ### 🔄 Steps to reproduce the issue. - run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pulse.sh)"` from the command line of the LXC to update ### ❌ Paste the full error output (if available). chown: cannot access ‘/etc/pulse’: No such file or directory ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:21:26 -05:00
saavagebueno commented 2025-11-20 05:21:27 -05:00
Author
Owner
Copy Link

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

@rcourtman @vhsdream

@MickLesk commented on GitHub (Oct 3, 2025): @rcourtman @vhsdream
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#1996
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?