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

Graylog lxc script fails when installing from a config file #1270

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

Originally created by @tuxhobo on GitHub (Jul 13, 2025).

✅ Have you read and understood the above guidelines?

yes

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

graylog

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

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

Running pve 8.4.1

Select the config file option for installation (item 4). The config file exists from a previous run. The script stops with the following error: ✖️ Password cannot be empty

Having the clear text root password in the configuration file is uncomfortable and probably a security violation.
Suggested resolution:

  1. remove the clear text password from the config file.
  2. query for the root password along with other items not in the config file (like the id).

Side note in addition to the above issue; If logged into a different node in the pve cluster, attempting to run this script from another target node crashes unpredictably. Success only when first logged into the pve host then run the script from its shell. (The pve ssh connection between hosts in the cluster cannot be used)

🔄 Steps to reproduce the issue.

Steps listed in description

❌ Paste the full error output (if available).

/ /____ ___ / /_ ____ _
/ / / / __ / / / / / __ \/ __ /
/ // / / / // / // / / // / // /
_// _,/_, //_/_, /
// /__/
💡 Using Config File on node lala100
💡 Using config File: /opt/community-scripts/graylog.conf
🆔 Container ID: 1100104
📦 Container Type: Unprivileged
✖️ Password cannot be empty

🖼️ Additional context (optional).

No response

Originally created by @tuxhobo on GitHub (Jul 13, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? graylog ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/graylog.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Running pve 8.4.1 Select the config file option for installation (item 4). The config file exists from a previous run. The script stops with the following error: ✖️ Password cannot be empty Having the clear text root password in the configuration file is uncomfortable and probably a security violation. Suggested resolution: 1. remove the clear text password from the config file. 2. query for the root password along with other items not in the config file (like the id). Side note in addition to the above issue; If logged into a different node in the pve cluster, attempting to run this script from another target node crashes unpredictably. Success only when first logged into the pve host then run the script from its shell. (The pve ssh connection between hosts in the cluster cannot be used) ### 🔄 Steps to reproduce the issue. Steps listed in description ### ❌ Paste the full error output (if available). ______ __ / ____/________ ___ __/ /___ ____ _ / / __/ ___/ __ `/ / / / / __ \/ __ `/ / /_/ / / / /_/ / /_/ / / /_/ / /_/ / \____/_/ \__,_/\__, /_/\____/\__, / /____/ /____/ 💡 Using Config File on node lala100 💡 Using config File: /opt/community-scripts/graylog.conf 🆔 Container ID: 1100104 📦 Container Type: Unprivileged ✖️ Password cannot be empty ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 00:06:52 +03:00
OVERLORD commented 2026-02-05 00:06:59 +03:00
Author
Owner
Copy Link

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

Config File is wrong. Reconfigure it. PASSWORD and CTID wrong.

@MickLesk commented on GitHub (Jul 13, 2025): Config File is wrong. Reconfigure it. PASSWORD and CTID wrong.
OVERLORD commented 2026-02-05 00:07:03 +03:00
Author
Owner
Copy Link

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

https://github.com/community-scripts/ProxmoxVE/discussions/1637#discussioncomment-13761117 & #5978

@MickLesk commented on GitHub (Jul 15, 2025): https://github.com/community-scripts/ProxmoxVE/discussions/1637#discussioncomment-13761117 & #5978
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#1270
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?