SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-18 06:02:30 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Zipline v4.1.0 script indefinite PostgreSQL failure and fails to complete install #1232

New Issue
Open
opened 2025-11-20 05:06:42 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:06:42 -05:00
Owner
Copy Link

Originally created by @flinthamm on GitHub (Jun 5, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Zipline

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

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

In Proxmox v8.3.1 I've tried multiple times starting with the default script settings and then advanced, advanced verbose and no matter what this script fails to complete the installation of PostgreSQL when it tries to upgrade to version 16 and I think then 17 in "Cluster" mode. If we stick to the default settings it will go through the script, update the container display the "Installed Dependencies" and "Installed "Node.js 22" but will then hang indefinitely (still running after 10 minutes) at the "Installing PostgreSQL 16 repository upgrade to 16..." see below:

See "Error Output" below.

There was a similar issue raised but seems to be unrelated to PostgreSQL as issue #3283.

🔄 Steps to reproduce the issue.

Just run the zipline install script

❌ Paste the full error output (if available).

/__  /  (_)___  / (_)___  ___ 
  / /  / / __ \/ / / __ \/ _ \
 / /__/ / /_/ / / / / / /  __/
/____/_/ .___/_/_/_/ /_/\___/ 
      /_/                     
  ⚙️  Using Default Settings on node proxmox1
  🖥️  Operating System: debian
  🌟  Version: 12
  📦  Container Type: Unprivileged
  💾  Disk Size: 5 GB
  🧠  CPU Cores: 2
  🛠️  RAM Size: 2048 MiB
  🆔  Container ID: 130
  🚀  Creating a Zipline LXC using the above default settings
  
  ✔️  Using local for Template Storage.
  ✔️  Using local-lvm for Container Storage.
  ✔️  Updated LXC Template List
  ✔️  LXC Template is ready to use.
  ✔️  LXC Container 130 was successfully created.
  ✔️   Started LXC Container
  ✔️  Set up Container OS
  ✔️  Network Connected: 192.168.8.159 
  ✔️  IPv4 Internet Connected
  ✖️  IPv6 Internet Not Connected
  ✔️  DNS Resolved github.com to 20.26.156.215
  ✔️  Updated Container OS
  ✔️  Core dependencies installed
  ✔️  Installed Dependencies
  ✔️  Installed Node.js 22
  ✔️  All requested Node modules have been processed
 ⠴   Installing PostgreSQL 16 pository  pgrade to 16    Dumping all PostgreSQL data from version 15

🖼️ Additional context (optional).

In advanced verbose mode I've tried to progress the script by answering the prompts regarding the PostgreSQL cluster upgrade with "No" but the script then errors out.

Originally created by @flinthamm on GitHub (Jun 5, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Zipline ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zipline.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. In Proxmox v8.3.1 I've tried multiple times starting with the default script settings and then advanced, advanced verbose and no matter what this script fails to complete the installation of PostgreSQL when it tries to upgrade to version 16 and I think then 17 in "Cluster" mode. If we stick to the default settings it will go through the script, update the container display the "Installed Dependencies" and "Installed "Node.js 22" but will then hang indefinitely (still running after 10 minutes) at the "Installing PostgreSQL 16 repository upgrade to 16..." see below: See "Error Output" below. There was a similar issue raised but seems to be unrelated to PostgreSQL as issue #3283. ### 🔄 Steps to reproduce the issue. Just run the zipline install script ### ❌ Paste the full error output (if available). ``` /__ / (_)___ / (_)___ ___ / / / / __ \/ / / __ \/ _ \ / /__/ / /_/ / / / / / / __/ /____/_/ .___/_/_/_/ /_/\___/ /_/ ⚙️ Using Default Settings on node proxmox1 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 5 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🆔 Container ID: 130 🚀 Creating a Zipline LXC using the above default settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 130 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.8.159 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ DNS Resolved github.com to 20.26.156.215 ✔️ Updated Container OS ✔️ Core dependencies installed ✔️ Installed Dependencies ✔️ Installed Node.js 22 ✔️ All requested Node modules have been processed ⠴ Installing PostgreSQL 16 pository pgrade to 16 Dumping all PostgreSQL data from version 15 ``` ### 🖼️ Additional context (optional). In advanced verbose mode I've tried to progress the script by answering the prompts regarding the PostgreSQL cluster upgrade with "No" but the script then errors out.
saavagebueno added the bug label 2025-11-20 05:06:42 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1232
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?