Problems after adding OSD nodes
Pages: 1 2
admin
2,929 Posts
December 2, 2024, 10:46 amQuote from admin on December 2, 2024, 10:46 amUnfortunately the PetaSAN logs have been rotated so the logs during deployment are gone. If you can check the other nodes, if its logs still covers the initial deployment it will help. But generally from ceph-volume logs, the osds seens to have been created from the deployment stage, but from our checks and tests we cannot explain this unless it was specified in the UI.
There is also consul errors that fills the PetaSAN log for that node, can you check if this is the case for all nodes, old/new ?
Unfortunately the PetaSAN logs have been rotated so the logs during deployment are gone. If you can check the other nodes, if its logs still covers the initial deployment it will help. But generally from ceph-volume logs, the osds seens to have been created from the deployment stage, but from our checks and tests we cannot explain this unless it was specified in the UI.
There is also consul errors that fills the PetaSAN log for that node, can you check if this is the case for all nodes, old/new ?
Pages: 1 2
Problems after adding OSD nodes
admin
2,929 Posts
Quote from admin on December 2, 2024, 10:46 amUnfortunately the PetaSAN logs have been rotated so the logs during deployment are gone. If you can check the other nodes, if its logs still covers the initial deployment it will help. But generally from ceph-volume logs, the osds seens to have been created from the deployment stage, but from our checks and tests we cannot explain this unless it was specified in the UI.
There is also consul errors that fills the PetaSAN log for that node, can you check if this is the case for all nodes, old/new ?
Unfortunately the PetaSAN logs have been rotated so the logs during deployment are gone. If you can check the other nodes, if its logs still covers the initial deployment it will help. But generally from ceph-volume logs, the osds seens to have been created from the deployment stage, but from our checks and tests we cannot explain this unless it was specified in the UI.
There is also consul errors that fills the PetaSAN log for that node, can you check if this is the case for all nodes, old/new ?