Error deploying node
adrianm
5 Posts
February 14, 2021, 11:12 amQuote from adrianm on February 14, 2021, 11:12 amHi just starting to spin up our new cluster. We a re provision with only the backend/management interface selected. Upon addition of 3rd node - regards of which way round we do it we keep recieving the following error.
Create ceph mon on psan-n3 returned error.
Have looked through some of the logs and it states it cant find ceph.conf but I have looked in /etc/ceph and the file is there.
Any further pointers appreciated.
Hi just starting to spin up our new cluster. We a re provision with only the backend/management interface selected. Upon addition of 3rd node - regards of which way round we do it we keep recieving the following error.
Create ceph mon on psan-n3 returned error.
Have looked through some of the logs and it states it cant find ceph.conf but I have looked in /etc/ceph and the file is there.
Any further pointers appreciated.
adrianm
5 Posts
February 14, 2021, 12:10 pmQuote from adrianm on February 14, 2021, 12:10 pmOk have found Petasan log file.
Last three line display
ceph-mon --mkfs --add returned error
could not build ceph monitors.
['Create ceph mon on psan-n3 returned error.']
If i run 'ceph-mon --mkfs --add' the error is 'too many arguments: [--add]'
If I run 'ceph-mon --mkfs' I get unable to parse network: 192.168.1.0/24'
This network is on a seperare interface to the management and all nodes can talk to each other over it.
Ok have found Petasan log file.
Last three line display
ceph-mon --mkfs --add returned error
could not build ceph monitors.
['Create ceph mon on psan-n3 returned error.']
If i run 'ceph-mon --mkfs --add' the error is 'too many arguments: [--add]'
If I run 'ceph-mon --mkfs' I get unable to parse network: 192.168.1.0/24'
This network is on a seperare interface to the management and all nodes can talk to each other over it.
adrianm
5 Posts
February 14, 2021, 1:50 pmQuote from adrianm on February 14, 2021, 1:50 pmLooks like I may have resolved to the issue. Some adapters had 192.168.001.00* attached to them and others 192.168.1.*. Once I stripped out the leading 0's from each ocolet the cluster started to connect.
Looks like I may have resolved to the issue. Some adapters had 192.168.001.00* attached to them and others 192.168.1.*. Once I stripped out the leading 0's from each ocolet the cluster started to connect.
Error deploying node
adrianm
5 Posts
Quote from adrianm on February 14, 2021, 11:12 amHi just starting to spin up our new cluster. We a re provision with only the backend/management interface selected. Upon addition of 3rd node - regards of which way round we do it we keep recieving the following error.
Create ceph mon on psan-n3 returned error.
Have looked through some of the logs and it states it cant find ceph.conf but I have looked in /etc/ceph and the file is there.
Any further pointers appreciated.
Hi just starting to spin up our new cluster. We a re provision with only the backend/management interface selected. Upon addition of 3rd node - regards of which way round we do it we keep recieving the following error.
Create ceph mon on psan-n3 returned error.
Have looked through some of the logs and it states it cant find ceph.conf but I have looked in /etc/ceph and the file is there.
Any further pointers appreciated.
adrianm
5 Posts
Quote from adrianm on February 14, 2021, 12:10 pmOk have found Petasan log file.
Last three line display
ceph-mon --mkfs --add returned error
could not build ceph monitors.
['Create ceph mon on psan-n3 returned error.']If i run 'ceph-mon --mkfs --add' the error is 'too many arguments: [--add]'
If I run 'ceph-mon --mkfs' I get unable to parse network: 192.168.1.0/24'
This network is on a seperare interface to the management and all nodes can talk to each other over it.
Ok have found Petasan log file.
Last three line display
ceph-mon --mkfs --add returned error
could not build ceph monitors.
['Create ceph mon on psan-n3 returned error.']
If i run 'ceph-mon --mkfs --add' the error is 'too many arguments: [--add]'
If I run 'ceph-mon --mkfs' I get unable to parse network: 192.168.1.0/24'
This network is on a seperare interface to the management and all nodes can talk to each other over it.
adrianm
5 Posts
Quote from adrianm on February 14, 2021, 1:50 pmLooks like I may have resolved to the issue. Some adapters had 192.168.001.00* attached to them and others 192.168.1.*. Once I stripped out the leading 0's from each ocolet the cluster started to connect.
Looks like I may have resolved to the issue. Some adapters had 192.168.001.00* attached to them and others 192.168.1.*. Once I stripped out the leading 0's from each ocolet the cluster started to connect.