Node interfaces do not match cluster interface settings.
Pages: 1 2
fayaz khan
7 Posts
September 12, 2019, 11:09 amQuote from fayaz khan on September 12, 2019, 11:09 amhi
i have send you email with the subject of " cluster is not working"
please check that logs and revert back to us. we are looking your response on it.
hi
i have send you email with the subject of " cluster is not working"
please check that logs and revert back to us. we are looking your response on it.
admin
2,930 Posts
September 12, 2019, 3:19 pmQuote from admin on September 12, 2019, 3:19 pmdid you recheck and re-installed ?
did you recheck and re-installed ?
admin
2,930 Posts
September 13, 2019, 12:23 amQuote from admin on September 13, 2019, 12:23 amlooking at the logs, it seems the build got stuck on node 2 when building the cluster which occurs when you deploy node 3. For whatever reason it froze rather than return an error. I would suggest rechecking your settings / hardware and re-install. if still you have an issue, i would check node 2 hardware and disks.
looking at the logs, it seems the build got stuck on node 2 when building the cluster which occurs when you deploy node 3. For whatever reason it froze rather than return an error. I would suggest rechecking your settings / hardware and re-install. if still you have an issue, i would check node 2 hardware and disks.
Last edited on September 13, 2019, 12:33 am by admin · #13
fayaz khan
7 Posts
September 13, 2019, 7:17 amQuote from fayaz khan on September 13, 2019, 7:17 amhi
i re-install the petasan on node3 and join cluster again but its same issue .
i got this via fdisk -l on my node 3 : can you check it.
root@petasan-03:~# fdisk -l
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 61519D7F-76C6-448B-9B99-4B83F2D6EF09
Device Start End Sectors Size Type
/dev/sdb1 2048 1953525134 1953523087 931.5G Linux filesystem
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8FA4DFFB-ABF4-48DA-A597-4411167443F3
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 266239 262144 128M EFI System
/dev/sda3 266240 31723519 31457280 15G Linux filesystem
/dev/sda4 31723520 94638079 62914560 30G Linux filesystem
/dev/sda5 94638080 488397134 393759055 187.8G Linux filesystem
Disk /dev/mapper/ceph--71da8d1d--2021--4d06--8fa6--7e91a48311e7-osd--block--8bced7b7--aaf3--4638--bfa1--a3f1b1561b76: 931 GiB, 999653638144 bytes, 1952448512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
root@petasan-03:~#
hi
i re-install the petasan on node3 and join cluster again but its same issue .
i got this via fdisk -l on my node 3 : can you check it.
root@petasan-03:~# fdisk -l
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 61519D7F-76C6-448B-9B99-4B83F2D6EF09
Device Start End Sectors Size Type
/dev/sdb1 2048 1953525134 1953523087 931.5G Linux filesystem
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8FA4DFFB-ABF4-48DA-A597-4411167443F3
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 266239 262144 128M EFI System
/dev/sda3 266240 31723519 31457280 15G Linux filesystem
/dev/sda4 31723520 94638079 62914560 30G Linux filesystem
/dev/sda5 94638080 488397134 393759055 187.8G Linux filesystem
Disk /dev/mapper/ceph--71da8d1d--2021--4d06--8fa6--7e91a48311e7-osd--block--8bced7b7--aaf3--4638--bfa1--a3f1b1561b76: 931 GiB, 999653638144 bytes, 1952448512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
root@petasan-03:~#
admin
2,930 Posts
September 13, 2019, 9:18 amQuote from admin on September 13, 2019, 9:18 amHi
as requested please install all 3 nodes, as per my prev post, the system hang on node 2 during the cluster build step. the install will take a couple of minutes only so please do it. If you still get thus hang, look at node 2 hardware
i would not worry now on the gpt error you got, i do not know when you run this command, but we typically wipe out the disks you select before building the cluster.
Hi
as requested please install all 3 nodes, as per my prev post, the system hang on node 2 during the cluster build step. the install will take a couple of minutes only so please do it. If you still get thus hang, look at node 2 hardware
i would not worry now on the gpt error you got, i do not know when you run this command, but we typically wipe out the disks you select before building the cluster.
Last edited on September 13, 2019, 9:19 am by admin · #15
Pages: 1 2
Node interfaces do not match cluster interface settings.
fayaz khan
7 Posts
Quote from fayaz khan on September 12, 2019, 11:09 amhi
i have send you email with the subject of " cluster is not working"
please check that logs and revert back to us. we are looking your response on it.
hi
i have send you email with the subject of " cluster is not working"
please check that logs and revert back to us. we are looking your response on it.
admin
2,930 Posts
Quote from admin on September 12, 2019, 3:19 pmdid you recheck and re-installed ?
did you recheck and re-installed ?
admin
2,930 Posts
Quote from admin on September 13, 2019, 12:23 amlooking at the logs, it seems the build got stuck on node 2 when building the cluster which occurs when you deploy node 3. For whatever reason it froze rather than return an error. I would suggest rechecking your settings / hardware and re-install. if still you have an issue, i would check node 2 hardware and disks.
looking at the logs, it seems the build got stuck on node 2 when building the cluster which occurs when you deploy node 3. For whatever reason it froze rather than return an error. I would suggest rechecking your settings / hardware and re-install. if still you have an issue, i would check node 2 hardware and disks.
fayaz khan
7 Posts
Quote from fayaz khan on September 13, 2019, 7:17 amhi
i re-install the petasan on node3 and join cluster again but its same issue .
i got this via fdisk -l on my node 3 : can you check it.
root@petasan-03:~# fdisk -l
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 61519D7F-76C6-448B-9B99-4B83F2D6EF09Device Start End Sectors Size Type
/dev/sdb1 2048 1953525134 1953523087 931.5G Linux filesystem
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8FA4DFFB-ABF4-48DA-A597-4411167443F3Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 266239 262144 128M EFI System
/dev/sda3 266240 31723519 31457280 15G Linux filesystem
/dev/sda4 31723520 94638079 62914560 30G Linux filesystem
/dev/sda5 94638080 488397134 393759055 187.8G Linux filesystem
Disk /dev/mapper/ceph--71da8d1d--2021--4d06--8fa6--7e91a48311e7-osd--block--8bced7b7--aaf3--4638--bfa1--a3f1b1561b76: 931 GiB, 999653638144 bytes, 1952448512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
root@petasan-03:~#
hi
i re-install the petasan on node3 and join cluster again but its same issue .
i got this via fdisk -l on my node 3 : can you check it.
root@petasan-03:~# fdisk -l
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 61519D7F-76C6-448B-9B99-4B83F2D6EF09
Device Start End Sectors Size Type
/dev/sdb1 2048 1953525134 1953523087 931.5G Linux filesystem
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8FA4DFFB-ABF4-48DA-A597-4411167443F3
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 266239 262144 128M EFI System
/dev/sda3 266240 31723519 31457280 15G Linux filesystem
/dev/sda4 31723520 94638079 62914560 30G Linux filesystem
/dev/sda5 94638080 488397134 393759055 187.8G Linux filesystem
Disk /dev/mapper/ceph--71da8d1d--2021--4d06--8fa6--7e91a48311e7-osd--block--8bced7b7--aaf3--4638--bfa1--a3f1b1561b76: 931 GiB, 999653638144 bytes, 1952448512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
root@petasan-03:~#
admin
2,930 Posts
Quote from admin on September 13, 2019, 9:18 amHi
as requested please install all 3 nodes, as per my prev post, the system hang on node 2 during the cluster build step. the install will take a couple of minutes only so please do it. If you still get thus hang, look at node 2 hardware
i would not worry now on the gpt error you got, i do not know when you run this command, but we typically wipe out the disks you select before building the cluster.
Hi
as requested please install all 3 nodes, as per my prev post, the system hang on node 2 during the cluster build step. the install will take a couple of minutes only so please do it. If you still get thus hang, look at node 2 hardware
i would not worry now on the gpt error you got, i do not know when you run this command, but we typically wipe out the disks you select before building the cluster.