[SOLVED] Failed to start Proxmox Backup API Proxy Server

W

werter

Well-Known Member
Dec 10, 2017
91
9
48
Hi.
Can't run PBS on the same host with latest PVE
Please help.

root@pve-01:~# systemctl status proxmox-backup-proxy.service
* proxmox-backup-proxy.service - Proxmox Backup API Proxy Server
Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-11-09 16:18:03 MSK; 2min 37s ago
Process: 30955 ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy (code=exited, status=1/FAILURE)
Main PID: 30955 (code=exited, status=1/FAILURE)
CPU: 14ms

Nov 09 16:18:03 pve-01 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 09 16:18:03 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 09 16:18:03 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 09 16:18:05 pve-01 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 09 16:18:05 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 09 16:18:05 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.

root@pve-01:~# cat /lib/systemd/system/proxmox-backup.service
[Unit]
Description=Proxmox Backup API Server
Wants=network-online.target
After=network.target

[Service]
Type=notify
ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api
ExecReload=/bin/kill -HUP $MAINPID
PIDFile=/run/proxmox-backup/api.pid
Restart=on-failure

[Install]
WantedBy=multi-user.target


root@pve-01:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-7-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-4
pve-kernel-5.11: 7.0-10
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 16.2.6-pve2
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.4-2~bpo11+1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-12
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-13
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
openvswitch-switch: 2.15.0+ds1-8~bpo11+1
proxmox-backup-client: 2.0.13-1
proxmox-backup-file-restore: 2.0.13-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve1

root@pve-01:~# proxmox-backup-manager versions --verbose
proxmox-backup unknown running kernel: 5.11.22-7-pve
proxmox-backup-server 2.0.13-1 running version: 2.0.13
pve-kernel-helper 7.1-4
pve-kernel-5.11 7.0-10
pve-kernel-5.11.22-7-pve 5.11.22-12
pve-kernel-5.11.22-5-pve 5.11.22-10
pve-kernel-5.11.22-4-pve 5.11.22-9
ifupdown2 3.1.0-1+pmx3
libjs-extjs 7.0.0-1
proxmox-backup-docs 2.0.13-1
proxmox-backup-client 2.0.13-1
proxmox-mini-journalreader 1.2-1
proxmox-widget-toolkit 3.3-6
pve-xtermjs 4.12.0-1
smartmontools 7.2-1
zfsutils-linux 2.1.1-pve1
 
Last edited:
please check the log for the first failed start (e.g., with journalctl -b -u proxmox-backup-proxy). in case that indicates some past problem, systemctl reset-failed proxmox-backup-proxy followed by systemctl restart proxmox-backup-proxy should properly restart it. if not, please post the full journal output for that unit...
 
fabian said:
please check the log for the first failed start (e.g., with journalctl -b -u proxmox-backup-proxy). in case that indicates some past problem, systemctl reset-failed proxmox-backup-proxy followed by systemctl restart proxmox-backup-proxy should properly restart it. if not, please post the full journal output for that unit...
Click to expand...

Thx for your answer.

root@pve-01:~# journalctl -b -u proxmox-backup-proxy
-- Journal begins at Fri 2021-10-29 12:05:01 MSK, ends at Wed 2021-11-10 10:01:38 MSK. --
Nov 10 09:56:10 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 09:56:10 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 09:56:11 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 09:56:11 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 09:56:11 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 09:56:11 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 09:56:11 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.

systemctl reset-failed proxmox-backup-proxy
root@pve-01:~# systemctl restart proxmox-backup-proxy
Job for proxmox-backup-proxy.service failed because the control process exited with error code.
See "systemctl status proxmox-backup-proxy.service" and "journalctl -xe" for details.

root@pve-01:~# systemctl status proxmox-backup-proxy.service
* proxmox-backup-proxy.service - Proxmox Backup API Proxy Server
Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-11-10 10:04:14 MSK; 38s ago
Process: 5813 ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy (code=exited, status=1/FAILURE)
Main PID: 5813 (code=exited, status=1/FAILURE)
CPU: 15ms

Nov 10 10:04:14 pve-01 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 10 10:04:14 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:04:14 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.

