[GH-ISSUE #12300] Zammad installation script fails eslasticsearch #2565

Closed
opened 2026-02-26 12:52:51 +03:00 by kerem · 3 comments
Owner

Originally created by @kailun18 on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/12300

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

No (this issue will likely be closed automatically)

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

No response

📈 Which Proxmox version are you on?

9.1.5

📝 Provide a clear and concise description of the issue.

Identical to issue at https://github.com/community-scripts/ProxmoxVE/issues/12111 except it's now moved to line 36 instead of line 35.

🔄 Steps to reproduce the issue.

Run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zammad.sh)" from Proxmox shell, try install with defaults

Paste the full error output (if available).

 _____                                       __
/__  /  ____ _____ ___  ____ ___  ____ _____/ /
  / /  / __ `/ __ `__ \/ __ `__ \/ __ `/ __  / 
 / /__/ /_/ / / / / / / / / / / / /_/ / /_/ /  
/____/\__,_/_/ /_/ /_/_/ /_/ /_/\__,_/\__,_/   
                                               
  ⚙️  Using Default Settings on node proxmox2
  💡  PVE Version 9.1.5 (Kernel: 6.17.9-1-pve)
  🆔  Container ID: 101
  🖥️  Operating System: debian (12)
  📦  Container Type: Unprivileged
  💾  Disk Size: 8 GB
  🧠  CPU Cores: 2
  🛠️  RAM Size: 4096 MiB
  🚀  Creating a Zammad LXC using the above default settings
  
  ✔️   Storage local (Free: 11.0GB  Used: 53.4GB) [Template]
  ✔️   Storage data (Free: 876.7GB  Used: 36.2GB) [Container]
  ✔️   Storage 'data' (lvmthin) validated
  ✔️   Template storage 'local' validated
  ✔️   Template search completed
  ✔️   Template debian-12-standard_12.7-1_amd64.tar.zst [local]
  ✔️   LXC Container 101 was successfully created.
  ✔️   Started LXC Container
  ✔️   Network in LXC is reachable (ping)
Extracting templates from packages: 100%
  ✔️   Customized LXC Container
  ✔️   Set up Container OS
  ✔️   Network Connected: 10.6.80.128 
  ✔️   IPv4 Internet Connected
  ✖️   IPv6 Internet Not Connected
  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
  ✔️   Updated Container OS
  ✔️   Installed Dependencies
  ✖️   in line 36: exit code 1 (General error / Operation not permitted): while executing command systemctl restart -q elasticsearch

  --- Last 20 lines of log ---
 sudo systemctl daemon-reload
 sudo systemctl enable elasticsearch.service
### You can start elasticsearch service by executing
 sudo systemctl start elasticsearch.service
Created elasticsearch keystore in /etc/elasticsearch/elasticsearch.keystore
-> Installing ingest-attachment
-> Downloading ingest-attachment from elastic
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@     WARNING: plugin requires additional permissions     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
* java.lang.RuntimePermission accessClassInPackage.sun.java2d.cmm.kcms
* java.lang.RuntimePermission accessDeclaredMembers
* java.lang.RuntimePermission getClassLoader
* java.lang.reflect.ReflectPermission suppressAccessChecks
* java.security.SecurityPermission createAccessControlContext
See https://docs.oracle.com/javase/8/docs/technotes/guides/security/permissions.html
for descriptions of what these permissions allow and the associated risks.
-> Installed ingest-attachment
-> Please restart Elasticsearch to activate any plugins installed
[2026-02-24 22:45:58] [ERROR] in line 36: exit code 1 (General error / Operation not permitted): while executing command systemctl restart -q elasticsearch
  -----------------------------------

  ✖️   Installation failed in container 101 (exit code: 1)

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

🖼️ Additional context (optional).

No response

