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

Zammad update errors out #2130

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

Originally created by @Sedation6612 on GitHub (Dec 6, 2025).

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

Zammad

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.1.2

📝 Provide a clear and concise description of the issue.

Attempted to update my Zammad LXC, it errored out.

🔄 Steps to reproduce the issue.

Run the update script within a Zammad LXC.

❌ Paste the full error output (if available).

 _____                                       __
/__  /  ____ _____ ___  ____ ___  ____ _____/ /
  / /  / __ `/ __ `__ \/ __ `__ \/ __ `/ __  / 
 / /__/ /_/ / / / / / / / / / / / /_/ / /_/ /  
/____/\__,_/_/ /_/ /_/_/ /_/ /_/\__,_/\__,_/   
                                               

  ✔️   Stopped Service
  ✖️   in line 37: exit code 100 (APT: Package manager error (broken packages / dependency problems))
 → apt -y upgrade
--- Last 10 lines of silent log ---
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details.

Something went wrong. Please check any error output above and fix the issues.
Then run the package installation again.
dpkg: error processing package zammad (--configure):
 installed zammad package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 zammad
Error: Sub-process /usr/bin/dpkg returned an error code (1)
-----------------------------------
 📋 View full log (46 lines): /tmp/create-lxc-0633e3b8.log


----
Logfile:

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Hit:1 http://security.debian.org trixie-security InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Hit:4 https://artifacts.elastic.co/packages/7.x/apt stable InRelease
Get:5 https://dl.packager.io/srv/deb/zammad/zammad/stable/debian 12 InRelease [1,845 B]
Fetched 1,845 B in 1s (1,910 B/s)
Reading package lists...
Building dependency tree...
Reading state information...
1 package can be upgraded. Run 'apt list --upgradable' to see it.
Warning: https://dl.packager.io/srv/deb/zammad/zammad/stable/debian/dists/12/InRelease: Policy will reject signature within a year, see --audit for details
zammad set on hold.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
Not upgrading:
  zammad

Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 1
  1 not fully installed or removed.
  Space needed: 0 B / 5,269 MB available

