Recent content by MarcelW

Hi, ich habe heute alle aktuellen Updates eingespielt, Reboot lief ohne Probleme, danke!

Auch, ja.

Hi, ja es war mal zum testen eingeschaltet, das ist aber schon ein bisschen her. pveversion: proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve) pve-manager: 6.1-5 (running version: 6.1-5/9bf06119) pve-kernel-5.3: 6.1-1 pve-kernel-helper: 6.1-1 pve-kernel-5.3.13-1-pve: 5.3.13-1...

Hallo zusammen, ich habe aktuell einen Cluster aus drei baugleichen Nodes. Bei zwei Nodes habe ich das Problem, dass wenn ich diese rebooten möchte ich ewig folgendes auf der Konsole ablesen kann: A stop job is running for PVE Local HA Resource Manager Daemon Aktuell läuft das ganze schon ca. 7...

Anyone got a solution for me?

pve-n1: (the good one) root@pve-n1:~# pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve) pve-manager: 6.1-5 (running version: 6.1-5/9bf06119) pve-kernel-5.3: 6.1-1 pve-kernel-helper: 6.1-1 pve-kernel-5.0: 6.0-11 pve-kernel-5.3.13-1-pve: 5.3.13-1 pve-kernel-5.3.10-1-pve: 5.3.10-1...

Okay, i have a external rbd storage that is causing the problems. BUT: on pve-n1 (node 1) i have the "old" ceph version running: ceph-common/stable,now 12.2.11+dfsg1-2.1+b1 amd64 [installed] ceph-fuse/stable,now 12.2.11+dfsg1-2.1+b1 amd64 [installed] libcephfs2/stable,now 12.2.11+dfsg1-2.1+b1...

Hello tim, i have the same problem but i haven't any NFS shares or something. The "pvestatd got timeout" message only appears on one node - other nodes are not affected. Log: Dec 25 01:10:08 pve-n2 pvestatd[14119]: got timeout Dec 25 01:10:08 pve-n2 pvestatd[14119]: status update time (5.074...

yes i did a pveceph install and migrated my machines to the node with the new library. this is the log output from the backup task last night: backup log How can i perform a rados bench on external storage? What should i ask them?

Hi everybody, i installed pveceph and these are the results for a single backup: INFO: starting new backup job: vzdump 105 --remove 0 --mode snapshot --storage storage01-backup --compress lzo --node pve-n2 INFO: Starting Backup of VM 105 (qemu) INFO: Backup started at 2019-12-03 10:44:16 INFO...

what does this mean with the sparse? all vms are recently restarted (migration, etc.)

Hi, i think this doesnt matter or? I dont use ceph on my proxmox nodes. I have rent some ceph space from my datacenter provider.

root@pve-n1:~# pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.21-5-pve) pve-manager: 6.0-15 (running version: 6.0-15/52b91481) pve-kernel-helper: 6.0-12 pve-kernel-5.0: 6.0-11 pve-kernel-5.0.21-5-pve: 5.0.21-10 pve-kernel-5.0.21-4-pve: 5.0.21-9 pve-kernel-5.0.21-3-pve: 5.0.21-7...

@tom do you have any idea on this?

i dont know why but now its the same as before: INFO: status: 40% (107453874176/268435456000), sparse 0% (1327009792), duration 3341, read/write 18/18 MB/s INFO: status: 41% (110167588864/268435456000), sparse 0% (1346469888), duration 3410, read/write 39/39 MB/s INFO: status: 42%...