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

Changedetection.io: environment: line 67: SPINNER_PID: unbound variable #470

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

Originally created by @itsthejb on GitHub (Feb 10, 2025).

✅ Have you read and understood the above guidelines?

yes

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

changedetection

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/changedetection.sh)"

📝 Provide a clear and concise description of the issue.

Hi,

Cannot install using the current version of the script. Even with default settings it fails with:

environment: line 67: SPINNER_PID: unbound variable

Not seeing any other reports of this right now

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  • bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/changedetection.sh)"
  • Select default settings
  • Fails as above

❌ Paste the full error output (if available).

   ________                              ____       __            __  _           
  / ____/ /_  ____ _____  ____ ____     / __ \___  / /____  _____/ /_(_)___  ____ 
 / /   / __ \/ __ `/ __ \/ __ `/ _ \   / / / / _ \/ __/ _ \/ ___/ __/ / __ \/ __ \
/ /___/ / / / /_/ / / / / /_/ /  __/  / /_/ /  __/ /_/  __/ /__/ /_/ / /_/ / / / /
\____/_/ /_/\__,_/_/ /_/\__, /\___/  /_____/\___/\__/\___/\___/\__/_/\____/_/ /_/ 
                       /____/                                                     
  ⚙️  Using Default Settings on node proxmox
  🖥️  Operating System: debian
  🌟  Version: 12
  📦  Container Type: Unprivileged
  💾  Disk Size: 8 GB
  🧠  CPU Cores: 2
  🛠️  RAM Size: 1024 MiB
  🆔  Container ID: 122
  🚀  Creating a Change Detection LXC using the above default settings
  
environment: line 67: SPINNER_PID: unbound variable

🖼️ Additional context (optional).

No response

Originally created by @itsthejb on GitHub (Feb 10, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? changedetection ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/changedetection.sh)" ### 📝 Provide a clear and concise description of the issue. Hi, Cannot install using the current version of the script. Even with default settings it fails with: ``` environment: line 67: SPINNER_PID: unbound variable ``` Not seeing any other reports of this right now ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. - `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/changedetection.sh)"` - Select default settings - Fails as above ### ❌ Paste the full error output (if available). ``` ________ ____ __ __ _ / ____/ /_ ____ _____ ____ ____ / __ \___ / /____ _____/ /_(_)___ ____ / / / __ \/ __ `/ __ \/ __ `/ _ \ / / / / _ \/ __/ _ \/ ___/ __/ / __ \/ __ \ / /___/ / / / /_/ / / / / /_/ / __/ / /_/ / __/ /_/ __/ /__/ /_/ / /_/ / / / / \____/_/ /_/\__,_/_/ /_/\__, /\___/ /_____/\___/\__/\___/\___/\__/_/\____/_/ /_/ /____/ ⚙️ Using Default Settings on node proxmox 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 1024 MiB 🆔 Container ID: 122 🚀 Creating a Change Detection LXC using the above default settings environment: line 67: SPINNER_PID: unbound variable ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD commented 2026-02-04 19:06:32 +03:00
Author
Owner
Copy Link

@precariouspanther commented on GitHub (Feb 10, 2025):

Also seeing this with the gitea install script. Possible related: https://github.com/community-scripts/ProxmoxVE/pull/2203

@precariouspanther commented on GitHub (Feb 10, 2025): Also seeing this with the gitea install script. Possible related: https://github.com/community-scripts/ProxmoxVE/pull/2203
OVERLORD commented 2026-02-04 19:06:36 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 10, 2025):

@michelroegl-brunner

@MickLesk commented on GitHub (Feb 10, 2025): @michelroegl-brunner
OVERLORD commented 2026-02-04 19:06:39 +03:00
Author
Owner
Copy Link

@Theetjuh commented on GitHub (Feb 10, 2025):

Seeing the same issue when installing the PBS LXC

@Theetjuh commented on GitHub (Feb 10, 2025): Seeing the same issue when installing the PBS LXC
OVERLORD commented 2026-02-04 19:06:46 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 10, 2025):

reverted now. fix coming asap

@MickLesk commented on GitHub (Feb 10, 2025): reverted now. fix coming asap
OVERLORD commented 2026-02-04 19:06:56 +03:00
Author
Owner
Copy Link

@itsthejb commented on GitHub (Feb 10, 2025):

Great, thanks. I debugged a little more and found out it's actually related to having diagnostics enabled. If I set DIAGNOSTICS = no in /usr/local/community-scripts/diagnostics then everything works. Probably you already realise this

@itsthejb commented on GitHub (Feb 10, 2025): Great, thanks. I debugged a little more and found out it's actually related to having diagnostics enabled. If I set `DIAGNOSTICS = no` in `/usr/local/community-scripts/diagnostics` then everything works. Probably you already realise this
OVERLORD commented 2026-02-04 19:07:05 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Feb 11, 2025):

Great, thanks. I debugged a little more and found out it's actually related to having diagnostics enabled. If I set DIAGNOSTICS = no in /usr/local/community-scripts/diagnostics then everything works. Probably you already realise this

That has nothing to do with it. the call to the api comes long befor this error happend :)

@michelroegl-brunner commented on GitHub (Feb 11, 2025): > Great, thanks. I debugged a little more and found out it's actually related to having diagnostics enabled. If I set `DIAGNOSTICS > = no` in `/usr/local/community-scripts/diagnostics` then everything works. Probably you already realise this That has nothing to do with it. the call to the api comes long befor this error happend :)
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
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#470
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?