Recent content by jmpfas

ok - the nic labeled cluster is the proxmox cluster, not optional ceph cluster. Right now it is on 10G but moving to 100G once I am 100% sure I have the 100G working properly. later today adding cross connect cables between the two 100G switches and will try LAG group for CEPH. well, first just...

ok - the nic labeled cluster is the proxmox cluster, not optional ceph cluster. Right now it is on 10G but moving to 100G once I am 100% sure I have the 100G working properly. later today adding cross connect cables between the two 100G switches and will try LAG group for CEPH. well, first just...

Hmm. I will try that (already was planning on moving cluster to 100G), but the docs say the ceph interface handles both replication and RADOS and talks about moving replication to a different network for performance. If what you said is correct, the docs are wrong. But I will try that

well, increasing num_PGs to 4096 helped. but not enough now getting WRITE: bw=6598MiB/s (6918MB/s), 217MiB/s-708MiB/s (228MB/s-743MB/s), io=476GiB (511GB), run=73787-73845msec Disk stats (read/write): dm-0: ios=0/33834, merge=0/0, ticks=0/12202032, in_queue=12202030, util=99.77%...

may have found it. based on install manual I had left num_pgs=auto, which resulted in 48 PGs...for 66 850Gb drives! I just set it to 4096 and will test after it finishes rebuilding

one more note. after I moved the CEPH interface from one NIC to the other, CEPH seemed fine but the virt bridges for the vms were not working. ended up rebooting the servers one at a time. then those came back. All tests done after the server reboot.

so...been using proxmox for many years (almost 20). have several existing server clusters. Just building a new server stack. 6x Dell R760 768G ram, dual 32 core cpu. each server with 11 850G 24GPS SA SCSI SSD, 4x 1G nic plus 2X dual 100G nic The drives are 3,400 MB/s capable Build cluster...

I have the solution (based on an answer on another thread). It was being blocked by ESET security. Even if you try "pause firewall/allow all network traffic" that does nOT pause the TLS filtering in ESET. You have to turn that off here

That WAS the problem. I thought that it was not ESET because I had tried "pause firewall/ allow all network traffic" and that made no difference. turns out that "allow all network traffic" does NOT stop the TLS filtering! This is what you have to turn off:

ok...I am now officially confused as hell. Adding exception in eset (which I do use) did not help stopping eset totally did not help clearing chrome cache did not help I found another laptop that had not been powered up in maybe two months. Fired it up, stopped eset so it would not update - and...

I had already tried updatecerts --force. Just tried again. the 25% success rate is random. does not matter which node I am connecting on vs node running vm. i.e. on gui for node04, I can connect to console on one vm out of ten right now, all running on that node

I tried disabling everything. I also found today that if I connect with firefox in private mode I can connect to console on maybe 25% of the VMs. It totally fails in chrome, ie, edge and safari. so...I am certain it is on the server end. But since some of them have not been updated in months...

A bit more info. using firefox, private mode it does work on some VMs - about 25% of them. the rest are blank screen. I think there are two problems: 1) reported by many people is this issue with consoles not working. you can connect, but no display 2) what I first reported. chrome, ie...

I saw a mention of that...but for some reason firefox will not connect to the gui at all. ok - just got it to connect to the gui by using private mode. And this does seem to go a step further - instead of "failed to connect to server" (with a JS cert error) it DOES connect, but is not working...

I tried chrome, ie, edge, even safari I have two clusters - one still on 5.1 the other on 5.4 (latest 5.x) both fail the same way