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 13 Packages Projects Releases 10 Wiki Activity

SQL Server 2022 Update Script Failing #2441

New Issue
Closed
opened 2026-02-05 04:52:44 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 04:52:44 +03:00
Owner
Copy Link

Originally created by @siyual on GitHub (Feb 4, 2026).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

SQLServer2022

📂 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?

Ubuntu 22.04

📈 Which Proxmox version are you on?

8.4.16

📝 Provide a clear and concise description of the issue.

Running update instantly fails. This happens on both silent and verbose.

🔄 Steps to reproduce the issue.

Step 1: run update
Step 2: be sad.

❌ Paste the full error output (if available).

SQL Server 2022 LXC Container
🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE

🖥️   OS: Ubuntu - Version: 22.04
🏠   Hostname: sqlsandbox
💡   IP Address: 192.168.50.58

✖️ in line 10: exit code 1 (General error / Operation not permitted): while executing command tr '
' ' '
✖️ in line 10: exit code 1 (General error / Operation not permitted): while executing command debuginfod_urls=sh -c "cat ${prefix}/etc/debuginfod/*.urls 2>/dev/null" | tr ' ' ' '

🖼️ Additional context (optional).

No response

Originally created by @siyual on GitHub (Feb 4, 2026). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? SQLServer2022 ### 📂 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? Ubuntu 22.04 ### 📈 Which Proxmox version are you on? 8.4.16 ### 📝 Provide a clear and concise description of the issue. Running `update` instantly fails. This happens on both silent and verbose. ### 🔄 Steps to reproduce the issue. Step 1: run `update` Step 2: be sad. ### ❌ Paste the full error output (if available). SQL Server 2022 LXC Container 🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE 🖥️ OS: Ubuntu - Version: 22.04 🏠 Hostname: sqlsandbox 💡 IP Address: 192.168.50.58 ✖️ in line 10: exit code 1 (General error / Operation not permitted): while executing command tr ' ' ' ' ✖️ in line 10: exit code 1 (General error / Operation not permitted): while executing command debuginfod_urls=`sh -c "cat ${prefix}/etc/debuginfod/*.urls 2>/dev/null" | tr ' ' ' '` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the questionbug labels 2026-02-05 04:52:44 +03:00
OVERLORD commented 2026-02-05 04:52:55 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Feb 4, 2026):

You didn't happen to run update while logged into the LXC as a non-root user, did you?

@vhsdream commented on GitHub (Feb 4, 2026): You didn't happen to run `update` while logged into the LXC as a non-root user, did you?
OVERLORD commented 2026-02-05 04:52:59 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 4, 2026):

SQLServer 2022 hasnt an "big" update. Its just apt. This lines above should not be part of our scripts.

    msg_info "Updating ${APP} LXC"
    $STD apt update
    $STD apt -y upgrade
    msg_ok "Updated successfully!"
@MickLesk commented on GitHub (Feb 4, 2026): SQLServer 2022 hasnt an "big" update. Its just apt. This lines above should not be part of our scripts. ```bash msg_info "Updating ${APP} LXC" $STD apt update $STD apt -y upgrade msg_ok "Updated successfully!" ```
OVERLORD commented 2026-02-05 04:53:04 +03:00
Author
Owner
Copy Link

@siyual commented on GitHub (Feb 4, 2026):

You didn't happen to run update while logged into the LXC as a non-root user, did you?

I was logged in as root to do the updates

@siyual commented on GitHub (Feb 4, 2026): > You didn't happen to run `update` while logged into the LXC as a non-root user, did you? I was logged in as root to do the updates
OVERLORD commented 2026-02-05 04:53:08 +03:00
Author
Owner
Copy Link

@siyual commented on GitHub (Feb 4, 2026):

SQLServer 2022 hasnt an "big" update. Its just apt. This lines above should not be part of our scripts.

    msg_info "Updating ${APP} LXC"
    $STD apt update
    $STD apt -y upgrade
    msg_ok "Updated successfully!"

Not sure what you mean. apt update wasn't the issue. That works fine.

It's the update command that generates the instant error. Whether it has an update to perform or not is irrelevant - if there's nothing for it to do, it should just report that it finished and didn't have anything to update, not throw ambiguous error messages.

So no, I don't think this is resolved at all.

@siyual commented on GitHub (Feb 4, 2026): > SQLServer 2022 hasnt an "big" update. Its just apt. This lines above should not be part of our scripts. > ```bash > msg_info "Updating ${APP} LXC" > $STD apt update > $STD apt -y upgrade > msg_ok "Updated successfully!" > ``` Not sure what you mean. `apt update` wasn't the issue. That works fine. It's the `update` command that generates the instant error. Whether it has an update to perform or not is irrelevant - if there's nothing for it to do, it should just report that it finished and didn't have anything to update, not throw ambiguous error messages. So no, I don't think this is resolved at all.
OVERLORD commented 2026-02-05 04:53:11 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 4, 2026):

i mean, "update" is just apt update && apt upgrade

@MickLesk commented on GitHub (Feb 4, 2026): i mean, "update" is just apt update && apt upgrade
OVERLORD commented 2026-02-05 04:53:13 +03:00
Author
Owner
Copy Link

@siyual commented on GitHub (Feb 4, 2026):

This image might help describe what I'm seeing:

Image

The above is from running update only. But apt update && apt upgrade works fine:

Image
@siyual commented on GitHub (Feb 4, 2026): This image might help describe what I'm seeing: <img width="1449" height="615" alt="Image" src="https://github.com/user-attachments/assets/bcad537e-7591-43ee-b432-c35f0d29bfc6" /> The above is from running `update` only. But `apt update && apt upgrade` works fine: <img width="923" height="617" alt="Image" src="https://github.com/user-attachments/assets/8bb0eeec-44e2-434d-bca8-669f070cb348" />
OVERLORD commented 2026-02-05 04:53:18 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 4, 2026):

Microsoft idiots create an debug-file which is defect

rm -f /etc/profile.d/debuginfod.sh /etc/profile.d/debuginfod.csh should solve it

@MickLesk commented on GitHub (Feb 4, 2026): Microsoft idiots create an debug-file which is defect rm -f /etc/profile.d/debuginfod.sh /etc/profile.d/debuginfod.csh should solve it
OVERLORD commented 2026-02-05 04:53:22 +03:00
Author
Owner
Copy Link

@siyual commented on GitHub (Feb 5, 2026):

That did the ticket - thanks!

@siyual commented on GitHub (Feb 5, 2026): That did the ticket - thanks!
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 question
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#2441
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?