[GH-ISSUE #5684] Error in MQTT install #1216

Closed
opened 2026-02-26 12:48:08 +03:00 by kerem · 10 comments
Owner

Originally created by @rmunizsanc on GitHub (Jul 4, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5684

Have you read and understood the above guidelines?

yes

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

Mqtt

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

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

I try to install MQTT server.

Execute the script using verbose, without any special config

🔄 Steps to reproduce the issue.

Step 1.
Execute the script

Step 2.
Select Verbose

Step 3.
Wait to error

Paste the full error output (if available).

__  _______  ____________

/ |/ / __ /_ _/ /
/ /|/ / / / / / / / /
/ / / / /
/ / / / / /
// //_
_// //

⚙️ Using Default Settings on node pve (🔍 Verbose)
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
💾 Disk Size: 2 GB
🧠 CPU Cores: 1
🛠️ RAM Size: 512 MiB
🆔 Container ID: 102
🔍 Verbose Mode: Enabled
🚀 Creating a MQTT LXC using the above default settings

✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ LXC Template List Updated
✔️ LXC Template 'debian-12-standard_12.7-1_amd64.tar.zst' is ready to use.
✔️ LXC Container 102 was successfully created.
✔️ Started LXC Container
Customizing LXC Container
[ERROR] in line 1176: exit code 0: while executing command pct exec "$CTID" -- bash -c "echo $tz >/etc/timezone && ln -sf /usr/share/zoneinfo/$tz /etc/localtime"

🖼️ Additional context (optional).

No response

Originally created by @rmunizsanc on GitHub (Jul 4, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5684 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Mqtt ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mqtt.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. I try to install MQTT server. Execute the script using verbose, without any special config ### 🔄 Steps to reproduce the issue. Step 1. Execute the script Step 2. Select Verbose Step 3. Wait to error ### ❌ Paste the full error output (if available). __ _______ ____________ / |/ / __ \/_ __/_ __/ / /|_/ / / / / / / / / / / / / /_/ / / / / / /_/ /_/\___\_\/_/ /_/ ⚙️ Using Default Settings on node pve (🔍 Verbose) 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 2 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 512 MiB 🆔 Container ID: 102 🔍 Verbose Mode: Enabled 🚀 Creating a MQTT LXC using the above default settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ LXC Template List Updated ✔️ LXC Template 'debian-12-standard_12.7-1_amd64.tar.zst' is ready to use. ✔️ LXC Container 102 was successfully created. ✔️ Started LXC Container ⏳ Customizing LXC Container [ERROR] in line 1176: exit code 0: while executing command pct exec "$CTID" -- bash -c "echo $tz >/etc/timezone && ln -sf /usr/share/zoneinfo/$tz /etc/localtime" ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:48:08 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@MickLesk commented on GitHub (Jul 4, 2025):

Timezone Issue on your Proxmox

timedatectl

timedatectl set-timezone Europe/Berlin (or your tz) 

dpkg-reconfigure tzdata

timedatectl
<!-- gh-comment-id:3034820263 --> @MickLesk commented on GitHub (Jul 4, 2025): Timezone Issue on your Proxmox ```bash timedatectl timedatectl set-timezone Europe/Berlin (or your tz) dpkg-reconfigure tzdata timedatectl ```
Author
Owner

@rmunizsanc commented on GitHub (Jul 4, 2025):

I try this option but is correct.

I try to execute again and get these messages.

Image

In these case the execution is correct

<!-- gh-comment-id:3034857095 --> @rmunizsanc commented on GitHub (Jul 4, 2025): I try this option but is correct. I try to execute again and get these messages. ![Image](https://github.com/user-attachments/assets/6b3b2edc-cecf-4bf9-8b9e-a4855930d8a4) In these case the execution is correct
Author
Owner

@MickLesk commented on GitHub (Jul 4, 2025):

That look okay, its just the verbose output

<!-- gh-comment-id:3034881638 --> @MickLesk commented on GitHub (Jul 4, 2025): That look okay, its just the verbose output
Author
Owner

@rmunizsanc commented on GitHub (Jul 4, 2025):

I try to execute without verbose and the error again

Image

If try to execute the command timedatectl
Image

<!-- gh-comment-id:3034899350 --> @rmunizsanc commented on GitHub (Jul 4, 2025): I try to execute without verbose and the error again ![Image](https://github.com/user-attachments/assets/0dd2bb92-b920-47a1-b412-cd416f6e205c) If try to execute the command timedatectl ![Image](https://github.com/user-attachments/assets/bed71eb6-9e9d-430f-8257-ab4f0a5ff090)
Author
Owner

@MickLesk commented on GitHub (Jul 4, 2025):

do you have the same issue, if you execute the dev script for debian?

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

<!-- gh-comment-id:3034922246 --> @MickLesk commented on GitHub (Jul 4, 2025): do you have the same issue, if you execute the dev script for debian? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/debian.sh)"
Author
Owner

@rmunizsanc commented on GitHub (Jul 4, 2025):

Its work well

Image

<!-- gh-comment-id:3034939576 --> @rmunizsanc commented on GitHub (Jul 4, 2025): Its work well ![Image](https://github.com/user-attachments/assets/291ebad7-3073-49b9-8652-6731e3fe700c)
Author
Owner

@MickLesk commented on GitHub (Jul 4, 2025):

okay, then please wait for bigger PR of core functionality, there is an additional check since some weeks, i prepare it today or tomorrow

<!-- gh-comment-id:3034945388 --> @MickLesk commented on GitHub (Jul 4, 2025): okay, then please wait for bigger PR of core functionality, there is an additional check since some weeks, i prepare it today or tomorrow
Author
Owner

@rmunizsanc commented on GitHub (Jul 4, 2025):

Ok, thank you for the support.

Regards

<!-- gh-comment-id:3034997158 --> @rmunizsanc commented on GitHub (Jul 4, 2025): Ok, thank you for the support. Regards
Author
Owner

@jsbrich commented on GitHub (Jul 4, 2025):

Got the same error using the Graylog install script.

<!-- gh-comment-id:3036960822 --> @jsbrich commented on GitHub (Jul 4, 2025): Got the same error using the Graylog install script.
Author
Owner

@MickLesk commented on GitHub (Jul 4, 2025):

Retry it and done

<!-- gh-comment-id:3036967240 --> @MickLesk commented on GitHub (Jul 4, 2025): Retry it and done
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#1216
No description provided.