Originally created by @kailun18 on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/12300 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? No (this issue will likely be closed automatically) ### 📜 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? _No response_ ### 📈 Which Proxmox version are you on? 9.1.5 ### 📝 Provide a clear and concise description of the issue. Identical to issue at https://github.com/community-scripts/ProxmoxVE/issues/12111 except it's now moved to line 36 instead of line 35. ### 🔄 Steps to reproduce the issue. Run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zammad.sh)" from Proxmox shell, try install with defaults ### ❌ Paste the full error output (if available). ``` _____ __ /__ / ____ _____ ___ ____ ___ ____ _____/ / / / / __ `/ __ `__ \/ __ `__ \/ __ `/ __ / / /__/ /_/ / / / / / / / / / / / /_/ / /_/ / /____/\__,_/_/ /_/ /_/_/ /_/ /_/\__,_/\__,_/ ⚙️ Using Default Settings on node proxmox2 💡 PVE Version 9.1.5 (Kernel: 6.17.9-1-pve) 🆔 Container ID: 101 🖥️ Operating System: debian (12) 📦 Container Type: Unprivileged 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 4096 MiB 🚀 Creating a Zammad LXC using the above default settings ✔️ Storage local (Free: 11.0GB Used: 53.4GB) [Template] ✔️ Storage data (Free: 876.7GB Used: 36.2GB) [Container] ✔️ Storage 'data' (lvmthin) validated ✔️ Template storage 'local' validated ✔️ Template search completed ✔️ Template debian-12-standard_12.7-1_amd64.tar.zst [local] ✔️ LXC Container 101 was successfully created. ✔️ Started LXC Container ✔️ Network in LXC is reachable (ping) Extracting templates from packages: 100% ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 10.6.80.128 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Installed Dependencies ✖️ in line 36: exit code 1 (General error / Operation not permitted): while executing command systemctl restart -q elasticsearch --- Last 20 lines of log --- sudo systemctl daemon-reload sudo systemctl enable elasticsearch.service ### You can start elasticsearch service by executing sudo systemctl start elasticsearch.service Created elasticsearch keystore in /etc/elasticsearch/elasticsearch.keystore -> Installing ingest-attachment -> Downloading ingest-attachment from elastic @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: plugin requires additional permissions @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ * java.lang.RuntimePermission accessClassInPackage.sun.java2d.cmm.kcms * java.lang.RuntimePermission accessDeclaredMembers * java.lang.RuntimePermission getClassLoader * java.lang.reflect.ReflectPermission suppressAccessChecks * java.security.SecurityPermission createAccessControlContext See https://docs.oracle.com/javase/8/docs/technotes/guides/security/permissions.html for descriptions of what these permissions allow and the associated risks. -> Installed ingest-attachment -> Please restart Elasticsearch to activate any plugins installed [2026-02-24 22:45:58] [ERROR] in line 36: exit code 1 (General error / Operation not permitted): while executing command systemctl restart -q elasticsearch ----------------------------------- ✖️ Installation failed in container 101 (exit code: 1) [1]+ Stopped bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zammad.sh)" ``` ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:52:51 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

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

You need ipv6 for elasticsearch & zammad

<!-- gh-comment-id:3955265254 --> @MickLesk commented on GitHub (Feb 24, 2026): You need ipv6 for elasticsearch & zammad
Author
Owner

@kailun18 commented on GitHub (Feb 25, 2026):

Is it a requirement that ipv6 needs to be connected during the creation?

I'm not sure that this is the source of the error - I tried to set a generic static ipv6 address and it still comes up with the same error. Any other suggestions to fix it?

<!-- gh-comment-id:3957744750 --> @kailun18 commented on GitHub (Feb 25, 2026): Is it a requirement that ipv6 needs to be connected during the creation? I'm not sure that this is the source of the error - I tried to set a generic static ipv6 address and it still comes up with the same error. Any other suggestions to fix it?
Author
Owner

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

hm, my install on my nodes work fine. Ive fixed it blind as example to their docs. You can try it after merge. Give feedback afterwards please

<!-- gh-comment-id:3957864789 --> @MickLesk commented on GitHub (Feb 25, 2026): hm, my install on my nodes work fine. Ive fixed it blind as example to their docs. You can try it after merge. Give feedback afterwards please
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2565
No description provided.