[SOLVED] Unable to install Ceph from GUI - fresh pve 6.2-11

[TwiX]

Hi,

After installing 3 nodes on a fresh cluster (6.2-11)
I'm not able to install Ceph from GUI.

Error is :


nothing interesting on syslog.

Spoiler: pveversion -v

proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-5
pve-kernel-helper: 6.2-5
pve-kernel-5.4.55-1-pve: 5.4.55-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.1-2
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-10
pve-cluster: 6.1-8
pve-container: 3.1-12
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-2
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-12
pve-xtermjs: 4.7.0-1
qemu-server: 6.2-11
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1

Thanks in advance !

Antoine

 

[Alwin]

The xterm.js connection on its own is working?

 

[TwiX]

Hi,
Yes, works as expected

 

[Alwin]

Can you please run the dev console (F12) in the browser and check which call gave the error? Should be marked in red.

 

[TwiX]

Same behaviour on a fresh install of pve on vmware workstation

 

[TwiX]

Here is a screenshot

 

[Alwin]

Hm... it is expected that the ceph/status will not work if no ceph-mon binary is found. But that's not the 'Error 400' message. Please check on the network tab of the dev tools to see if any other request failed.

 

[TwiX]

 

[TwiX]

 

[Alwin]

This should now be fixed in pve-xtermjs 4.7.0-2.

 

[TwiX]

Thanks...
I ran the command line instead

Also, did you ever seen some bad writes performances with ceph just after building the first pool ?

For example, with 18 SSD ODS => 400Mbytes/s writes and 2000Mbytes/s read.
I was expecting 900Mbytes/s for writes

With same hardware on proxmox 5.4 => 900 Mbytes/s

 

[tom]

thanks for the report, we already fixed the bug in latest package uploads.

> apt update
> apt dist-upgrade

see also http://download.proxmox.com/debian/...on/binary-amd64/pve-xtermjs_4.7.0-2.changelog

 

[Alwin]

@TwiX, different topic and needs more information to say anything. Please open up a new thread.

 

[damon1]

I am adding a new node to a 4 node system

I am using the fresh ISO from Proxmox 6.2 downloaded today and have done
> apt update
> apt dist-upgrade
The node adds to the cluster fine.

if I try to install CEPH using another node I get the 400 ERROR as described above.

If I log out of the other node and into the NEW node I dont see the 400 ERROR but during the installion of Ceph I get this "got timeout"



Even though it is greyed out CEPH continues to install all the way to the end



since it is still "got timeout" you cannot click on NEXT and hence CEPH will not install.

Any hints?

 

[damon1]

Update:
When I look in the SYSLOG I see a lot of these?

Sep 03 16:14:01 DC5 pvestatd[1751]: got timeout
Sep 03 16:14:02 DC5 pvestatd[1751]: status update time (5.460 seconds)
Sep 03 16:14:11 DC5 pvestatd[1751]: got timeout
Sep 03 16:14:11 DC5 pvestatd[1751]: status update time (5.452 seconds)
Sep 03 16:14:21 DC5 pvestatd[1751]: got timeout
Sep 03 16:14:22 DC5 pvestatd[1751]: status update time (5.465 seconds)
Sep 03 16:14:31 DC5 pvestatd[1751]: got timeout
Sep 03 16:14:31 DC5 pvestatd[1751]: status update time (5.450 seconds)
Sep 03 16:14:42 DC5 pvestatd[1751]: got timeout
Sep 03 16:14:42 DC5 pvestatd[1751]: status update time (5.470 seconds)
Sep 03 16:14:51 DC5 pvestatd[1751]: got timeout
Sep 03 16:14:51 DC5 pvestatd[1751]: status update time (5.470 seconds)

In case they are related or might give a clue.
thanks
Damon

 

[damon1]

If I need to come back to this - here is the solution.
On the new node you need to add the network that ceph uses
I.e. 10.10.10.8
Even if you have got the timeout and it says completed just add the network and reboot the node
problem solved