starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #11908] PBS Post Install Scripts doesn't work because of `ifupdown2` upgrade #2502

New issue

Closed

opened 2026-02-26 12:52:39 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 12:52:39 +03:00

Owner

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

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

PBS Post Install

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/post-pbs-install.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.1.5

📝 Provide a clear and concise description of the issue.

On Proxmox Backup Server inside an privileged LXC container (Debian 13 / trixie), running the post-install script and then upgrading packages can make the PBS Web UI unavailable after reboot.

I think the main suspect is ifupdown2 upgrade:

from: 3.0.0-1.3
to: 3.3.0-1+pmx12

Container itself stays running, but UI is unreachable.

🔄 Steps to reproduce the issue.

Create fresh PBS Privileged LXC on trixie.
Run post-install script
Reboot container.
Check PBS UI.

❌ Paste the full error output (if available).

journal logs seems fine

root@pbs:/# journalctl -ru proxmox-backup.service
Feb 14 13:23:50 pbs systemd[1]: Stopped proxmox-backup.service - Proxmox Backup API Server.
Feb 14 13:23:50 pbs systemd[1]: proxmox-backup.service: Deactivated successfully.
Feb 14 13:23:50 pbs systemd[1]: Stopping proxmox-backup.service - Proxmox Backup API Server...
Feb 14 13:22:42 pbs login[5017]: ROOT LOGIN ON pts/3
Feb 14 13:22:41 pbs login[5017]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Feb 14 13:19:28 pbs proxmox-backup-api[4912]: authentication failure; rhost=[::ffff:192.168.2.12]:56870 user=root@pam msg=authentication error - AUTH_ERR (7)
Feb 14 13:19:26 pbs proxmox-backup-api[4912]: pam_unix(proxmox-backup-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:192.168.2.12  user=root
Feb 14 13:19:08 pbs systemd[1]: Started proxmox-backup.service - Proxmox Backup API Server.
Feb 14 13:19:08 pbs proxmox-backup-api[4912]: catching reload signal
Feb 14 13:19:08 pbs proxmox-backup-api[4912]: catching shutdown signal
Feb 14 13:19:07 pbs systemd[1]: Starting proxmox-backup.service - Proxmox Backup API Server...


root@pbs:/# journalctl -ru proxmox-backup-proxy.service
Feb 14 13:23:50 pbs systemd[1]: Stopped proxmox-backup-proxy.service - Proxmox Backup API Proxy Server.
Feb 14 13:23:50 pbs systemd[1]: proxmox-backup-proxy.service: Deactivated successfully.
Feb 14 13:23:50 pbs systemd[1]: Stopping proxmox-backup-proxy.service - Proxmox Backup API Proxy Server...
Feb 14 13:19:08 pbs systemd[1]: Started proxmox-backup-proxy.service - Proxmox Backup API Proxy Server.
Feb 14 13:19:08 pbs proxmox-backup-proxy[4923]: rrd journal successfully committed (0 files in 0.000 seconds)
Feb 14 13:19:08 pbs proxmox-backup-proxy[4923]: catching reload signal
Feb 14 13:19:08 pbs proxmox-backup-proxy[4923]: catching shutdown signal
Feb 14 13:19:08 pbs proxmox-backup-proxy[4923]: applied rrd journal (2 entries in 0.003 seconds)
Feb 14 13:19:08 pbs systemd[1]: Starting proxmox-backup-proxy.service - Proxmox Backup API Proxy Server...

🖼️ Additional context (optional).

I have fixed the problem my manually holding the upgrade of ifupdown2 by

apt-mark hold ifupdown2

Originally created by @ilkersigirci on GitHub (Feb 14, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11908 ### ✅ 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? PBS Post Install ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/post-pbs-install.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.1.5 ### 📝 Provide a clear and concise description of the issue. On Proxmox Backup Server inside an privileged LXC container (Debian 13 / trixie), running the post-install script and then upgrading packages can make the PBS Web UI unavailable after reboot. I think the main suspect is `ifupdown2` upgrade: - from: `3.0.0-1.3` - to: `3.3.0-1+pmx12` Container itself stays running, but UI is unreachable. ### 🔄 Steps to reproduce the issue. 1. Create fresh PBS Privileged LXC on trixie. 2. Run post-install script 3. Reboot container. 4. Check PBS UI. ### ❌ Paste the full error output (if available). journal logs seems fine ```bash root@pbs:/# journalctl -ru proxmox-backup.service Feb 14 13:23:50 pbs systemd[1]: Stopped proxmox-backup.service - Proxmox Backup API Server. Feb 14 13:23:50 pbs systemd[1]: proxmox-backup.service: Deactivated successfully. Feb 14 13:23:50 pbs systemd[1]: Stopping proxmox-backup.service - Proxmox Backup API Server... Feb 14 13:22:42 pbs login[5017]: ROOT LOGIN ON pts/3 Feb 14 13:22:41 pbs login[5017]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0) Feb 14 13:19:28 pbs proxmox-backup-api[4912]: authentication failure; rhost=[::ffff:192.168.2.12]:56870 user=root@pam msg=authentication error - AUTH_ERR (7) Feb 14 13:19:26 pbs proxmox-backup-api[4912]: pam_unix(proxmox-backup-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:192.168.2.12 user=root Feb 14 13:19:08 pbs systemd[1]: Started proxmox-backup.service - Proxmox Backup API Server. Feb 14 13:19:08 pbs proxmox-backup-api[4912]: catching reload signal Feb 14 13:19:08 pbs proxmox-backup-api[4912]: catching shutdown signal Feb 14 13:19:07 pbs systemd[1]: Starting proxmox-backup.service - Proxmox Backup API Server... root@pbs:/# journalctl -ru proxmox-backup-proxy.service Feb 14 13:23:50 pbs systemd[1]: Stopped proxmox-backup-proxy.service - Proxmox Backup API Proxy Server. Feb 14 13:23:50 pbs systemd[1]: proxmox-backup-proxy.service: Deactivated successfully. Feb 14 13:23:50 pbs systemd[1]: Stopping proxmox-backup-proxy.service - Proxmox Backup API Proxy Server... Feb 14 13:19:08 pbs systemd[1]: Started proxmox-backup-proxy.service - Proxmox Backup API Proxy Server. Feb 14 13:19:08 pbs proxmox-backup-proxy[4923]: rrd journal successfully committed (0 files in 0.000 seconds) Feb 14 13:19:08 pbs proxmox-backup-proxy[4923]: catching reload signal Feb 14 13:19:08 pbs proxmox-backup-proxy[4923]: catching shutdown signal Feb 14 13:19:08 pbs proxmox-backup-proxy[4923]: applied rrd journal (2 entries in 0.003 seconds) Feb 14 13:19:08 pbs systemd[1]: Starting proxmox-backup-proxy.service - Proxmox Backup API Proxy Server... ``` ### 🖼️ Additional context (optional). I have fixed the problem my manually holding the upgrade of `ifupdown2` by ```bash apt-mark hold ifupdown2 ```

kerem

2026-02-26 12:52:39 +03:00

closed this issue
added the
external
label

kerem commented

2026-02-26 12:52:39 +03:00

Author

Owner

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

https://bugzilla.proxmox.com/

Feel free to create an issue there. This has nothing to do with our script or the post-PBS.

@MickLesk commented on GitHub (Feb 14, 2026): > https://bugzilla.proxmox.com/ Feel free to create an issue there. This has nothing to do with our script or the post-PBS.

kerem referenced this issue

2026-02-26 13:34:40 +03:00

[PR #2502] [MERGED] New Script: Dolibarr #3795

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#2502

No description provided.

Rows
Columns

[GH-ISSUE #11908] PBS Post Install Scripts doesn't work because of ifupdown2 upgrade #2502

✅ Have you read and understood the above guidelines?

🔎 Did you run the script with verbose mode enabled?

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

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

⚙️ What settings are you using?

🖥️ Which Linux distribution are you using?

📈 Which Proxmox version are you on?

📝 Provide a clear and concise description of the issue.

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

[GH-ISSUE #11908] PBS Post Install Scripts doesn't work because of `ifupdown2` upgrade #2502