[SOLVED] ceph greyed out

pille99

Active Member
Sep 14, 2022
360
28
28
what to do ?
 

Attachments

  • 1.JPG
    1.JPG
    47.9 KB · Views: 13
  • 2.JPG
    2.JPG
    59.2 KB · Views: 13
  • 3.JPG
    3.JPG
    15.5 KB · Views: 13
What was the last change?
This can have multiple root issues, mostly Network.
 
the change i try to do was to change from sdn vxlan to evpn.
i changed the physically NIC as a vLan but it wasnt proper working. than i did the previous update. and since the ceph osd cant be seen again.
 
in the syslogs are shown
irt04 pvestatd[1944]: status update time (10.213 seconds)
Mar 15 21:09:23 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:09:28 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:09:28 hvirt04 pvestatd[1944]: status update time (10.212 seconds)
Mar 15 21:09:33 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:09:38 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:09:38 hvirt04 pvestatd[1944]: status update time (10.214 seconds)
Mar 15 21:09:43 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:09:48 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:09:49 hvirt04 pvestatd[1944]: status update time (10.211 seconds)
Mar 15 21:09:54 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:09:59 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:09:59 hvirt04 pvestatd[1944]: status update time (10.213 seconds)
Mar 15 21:10:04 hvirt04 pvestatd[1944]: got timeout
Mar 15 21:10:09 hvirt04 pvestatd[1944]: got timeout

i have no idea from where the timeout is coming from. all ips are pingable
 
Do you use Jumbo Frames?
You can check with large Ping Packets.
 
PING 10.10.12.11 (10.10.12.11) 9000(9028) bytes of data.
ping: local error: message too long, mtu=9000
ping: local error: message too long, mtu=9000
ping: local error: message too long, mtu=9000
ping: local error: message too long, mtu=9000
ping: local error: message too long, mtu=9000
 
ping to all and from all interfaces are now with the result in top. this config was running the last half year. why it doesnt work anymore ?
i changed to standard value (removed the value) and try again
the ping with
root@hvirt01:~# ping -M do -s 8972 10.10.12.11
PING 10.10.12.11 (10.10.12.11) 8972(9000) bytes of data.
8980 bytes from 10.10.12.11: icmp_seq=1 ttl=64 time=1.56 ms
8980 bytes from 10.10.12.11: icmp_seq=2 ttl=64 time=0.995 ms
is working. strange
 
fugg me - with 8972 mtu its working again.

i made to much changes at the time like create sdn, made the latest updates, and some changes on the network (just not the mtu value - because it was working). it must be of the new updates. maybe somebody else can confirm that
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!