Recent content by HuHu

Sorry, not now. I have a hunch it has something to do with the storage. I run my own Ceph cluster and it has some performance problems. Best regards CHristian

Hi all, nach dem Update auf die Version 5.3-1 wird kein Benutzer in der VM-Zuordnung (Rechte - Hinzufügen - Benutzer) angezeigt. In der Datei user.cfg sind ca. 450 Usereinträge. Hat einer eine Idee was hier Sache ist? Version: proxmox-ve: 5.3-1 (running kernel: 4.15.18-10-pve) pve-manager...

4x HP BL365 G6 ============ CPU: === Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 24 On-line CPU(s) list: 0-23 Thread(s) per core: 1 Core(s) per socket: 6 Socket(s): 4 NUMA node(s): 4...

Right now, I do not monitoring the PVE-Cluster. HW: 4x double HP Blade BL360 G6, CPU/Core/Ram (s. image above), 10 GB Net Storage: external Ceph-Cluster, 8 Nodes (nix of HP DL380 G4/G6/G8, HP BL360 G6+Storage-Blade), approximately 60 OSDs, 10GB public-/private Net VM-Config: follow tomorro...

Oh, nobody has the same problem?

Hear the version information. All nodes have the same software version. Are this the monitoring/metrics or what information do you exactly need?

Thanks sb-jw for your quick reply. I guess it's PVE 5.2. The error has existed for a longer time (1.5 year). Sorry, I'm not sitting in front of the machine. Tomorrow I can give the necessary details.

Hi all, I run a 4-node PVE-Cluster. Everything looks OK when I work alone with the system. If 20 or more students work with the system (KVM) then it comes again and again to the following error „broken pipe (599)“. The students connect there VMs with noVNC and/or Spice. What can I do to make...

Hi all, I have a well running python script to deploy KVM VMs with personal permissions and automatically naming. After a PVE update (3 or 4 months ago) I got this error message: raceback (most recent call last): File "/usr/local/bin/clone_template_linked.py", line 118, in <module>...

After a couple of tests I found a unclear situation in /usr/share/perl5/PVE/CephTools.pm line 240 dir_glob_foreach('/sys/block', '.*', sub { A check in /sys/block and I can't see any information about the /dev/xxx futurity OSD-device. So it is verry clear that pveceph createosd /dev/xxx...

Same situation here. I want to cerate a new OSD and select a hard drive (/dev/cciss!c0p2) a journal (/dev/cciss!c0d1) and finaly the following error message pop up: What is goning wrong? HW: HP Prolinat DL 385 G2 OS: Proxmox 3.2 proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)...