Search results

This actually confuses me now: Either apt-get update apt-get dist-upgrade or apt update apt full-upgrade Does anyone know the answer?

Great! I have a question about the upgrade. The upgrade guide recommends the apt dist-upgrade command. Until now, I thought that one used either apt full-upgrade or apt-get dist-upgrade. Which is correct, or does it not matter?

What about this workaround? Dark mode PBS https://github.com/Luckyvb/PBSDiscordDark Installation (as root) The installation is done via the CLI utility. Run the following commands on the PVE node serving the Web UI: wget...

Du kannst den thread auf [solved] stellen.

Beim Update des backup client wurde bei mir die vzdump.conf überschrieben. D. h. ich musste den Eintrag für die tmp-datei neu einfügen: nano /etc/vzdump.conf Dort einfügen: tmpdir: /tmp

Hi, I am running Proxmox Backup Server version 2.1-5. Currently I noticed that the systemd-timesyncd is not running. However, the daily updates are backed up without errors. Do I need to do something or can I leave it like this? Proxmox PVE uses chrony since version 7. Is it an alternative...

Last night, a Proxmox node left a cluster and was also no longer accessible via ssh. The following was kept in the log. Unfortunately, the quorum for the cluster was deemed ok and thus ha did not work. Only a hard reboot could fix the problem. Is there a solution to this and do I have to...

systemctl status pvesr.timer shows: thomas@pve:~$ sudo systemctl status pvesr.timer [sudo] Passwort für thomas: ● pvesr.timer - Proxmox VE replication runner Loaded: loaded (/etc/systemd/system/pvesr.timer; enabled; vendor preset: enabled) Active: active (waiting) since Thu 2021-06-10...

Hello, I am currently running a proxmox standalone system and have set the replication runner from minute to month to save the write load with systemctl edit --full pvesr.timer But now I would like to set up additional nodes for replication. How can I restart the replication runner every...

IMHO the gateway should be the same for all hots in this network segment (192.168.100.1).

Okay, got it. Thats how it works. 13 22 1 * * bash -c 'source /root/.bashrc; /usr/bin/proxmox-backup-client backup root.pxar:/ >/dev/null 2>&1' Thank you for pushing me in the right direction :) Best regards Thomas

I don't see any errors in syslog May 31 11:00:01 pve CRON[28406]: (root) CMD ("source /root/.bashrc; proxmox-backup-client backup root.pxar:/") May 31 11:00:01 pve CRON[28405]: pam_unix(cron:session): session closed for user root May 31 11:00:01 pve postfix/pickup[7380]: 7E05581B87: uid=0...

Sorry for my misunderstanding, i'm embarrassed. It is in the .bashrc of root, so i tried 13 22 1 * * "source /root/.bashrc; /usr/bin/proxmox-backup-client backup root.pxar:/ >/dev/null 2>&1" even the single quotes did not lead to success. 13 22 1 * * 'export...

It seems, i have a syntax problem. None of the following examples leads to a backup: 13 22 1 * * "source ~/.bashrc; /usr/bin/proxmox-backup-client backup root.pxar:/ >/dev/null 2>&1" 13 22 1 * * "export PBSREPOSITORY="user@pbs@192.xxx.xxx.xxx:datastore"; export PBSPASSWORD="xxxx"...

Ich möchte einmal im Monat ein terminiertes Backup des Proxmox pve vermittels des Proxmox Backup Client durchführen. Hierzu habe ich als root auf dem Proxmox pve via crontab -e diesen Eintrag für das Backup an jedem ersten des Monats um 22:13 Uhr eingefügt: 13 22 1 * * proxmox-backup-client...

Ok, - again - thanks a lot ;) . This made it. Indeed, a warning would be nice.

Unfortunately i put the new fingerprint in there and the datastore is connectet. The issue occurs with the new fingerprint. As i wrote, the pbs could be reached but the backup of root.pxar is not possible.

I had to renew a proxmox backup server running in one proxmox lxc. I used the exact ip as used before and backups of lxc and vm work fine. If i try to backup the pve node comes a certificate error. It seems, the pve expects the certificate of the old pbs and runs in an error. How can i fix...

I instantly updated the client on proxmox backup server and also on the pve host. All works fine: recovering backed-up configuration from 'pbsbackp:backup/ct/300/2021-04-06T06:39:32Z' Logical volume "vm-301-disk-0" created. Creating filesystem with 2097152 4k blocks and 524288 inodes...

Fine @fabian, because this bug was very annoying in the last few days and my hair began to turn grey ;).