Search results

hi, because I have no idea to solve it .. I used a workaround with expect: #!/bin/bash # Workaround for input passphrase to proxmox-backup client # Source: modules/profile/files/base # Read the settings and passphrase source /root/.config/proxmox-backup/secrets if [ -f...

hi, is it possible to read the passphrase from a file or from STDIN ? If I try: echo secret | proxmox-backup-client key create or echo secet | proxmox-backup-client key create - it fails with: Error: unable to read passphrase - no tty cu denny

Hi @dcsapak 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...

hi, 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. cu denny

Ok, solved :) root@fra-corp-srv-backup:[/mnt/datastore/store-01/vm/127]: ls -l total 0 -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...

hi, I have the same issue, on a single VM. All VMs can backuped, also on the same PVE ... Task viewer: VM/CT 127 - Backup OutputStatus Stop 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...

Hello, writing this post was great, I think :-) I saw, that the useragent is "s-nail" and I replaced it with the default bsd-mailx. I'm pretty sure, that this will solve our problems. cu denny

Hello, 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...

hi, 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 "bluefs_allocator": "bitmap"...

hi, because my Icinga2 sends a notification: also with 5.4-13 and Ceph 12.2.12-pve1 this problem still exists. I have to reboot (I dislike to just restart the OSD's) after a few weeks. cu denny

hi, I have to check it next week :-)

hi, nope. No new news. Also with 12.2.12 I have to reboot the nodes after a few weeks.

Hi, jupp, we have two datacenter and I rebooted them all, after setting this option: We try today: [osd] ... bluestore_allocator = bitmap bluefs_allocator = bitmap

hi, I have the very same problem, but over the time. I had set the osd_memory_target, but over a month it takes more memory: From my ceph-user mailinglist: The thread starts here: http://lists.ceph.com/pipermail/ceph-users-ceph.com/2019-May/034530.html Its getting very annoying :-) I'm...

hi, # pveversion -v proxmox-ve: 5.4-1 (running kernel: 4.15.18-12-pve) pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62) pve-kernel-4.15: 5.3-3 pve-kernel-4.15.18-12-pve: 4.15.18-35 pve-kernel-4.15.18-11-pve: 4.15.18-34 pve-kernel-4.15.18-10-pve: 4.15.18-32 pve-kernel-4.15.18-9-pve...

hi, I have a cluster with and I have a container, which does not start on a 5.4. node: lxc-start: 133: conf.c: lxc_mount_rootfs: 1343 Failed to mount rootfs "/var/lib/lxc/133/rootfs" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs" with options "(null)" On a host with PVE 5.3 the same container...

hi, correct ... we have to wait, until it happens again. Thx

Hi, that we tought too, but also ... there was nothing in the logs. A normal shutdown would be send data to syslog or our sidecar agent (Graylog). It looks like more than a "qm stop <id>", but needless to say .. there was no qm command also in our snoopy.log.

hi, nope. Nothing.

hi, we had a very strange issue. A VM just disapears / stopped and the only thing we found, in kern.log "vmbr101: port2(tap104i0) entered disabled state" Nothing more, either in the remote syslog, nor in the local log files from the PVE 5.2-5 or in the VM itself. The VM itself is the 2nd...