PowerEdge: O nó não consegue ingressar no cluster Linux existente
요약: Ao tentar associar um nó a um cluster Linux existente, recebendo um "warning: csync2 run failed - some files may not be sync'd" e "error: cluster.join: [Errno 2] No such file or directory: Mensagens '/etc/corosync/corosync.conf' ...
이 문서는 다음에 적용됩니다.
이 문서는 다음에 적용되지 않습니다.
이 문서는 특정 제품과 관련이 없습니다.
모든 제품 버전이 이 문서에 나와 있는 것은 아닙니다.
증상
Um cluster Linux foi criado no nó 01 usando #crm comando cluster init e, em seguida, o cluster foi criado com sucesso.
Quando o nó 02 está tentando ingressar no cluster, é possível receber avisos sobre falha na execução do csync2 e erro ao ingressar no cluster.
No entanto, o erro abaixo pode ser observado:
node01:~ # crm status
Cluster Summary:
* Stack: corosync
* Current DC: node01 (version 2.1.2+20211124.ada5c3b36-150400.4.14.9-2.1.2+20211124.ada5c3b36) - partition with quorum
* Last updated: Thu Oct 26 13:44:44 2023
* Last change: Thu Oct 26 13:27:44 2023 by root via crm_node on node01
* 1 node configured
* 0 resource instances configured
Node List:
* Online: [ node01 ]
Full List of Resources:
* No resources
Quando o nó 02 está tentando ingressar no cluster, é possível receber avisos sobre falha na execução do csync2 e erro ao ingressar no cluster.
node02:~ # crm cluster join INFO: Join This Node to Cluster: You will be asked for the IP address of an existing node, from which configuration will be copied. If you have not already configured passwordless ssh between nodes, you will be prompted for the root password of the existing node. IP address or hostname of existing node (e.g.: 192.168.1.1) []node01 INFO: The user 'hacluster' will have the login shell configuration changed to /bin/bash Continue (y/n)? y INFO: Generating SSH key for hacluster INFO: Configuring SSH passwordless with hacluster@node01 INFO: BEGIN Configuring csync2 WARNING: csync2 run failed - some files may not be sync'd INFO: END Configuring csync2 INFO: Merging known_hosts INFO: BEGIN Probing for new partitions INFO: END Probing for new partitions ERROR: cluster.join: [Errno 2] No such file or directory: '/etc/corosync/corosync.conf'Em seguida, verificamos o status csync2 do node01.
node01:~ # csync2 -x Peer did provide a wrong SSL X509 cetrificate.O procedimento normal para resolver esse problema é executar um "$PEERNAME csync2-rm-ssl-cert" para remover as entradas antigas.
No entanto, o erro abaixo pode ser observado:
node01:~ # csync2-rm-ssl-cert node2 Certificate for 'node2' not in local database.
원인
Certificado SSL X509 incorreto
해결
Usando o seguinte comando para excluir a entrada antiga :(NOTA: Para SLES12, VERSÃO = 3)
# echo "DELETE FROM x509_cert WHERE peername='HOST2';" |sqlite${VERSION} /var/lib/csync2/$(echo $HOSTNAME | tr [:upper:] [:lower:]).db${VERSION}
Em nosso exemplo:
node01: # echo "DELETE FROM x509_cert WHERE peername='node02';" |sqlite3 /var/lib/csync2/$(echo $HOSTNAME | tr [:upper:] [:lower:]).db3
Reingressar no cluster a partir do nó 02 novamente será bem-sucedido.
node02:~ # crm cluster join INFO: Join This Node to Cluster: You will be asked for the IP address of an existing node, from which configuration will be copied. If you have not already configured passwordless ssh between nodes, you will be prompted for the root password of the existing node. IP address or hostname of existing node (e.g.: 192.168.1.1) []node01 INFO: BEGIN Configuring csync2 INFO: END Configuring csync2 INFO: Merging known_hosts INFO: BEGIN Probing for new partitions INFO: END Probing for new partitions Address for ring0 [192.168.XXX.XXX]192.168.XXX.XXX INFO: Hawk cluster interface is now running. To see cluster status, open: INFO: https://192.168.XXX.XXX:7630/ INFO: Log in with username 'hacluster', password 'XXXXX' WARNING: You should change the hacluster password to something more secure! INFO: BEGIN Waiting for cluster .. INFO: END Waiting for cluster INFO: BEGIN Reloading cluster configuration INFO: END Reloading cluster configuration INFO: Done (log saved to /var/log/crmsh/crmsh.log)
Verifique o status do cluster:
node02:~ # crm status
Cluster Summary:
* Stack: corosync
* Current DC: node01 (version 2.1.2+20211124.ada5c3b36-150400.4.14.9-2.1.2+20211124.ada5c3b36) - partition with quorum
* Last updated: Thu Oct 26 14:10:32 2023
* Last change: Thu Oct 26 14:05:22 2023 by hacluster via crmd on node01
* 2 nodes configured
* 0 resource instances configured
Node List:
* Online: [ node01 node02 ]
Full List of Resources:
* No resources
해당 제품
Red Hat Enterprise Linux Version 7, Red Hat Enterprise Linux Version 9, Red Hat Enterprise Linux Version 8, SUSE Linux Enterprise Server 15제품
PowerEdge XR2, PowerEdge C6420, PowerEdge C6520, PowerEdge C6525, PowerEdge C6615, PowerEdge C6620, PowerEdge M640, PowerEdge M640 (for PE VRTX), PowerEdge MX5016s, PowerEdge MX740C, PowerEdge MX750c, PowerEdge MX760c, PowerEdge MX840C
, PowerEdge R240, PowerEdge R250, PowerEdge R260, PowerEdge R340, PowerEdge R350, PowerEdge R360, PowerEdge R440, PowerEdge R450, PowerEdge R540, PowerEdge R550, PowerEdge R640, PowerEdge R6415, PowerEdge R650, PowerEdge R650xs, PowerEdge R6515, PowerEdge R6525, PowerEdge R660, PowerEdge R660xs, PowerEdge R6615, PowerEdge R6625, PowerEdge R740, PowerEdge R740XD, PowerEdge R740XD2, PowerEdge R7415, PowerEdge R7425, PowerEdge R750, PowerEdge R750XA, PowerEdge R750xs, PowerEdge R7515, PowerEdge R7525, PowerEdge R760, PowerEdge R760XA, PowerEdge R760xd2, PowerEdge R760xs, PowerEdge R7615, PowerEdge R7625, PowerEdge R840, PowerEdge R860, PowerEdge R940, PowerEdge R940xa, PowerEdge R960, PowerEdge XE2420, PowerEdge XE7420, PowerEdge XE7440, PowerEdge XE8545, PowerEdge XE8640, PowerEdge XE9640, PowerEdge XE9680, PowerEdge XR11, PowerEdge XR12, PowerEdge XR4510c, PowerEdge XR4520c, PowerEdge XR5610, PowerEdge XR7620, PowerEdge XR8610t, PowerEdge XR8620t
...
문서 속성
문서 번호: 000218952
문서 유형: Solution
마지막 수정 시간: 03 1월 2025
버전: 2
다른 Dell 사용자에게 질문에 대한 답변 찾기
지원 서비스
디바이스에 지원 서비스가 적용되는지 확인하십시오.