Setting up zammad (6.5.2-1764330797.bc4a754e.bookworm) ...
# Enforcing Redis...
# Creating Redis bootstart
Synchronizing state of redis-server.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.^M
Executing: /usr/lib/systemd/systemd-sysv-install enable redis-server^M
# Starting Redis server
^[[0;1;31mJob for redis-server.service failed because the control process exited with error code.^[[0m^M
^[[0;1;31mSee "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details.^[[0m^M

Something went wrong. Please check any error output above and fix the issues.
Then run the package installation again.
dpkg: error processing package zammad (--configure):
 installed zammad package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 zammad
Error: Sub-process /usr/bin/dpkg returned an error code (1)

🖼️ Additional context (optional).

No response

Originally created by @Sedation6612 on GitHub (Dec 6, 2025). ### ✅ 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? Zammad ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zammad.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.1.2 ### 📝 Provide a clear and concise description of the issue. Attempted to update my Zammad LXC, it errored out. ### 🔄 Steps to reproduce the issue. Run the update script within a Zammad LXC. ### ❌ Paste the full error output (if available). ``` _____ __ /__ / ____ _____ ___ ____ ___ ____ _____/ / / / / __ `/ __ `__ \/ __ `__ \/ __ `/ __ / / /__/ /_/ / / / / / / / / / / / /_/ / /_/ / /____/\__,_/_/ /_/ /_/_/ /_/ /_/\__,_/\__,_/ ✔️ Stopped Service ✖️ in line 37: exit code 100 (APT: Package manager error (broken packages / dependency problems)) → apt -y upgrade --- Last 10 lines of silent log --- Job for redis-server.service failed because the control process exited with error code. See "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details. Something went wrong. Please check any error output above and fix the issues. Then run the package installation again. dpkg: error processing package zammad (--configure): installed zammad package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: zammad Error: Sub-process /usr/bin/dpkg returned an error code (1) ----------------------------------- 📋 View full log (46 lines): /tmp/create-lxc-0633e3b8.log ---- Logfile: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Hit:1 http://security.debian.org trixie-security InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://artifacts.elastic.co/packages/7.x/apt stable InRelease Get:5 https://dl.packager.io/srv/deb/zammad/zammad/stable/debian 12 InRelease [1,845 B] Fetched 1,845 B in 1s (1,910 B/s) Reading package lists... Building dependency tree... Reading state information... 1 package can be upgraded. Run 'apt list --upgradable' to see it. Warning: https://dl.packager.io/srv/deb/zammad/zammad/stable/debian/dists/12/InRelease: Policy will reject signature within a year, see --audit for details zammad set on hold. WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... Not upgrading: zammad Summary: Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 1 1 not fully installed or removed. Space needed: 0 B / 5,269 MB available Setting up zammad (6.5.2-1764330797.bc4a754e.bookworm) ... # Enforcing Redis... # Creating Redis bootstart Synchronizing state of redis-server.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.^M Executing: /usr/lib/systemd/systemd-sysv-install enable redis-server^M # Starting Redis server ^[[0;1;31mJob for redis-server.service failed because the control process exited with error code.^[[0m^M ^[[0;1;31mSee "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details.^[[0m^M Something went wrong. Please check any error output above and fix the issues. Then run the package installation again. dpkg: error processing package zammad (--configure): installed zammad package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: zammad Error: Sub-process /usr/bin/dpkg returned an error code (1) ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:52:00 +03:00
OVERLORD commented 2026-02-05 03:52:11 +03:00
Author
Owner
Copy Link

@akh7177 commented on GitHub (Dec 6, 2025):

Hello @Sedation6612 ,

Was the redis server service running before executing the script?

@akh7177 commented on GitHub (Dec 6, 2025): Hello @Sedation6612 , Was the redis server service running before executing the script?
OVERLORD commented 2026-02-05 03:52:20 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 7, 2025):

Hi, its an source issue with bookworm <> trixie. Try this, or recreate the lxc after 9750 merged. It should fix it.

sed -i 's/Suites: 12/Suites: 13/' /etc/apt/sources.list.d/zammad.sources
dpkg --configure -a && systemctl start zammad
@MickLesk commented on GitHub (Dec 7, 2025): Hi, its an source issue with bookworm <> trixie. Try this, or recreate the lxc after 9750 merged. It should fix it. ```bash sed -i 's/Suites: 12/Suites: 13/' /etc/apt/sources.list.d/zammad.sources dpkg --configure -a && systemctl start zammad ```
OVERLORD commented 2026-02-05 03:52:24 +03:00
Author
Owner
Copy Link

@Sedation6612 commented on GitHub (Dec 7, 2025):

Hi, its an source issue with bookworm <> trixie. Try this, or recreate the lxc after 9750 merged. It should fix it.

sed -i 's/Suites: 12/Suites: 13/' /etc/apt/sources.list.d/zammad.sources
dpkg --configure -a && systemctl start zammad

root@memozammad:/etc/network# sed -i 's/Suites: 12/Suites: 13/' /etc/apt/sources.list.d/zammad.sources
root@memozammad:/etc/network# dpkg --configure -a && systemctl start zammad
Setting up zammad (6.5.2-1764330797.bc4a754e.bookworm) ...
# Enforcing Redis...
# Creating Redis bootstart
Synchronizing state of redis-server.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable redis-server
# Starting Redis server
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details.

Something went wrong. Please check any error output above and fix the issues.
Then run the package installation again.
dpkg: error processing package zammad (--configure):
 installed zammad package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 zammad

This is the error I got when I attempted to run these commands.

@Sedation6612 commented on GitHub (Dec 7, 2025): > Hi, its an source issue with bookworm <> trixie. Try this, or recreate the lxc after 9750 merged. It should fix it. > > sed -i 's/Suites: 12/Suites: 13/' /etc/apt/sources.list.d/zammad.sources > dpkg --configure -a && systemctl start zammad ``` root@memozammad:/etc/network# sed -i 's/Suites: 12/Suites: 13/' /etc/apt/sources.list.d/zammad.sources root@memozammad:/etc/network# dpkg --configure -a && systemctl start zammad Setting up zammad (6.5.2-1764330797.bc4a754e.bookworm) ... # Enforcing Redis... # Creating Redis bootstart Synchronizing state of redis-server.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable redis-server # Starting Redis server Job for redis-server.service failed because the control process exited with error code. See "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details. Something went wrong. Please check any error output above and fix the issues. Then run the package installation again. dpkg: error processing package zammad (--configure): installed zammad package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: zammad ``` This is the error I got when I attempted to run these commands.
OVERLORD commented 2026-02-05 03:52:27 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 7, 2025):

ah they have removed the deb13 repo from stable to dev, so it always fail. Only Possible Solution is an Recreation of the LXC after the PR is merged

@MickLesk commented on GitHub (Dec 7, 2025): ah they have removed the deb13 repo from stable to dev, so it always fail. Only Possible Solution is an Recreation of the LXC after the PR is merged
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#2130
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?