I have since update from 5 to 6 the problem, that the node-03 wants to send mails to node-01 .. instead of, what is configured on Postfix.
We manage the whole Postfix configuration with Puppet, so every node is identical ... except
myorigin = fra-corp-pmox-03.example.local
unser Firewall erzählt uns, dass alle Proxmox Instanzen mit 184.108.40.206 über HTTPS reden wollen, was scheinbar zu einem CDN (debian.map.fastlydns.net) gehört, oder gehörte. In der /etc/apt/ ist es nicht zu finden, da wir eigene Repos haben und auch Proxmox selbst hat für...
I tried it with one node and "ignored" the messages:
# ceph-volume simple activate --all
--> activating OSD specified in /etc/ceph/osd/0-c905557d-3619-4d8b-9da5-cff66fa6340d.json
Running command: /bin/ln -snf /dev/sdb2 /var/lib/ceph/osd/ceph-0/block
Running command: /bin/chown -R...
I have the exact same problem
# ceph-volume simple scan
stderr: lsblk: /var/lib/ceph/osd/ceph-5: not a block device
stderr: Bad argument "/var/lib/ceph/osd/ceph-5", expected an absolute path in /dev/ or /sys or a unit name: Invalid argument
Running command: /sbin/cryptsetup status...
hi @dcsapak ,
the question is: why not ? :) We can have for every node / backup a different passphrase, thanks to Puppet with Hiera + Eyaml. So it would be very nice, to make it possible, to submit a passphrase without stuff like expect.
Also ... maybe you don't want to use the master key ...
because I have no idea to solve it .. I used a workaround with expect:
# Workaround for input passphrase to proxmox-backup client
# Source: modules/profile/files/base
# Read the settings and passphrase
if [ -f...
is it possible to read the passphrase from a file or from STDIN ?
If I try:
echo secret | proxmox-backup-client key create
echo secet | proxmox-backup-client key create -
it fails with:
Error: unable to read passphrase - no tty
that is, what I thought ... but ... the output looks very strange to me :-) you have around 12 QR code blocks, surrounded by the lines from the key itself. It looks much different, than from the client encryption key. Maybe, the paperkey is not able to handle a key pair, but...
on the manual, I have the following:
but, is that "master" key the correct word, or is it the client encryption key. Because, it takes the file from ~/.config/proxmox-backup/encryption-key.json which is not the master key.
Ok, solved :)
root@fra-corp-srv-backup:[/mnt/datastore/store-01/vm/127]: ls -l
-rw-r--r-- 1 backup backup 0 May 12 06:08 owner
root@fra-corp-srv-backup:[/mnt/datastore/store-01/vm]: rm -Rf 127/
So I've deleted that folder ... and backup works now. The origin problem was, that the...
I have the same issue, on a single VM. All VMs can backuped, also on the same PVE ...
Task viewer: VM/CT 127 - Backup
INFO: starting new backup job: vzdump 127 --node fra-corp-pmox-03 --remove 0 --storage fra-corp-srv-backup --mode snapshot
INFO: Starting Backup of VM...
we use Tiger as audit tool on all our hosts. The strange thing, why I posting here is, that this problem occurs only on PVE6. We get the Tigercron mails with an emtpy Subject and to the "wrong" RCPTO.
The "Subject:" and the "From:" is in the body, instead of the headers. We have hosts...
I've enabled it a long time ago ( I think one version before it was supported), but it didn't changed anything. I hope it will help, to remove all the WD red disks.
As example for a SSD
ceph daemon osd.5 config show | grep allocator