root@pve-01:~# journalctl -xe
-- Subject: A start job for unit proxmox-backup-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit proxmox-backup-proxy.service has finished with a failure.
--
-- The job identifier is 2465 and the job result is failed.
Nov 10 10:04:14 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit proxmox-backup-proxy.service has entered the 'failed' state with result 'exit-code'.
Nov 10 10:04:14 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
-- Subject: A start job for unit proxmox-backup-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit proxmox-backup-proxy.service has finished with a failure.
--
-- The job identifier is 2537 and the job result is failed.
Nov 10 10:04:14 pve-01 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 10 10:04:14 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit proxmox-backup-proxy.service has entered the 'failed' state with result 'exit-code'.
Nov 10 10:04:14 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
-- Subject: A start job for unit proxmox-backup-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit proxmox-backup-proxy.service has finished with a failure.
--
-- The job identifier is 2609 and the job result is failed.

The same :(

Try to run line from /lib/systemd/system/proxmox-backup-proxy.service (ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy).
root@pve-01:~# /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy
Error: proxy not running as backup user or group (got uid 0 gid 0)

root@pve-01:~# id backup
uid=34(backup) gid=34(backup) groups=34(backup),26(tape)

Guys, what's wrong? LATEST PVE with the LATEST PBS - and this (
 
Last edited:
root@pve-01:~# proxmox-backup-manager versions --verbose
proxmox-backup unknown running kernel: 5.11.22-7-pve
proxmox-backup-server 2.0.13-1 running version: 2.0.13
pve-kernel-helper 7.1-4
pve-kernel-5.11 7.0-10
pve-kernel-5.11.22-7-pve 5.11.22-12
pve-kernel-5.11.22-5-pve 5.11.22-10
pve-kernel-5.11.22-4-pve 5.11.22-9
ifupdown2 3.1.0-1+pmx3
libjs-extjs 7.0.0-1
proxmox-backup-docs 2.0.13-1
proxmox-backup-client 2.0.13-1
proxmox-mini-journalreader 1.2-1
proxmox-widget-toolkit 3.3-6
pve-xtermjs 4.12.0-1
smartmontools 7.2-1
zfsutils-linux 2.1.1-pve1

Why proxmox-backup has unknown version ?
 
Last edited:
root@pve-01:~# apt search proxmox-backup
Sorting... Done
Full Text Search... Done
libproxmox-backup-qemu0/stable,now 1.2.0-1 amd64 [installed]
Proxmox Backup Server client library for QEMU

libproxmox-backup-qemu0-dbgsym/stable 1.2.0-1 amd64
debug symbols for libproxmox-backup-qemu0

libproxmox-backup-qemu0-dev/stable 1.2.0-1 amd64
Proxmox Backup Server client library for QEMU development files

proxmox-backup/stable 2.0-1 all
Proxmox Backup Server metapackage
...

Make apt install -y proxmox-backup. Why this pkg don't automaticalliy installed with proxmox-backup-server pkg ?
Reboot.
But the same again (

root@pve-01:~# systemctl reset-failed proxmox-backup-proxy

root@pve-01:~# systemctl restart proxmox-backup-proxy.service
Job for proxmox-backup-proxy.service failed because the control process exited with error code.
See "systemctl status proxmox-backup-proxy.service" and "journalctl -xe" for details.

root@pve-01:~# systemctl status proxmox-backup-proxy.service
* proxmox-backup-proxy.service - Proxmox Backup API Proxy Server
Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-11-10 10:34:19 MSK; 46s ago
Process: 4005 ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy (code=exited, status=1/FAILURE)
Main PID: 4005 (code=exited, status=1/FAILURE)
CPU: 13ms

Nov 10 10:34:19 pve-01 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 10 10:34:19 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:34:19 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.

root@pve-01:~# journalctl -xe
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit proxmox-backup-proxy.service has finished with a failure.
--
-- The job identifier is 2448 and the job result is failed.
Nov 10 10:34:19 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit proxmox-backup-proxy.service has entered the 'failed' state with result 'exit-code'.
Nov 10 10:34:19 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
-- Subject: A start job for unit proxmox-backup-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit proxmox-backup-proxy.service has finished with a failure.
--
-- The job identifier is 2520 and the job result is failed.
Nov 10 10:34:19 pve-01 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 10 10:34:19 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit proxmox-backup-proxy.service has entered the 'failed' state with result 'exit-code'.
Nov 10 10:34:19 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
-- Subject: A start job for unit proxmox-backup-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit proxmox-backup-proxy.service has finished with a failure.
--
-- The job identifier is 2592 and the job result is failed.
 
Try to reinstall PVE globally.
But :(

...
Created symlink /etc/systemd/system/getty.target.wants/proxmox-backup-banner.service -> /lib/systemd/system/proxmox-backup-banner.service.
Created symlink /etc/systemd/system/multi-user.target.wants/proxmox-backup-proxy.service -> /lib/systemd/system/proxmox-backup-proxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/proxmox-backup.service -> /lib/systemd/system/proxmox-backup.service.
Job for proxmox-backup-proxy.service failed because the control process exited with error code.
See "systemctl status proxmox-backup-proxy.service" and "journalctl -xe" for details.
...
 
the proxmox-backup package is just a meta package pulling in proxmox-backup-server and the kernel packages and so on. it's not strictly needed (when running in a container, just proxmox-backup-server is enough).

you need to get the log from the unit initially failing instead of when it fails because it already failed too often too quickly ;)

run in one shell, keep running until the other shell's commands are done, then Ctrl+C and copy output here:
Code: 
journalctl -f

run in another shell

Code: 
systemctl reset-failed proxmox-backup-proxy
systemctl restart proxmox-backup-proxy
 
root@pve-01:~# journalctl -f
-- Journal begins at Fri 2021-10-29 12:05:01 MSK. --
Nov 10 10:49:06 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:49:07 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:49:07 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:49:07 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:49:07 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:49:07 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:49:07 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:49:07 pve-01 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 10 10:49:07 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:49:07 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:50:22 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:50:22 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:50:22 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:50:22 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:50:22 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:50:22 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:50:23 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:50:23 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:50:23 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:50:23 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 10 10:50:23 pve-01 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 10 10:50:23 pve-01 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 10 10:50:23 pve-01 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
^C
 
root@pve-01:~# cat /lib/systemd/system/proxmox-backup-proxy.service
[Unit]
Description=Proxmox Backup API Proxy Server
Wants=network-online.target
After=network.target
Wants=proxmox-backup.service
After=proxmox-backup.service

[Service]
Type=notify
ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy
ExecReload=/bin/kill -HUP $MAINPID
PIDFile=/run/proxmox-backup/proxy.pid
Restart=on-failure
User=backup
Group=backup

[Install]
WantedBy=multi-user.target

root@pve-01:~# ls -ahl /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy
-rwxr-xr-x 1 root root 20M Oct 21 09:17 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy

Is it right?

root@pve-01:~# systemctl status proxmox-backup
* proxmox-backup.service - Proxmox Backup API Server
Loaded: loaded (/lib/systemd/system/proxmox-backup.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-11-10 10:42:33 MSK; 14min ago
Main PID: 7594 (proxmox-backup-)
Tasks: 5 (limit: 18997)
Memory: 7.3M
CPU: 1.318s
CGroup: /system.slice/proxmox-backup.service
`-7594 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api
 
Last edited:
yeah, that looks okay. can you try running it manually in the foreground?

Code: 
systemctl stop proxmox-backup-proxy
runuser -u backup -g backup /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy
 
root@pve-01:~# systemctl stop proxmox-backup-proxy
root@pve-01:~# runuser -u backup -g backup /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy
Error: unable to create rrdb stat dir - EACCES: Permission denied
 
Last edited:
Solved:

https://forum.proxmox.com/threads/e...-clean-pbs-v2-installation.99395/#post-429098
mkdir -vp /var/lib/proxmox-backup/rrdb
chown -Rv backup:backup /var/lib/proxmox-backup/rrdb
systemctl reset-failed proxmox-backup-proxy
systemctl restart proxmox-backup-proxy

root@pve-01:~# systemctl status proxmox-backup-proxy
* proxmox-backup-proxy.service - Proxmox Backup API Proxy Server
Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-11-10 11:11:51 MSK; 2s ago
Main PID: 14004 (proxmox-backup-)
Tasks: 6 (limit: 18997)
Memory: 4.5M
CPU: 21ms
CGroup: /system.slice/proxmox-backup-proxy.service
`-14004 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy


Fix this problem in the next release, please.
And thx for your job, guys :)
 
Last edited:
Having the same issue installing PBS on same PVE server


Nov 28 16:40:45 ba1 systemd[1]: Starting Proxmox Backup API Proxy Server...
Nov 28 16:40:45 ba1 proxmox-backup-proxy[8638]: apply old journal log rrd.journal-6384726f
Nov 28 16:40:45 ba1 proxmox-backup-proxy[8638]: Error: Address family not supported by protocol (os error 97)
Nov 28 16:40:45 ba1 systemd[1]: proxmox-backup-proxy.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 16:40:45 ba1 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 28 16:40:45 ba1 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 28 16:40:45 ba1 systemd[1]: proxmox-backup-proxy.service: Scheduled restart job, restart counter is at 1.
Nov 28 16:40:45 ba1 systemd[1]: Stopped Proxmox Backup API Proxy Server.
Nov 28 16:40:45 ba1 systemd[1]: Starting Proxmox Backup API Proxy Server...
Nov 28 16:40:45 ba1 proxmox-backup-proxy[8709]: apply old journal log rrd.journal-6384726f
Nov 28 16:40:45 ba1 proxmox-backup-proxy[8709]: Error: Address family not supported by protocol (os error 97)
Nov 28 16:40:45 ba1 systemd[1]: proxmox-backup-proxy.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 16:40:45 ba1 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 28 16:40:45 ba1 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 28 16:40:45 ba1 systemd[1]: proxmox-backup-proxy.service: Scheduled restart job, restart counter is at 2.
Nov 28 16:40:45 ba1 systemd[1]: Stopped Proxmox Backup API Proxy Server.
Nov 28 16:40:46 ba1 systemd[1]: Starting Proxmox Backup API Proxy Server...
Nov 28 16:40:46 ba1 proxmox-backup-proxy[8778]: apply old journal log rrd.journal-6384726f
Nov 28 16:40:46 ba1 proxmox-backup-proxy[8778]: Error: Address family not supported by protocol (os error 97)
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 28 16:40:46 ba1 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Scheduled restart job, restart counter is at 3.
Nov 28 16:40:46 ba1 systemd[1]: Stopped Proxmox Backup API Proxy Server.
Nov 28 16:40:46 ba1 systemd[1]: Starting Proxmox Backup API Proxy Server...
Nov 28 16:40:46 ba1 proxmox-backup-proxy[8847]: apply old journal log rrd.journal-6384726f
Nov 28 16:40:46 ba1 proxmox-backup-proxy[8847]: Error: Address family not supported by protocol (os error 97)
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 28 16:40:46 ba1 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Scheduled restart job, restart counter is at 4.
Nov 28 16:40:46 ba1 systemd[1]: Stopped Proxmox Backup API Proxy Server.
Nov 28 16:40:46 ba1 systemd[1]: Starting Proxmox Backup API Proxy Server...
Nov 28 16:40:46 ba1 proxmox-backup-proxy[8923]: apply old journal log rrd.journal-6384726f
Nov 28 16:40:46 ba1 proxmox-backup-proxy[8923]: Error: Address family not supported by protocol (os error 97)
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 28 16:40:46 ba1 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 28 16:40:46 ba1 pve-firewall[2236]: status update error: iptables_restore_cmdlist: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Scheduled restart job, restart counter is at 5.
Nov 28 16:40:46 ba1 systemd[1]: Stopped Proxmox Backup API Proxy Server.
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Nov 28 16:40:46 ba1 systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Nov 28 16:40:46 ba1 systemd[1]: Failed to start Proxmox Backup API Proxy Server.
Nov 28 16:40:56 ba1 pve-firewall[2236]: status update error: iptables_restore_cmdlist: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
 
that looks like a different error (but also on causing a failing start). did you manually disable ipv6 somehow?
 
can reproduce the issue - PBS currently tries to bind to "::" which doesn't work if IPv6 is disabled entirely. as a workaround, you could just disable assigning ipv6 addresses, instead of disabling the full ipv6 stack:

ipv6.disable_ipv6=1

should do the trick.
 
  • Like
Reactions: _gabriel
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom