Search results

For some reason, it ends like 3h ago? ls -al /root/.bash* -rw------- 1 root root 11177 Aug 25 09:19 /root/.bash_history but you are on the right track, I'm on a weak connection and I have either copy / pasted something wrong or when reverse searching the bash history with CTRL+R selected...

btw. nvme0 and nvme1 are mirrored and this is where PVE runs. proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with uefi C284-A04D is configured with: uefi (versions: 5.4.119-1-pve, 5.4.124-1-pve, 5.4.128-1-pve)...

thx, I already suspected that but its not the case. I have 2 zfs pools. (I'm skipping a few irrelevant lines here) df -h Filesystem Size Used Avail Use% Mounted on udev...

any hints? I'm kinda stumped on how to fix this. I did an apt-get update followed by apt-get dist-upgrade which kept hanging so I pressed CTRL+C When running apt-get dist-upgrade again I got E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. but this...

nothing special. PX is on a VPS from a German provider, PBS is on a KVM from a US provider. tried mtr - no issues found. tried iperf3 between the two and TCP is ok, plenty of lost packets when using udp hence I switched back from using the wireguard VPN solution to plain simply connecting to the...

talking about ressources there is almost no noticable usage. I am analyzing both server's stats with netdata and I see no peak during the benchmarks. at all. they are idle. checked the logs and didn't find much on both. on the target (PBS) I see a few failed benchmarks which say "broken pipe"...

here you go

oh, I have news. The latest frozen benchmark just produced an error: proxmox-backup-client benchmark --repository root@pam@PBS-public-IP:datastore Message from syslogd@proxmox-host at May 26 16:33:46 ... kernel:[112192.699946] watchdog: BUG: soft lockup - CPU#1 stuck for 25s! [kvm:14958]...

Shall I pipe it to a log file and attach it here or what am I looking for? something like strace -f -yy proxmox-backup-client benchmark --repository root@pam@PBS-public-IP:datastore > logfile.log btw. I've just had 5-10 benchmarks working consecutively. I have no idea what is going on since...

thanks. Does this help? ps ax | grep proxmox-backup-client 30426 pts/2 Sl+ 0:00 proxmox-backup-client benchmark --repository root@pam@PBS-public-IP:datastore 30816 pts/3 S+ 0:00 grep proxmox-backup-client grep -r '' /proc/30426/task/*/stack /proc/30426/task/30426/stack:[<0>]...

hi there, 1 Proxmox server and 1 PBS with different providers. Both servers are up to date. Backups worked fine through tailscale (wireguard based VPN) then went from taking on average 10 minutes to 5-8 hours with similar backup sizes. Switched back to connecting to PBS via public IP, same...

What exactly do you mean by "on the same line"? Something like this? options zfs zfs_arc_min=4294967296 zfs_arc_max=8589934592

ah, I see, that seems to be the case, thanks for pointing it out. I guess eventually the old ones will be deleted. I was just wondering since auth.log seems to go back till the 3rd of February ls -al /var/log/proxmox-backup/api/ total 20205 drwxr-xr-x 2 backup backup 18 Apr 12 00:00 ...

that does not seem to be the case - this is a Debian 10 system with a manually installed PBS (not via the .iso) => https://pbs.proxmox.com/docs/installation.html#install-proxmox-backup-server-on-debian cat /var/lib/logrotate/status logrotate state -- version 2 "/var/log/syslog"...

The log directory seems to be getting out of hand so I was wondering if anyone could share his logrotate config? /var/log# du -cksh proxmox-backup/* 20M proxmox-backup/api 7.0M proxmox-backup/tasks 27M total

###edit### all this fiddling around didn't help. I will now delete all backups via PBS GUI, remove the storage from PVE and start from scratch.

ok, that was the problem. /etc/pve/priv/storage/STORAGEID.enc contains a fingerprint of the PBS /etc/pve/storage.cfg contains BOTH encyption-key AND fingerprint. Encryption-key is NOT as expected the STORAGEID but rather the fingerprint contained in the encryption-key. This is all very...

thanks. I already tried correcting the fingerprint in the .enc file but the PVE GUI still shows the old fingerprint as in my last screenshot I posted here so I'm wondering which service I could restart for the .enc file to be reread?

I don't need the encrypted backups. I had a look at the GUI, can you please specify how to generate a new key and replace the old one? I'n not 100% sure if this can be done via GUI as the help doesn't really explain these options: I guess i need to manually delete the old useless backups...

well, the error logs looks like this: ERROR: Backup job failed - upload log failed: Error: KeyConfig contains wrong fingerprint 90:ef:xx:xx:xx:xx:98:5b, contained key has fingerprint 9e:4f:xx:xx:xx:xx:4a:ef proxmox-backup-client key show ... results in showing me the fingerprint mentioned in...