-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metad not receive heartbeat from storaged #4890
Comments
Dear @robcinko Could you plz check logs under log volumes of the storaged pods? |
Hello @wey-gu If you think that I have to check logs from pvc which using storaged pod as log store volume, then there are no events. |
@robcinko the log was not wired to k8s, it's file based, could you access the shell of the pod and print logs there?
|
Oh, my apologies for misunderstanding. Only pod which is sending heartbeat is nebula-cluster-storaged-1 [root@nebula-cluster-storaged-0 nebula]# cat logs/nebula-storaged.ERROR [root@nebula-cluster-storaged-1 nebula]# cat logs/nebula-storaged.ERROR Log file created at: 2022/11/15 13:11:10 |
It seems that it could not resolve the metad-0 's fqdn |
Yes, it seems we had a problem with coredns, now its solved. Thank you for help.😍 |
You are always welcome @robcinko :D |
Hi,
we have to reboot k8s workers (for some maintenance) where nebula cluster is running, after boot workers up all nebula services are running, but 2 of 3 storaged is not sending heartbeat to metad and we see 2 of 3 storaged pods offline (SHOW HOSTS in nebula-console). Sometimes this problem storaged pods sends heartbeat and goes ONLINE but after some time goes OFFLINE again.
Do you have any suggestions how to fix this ?
Thank you very much.
The text was updated successfully, but these errors were encountered: