Search results

Hello, Please check: https://security-tracker.debian.org/tracker/CVE-2021-29657

Crush rules was created with commands: ceph osd crush rule create-replicated ssd-pool-rule default osd ssd ceph osd crush rule create-replicated hdd-pool-rule default osd hdd

Here is current tree from crushmap: # ceph osd crush tree --show-shadow ID CLASS WEIGHT TYPE NAME -12 ssd 10.47583 root default~ssd -9 ssd 2.61896 host cloud1~ssd 3 ssd 0.87299 osd.3 4 ssd 0.87299 osd.4 5 ssd 0.87299...

Guys could you please briefly look if steps I've mentioned are correct?

As I correctly understood, next steps should be taken: 1. ceph osd getcrushmap -o /tmp/mycrushmap 2. crushtool -d /tmp/mycrushmap > /tmp/mycrushmap.txt 3. Change ssd-pool-rule and hdd-pool-rule with (step chooseleaf firstn 0 type host): rule ssd-pool-rule { id 1 type replicated...

Hello, Could you please advice on how to safely change the replica's to be on different hosts, instead of OSDs for next crush map (PVE 6.2): # begin crush map tunable choose_local_tries 0 tunable choose_local_fallback_tries 0 tunable choose_total_tries 50 tunable chooseleaf_descend_once 1...

How I can check that distribution goes to different nodes, not to OSDs?

I will check

Hello, On some servers in cloud I see this error, while trying to check cephfs - content: mount error: exit code 16 (500) I have next package versions:

Try to run command inside terminal multiplexer such as tmux.

Hello, I'd wish to understand if anyone here running production-grade Kubernates on proxmox (either in KVM or in LXC). I found many articles on web, but most of them are about test or small k8s small or test clusters. As far as I understood (please correct me if I wrong - Kubernetes needs some...

@iT!T please, mark as SOLVED :)

No-matter what, but something should be enable by default, to sync time :)

Meet time sync problem with PVE 5.4 strange, that ntp time sync not enabled by default.

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 ceph: 12.2.11-pve1 corosync: 2.4.4-pve1 criu: 2.11.1-1~bpo90 glusterfs-client: 3.8.8-1 ksm-control-daemon: 1.2-2 libjs-extjs...

Hello, While editing server notes on clean install and trying to save note, I always get error: unable to open file '/etc/pve/nodes/cloud1/config.tmp.1652' - Permission denied (500)

https://bugzilla.proxmox.com/show_bug.cgi?id=2183

Seems, like it blinks only in case at least 1 node from cluster is in down state.

Hello, Just FYI - I recorded small screencast of proxmox subscription status blinking, looks very strange :)

Can you please also try with Gzip?