由於 Bare Metal 解決方案 SSH 守護程式設定問題，因此執行重新設定的 SCP 檔案複製作業可能會花費太長時間。
如要解決這個問題，請按照下列步驟操作：
在 Bare Metal 解決方案伺服器上，以編輯模式開啟 sshd_config 檔案。
vi /etc/ssh/sshd_config
在 sshd_config 檔案中新增以下行。如果檔案中已存在該行，請按照下列方式修改：
ClientAliveInterval 420
重新啟動 sshd 服務，套用變更。
/etc/init.d/sshd restart
CRS root.sh 或 OCSSD 失敗，並顯示 No Network HB 錯誤
如果節點對 IP 位址 169.254.169.254 執行 ping 作業，CRS root.sh 指令碼就會失敗，並顯示以下錯誤：
has a disk HB, but no network HB
IP 位址 169.254.169.254 是 Google Cloud 中繼資料服務，可在 Google Cloud中註冊執行個體。如果您封鎖這個 IP 位址， Google Cloud VM 就無法啟動。這反過來可能會中斷 HAIP 通訊路徑，導致 Bare Metal 解決方案 RAC 伺服器發生 HAIP 通訊問題。
如要解決這個問題，請封鎖 IP 位址或停用 HAIP。以下範例說明如何使用 route 指令封鎖 IP 位址。route 陳述式所做的變更不會保留。因此，您需要修改系統啟動指令碼。
如要解決這個問題，請按照下列步驟操作：
請在所有節點上執行下列指令，然後再重新執行 root.sh 指令碼。
/sbin/route add -host 169.254.169.254 reject
將 rc 指令碼設為可執行。
chmod +x /etc/rc.d/rc.local
在 /etc/rc.d/rc.local 檔案中，新增以下行：
/sbin/route add -host 169.254.169.254 reject
Enable rc-local service
systemctl status rc-local.service
systemctl enable rc-local.service
systemctl start rc-local.service
重新啟動程序沒有回應
如果伺服器執行 Red Hat Linux、OVM 或 SUSE Linux，且有許多 LUN 連接至該伺服器，重新啟動程序可能會停止回應。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThis document provides solutions for common issues encountered when troubleshooting Oracle RAC on Bare Metal Solution, including SSH and SCP performance problems.\u003c/p\u003e\n"],["\u003cp\u003eThe OpenSSH error during Grid Infrastructure installation can be resolved by modifying the \u003ccode\u003eKexAlgorithms\u003c/code\u003e in the \u003ccode\u003e/etc/ssh/sshd_config\u003c/code\u003e file and restarting the \u003ccode\u003esshd\u003c/code\u003e service.\u003c/p\u003e\n"],["\u003cp\u003eIssues with CRS \u003ccode\u003eroot.sh\u003c/code\u003e or OCSSD failing due to a \u003ccode\u003eNo Network HB\u003c/code\u003e error can be addressed by blocking the IP address 169.254.169.254 using the \u003ccode\u003eroute\u003c/code\u003e command and adding it to the \u003ccode\u003e/etc/rc.d/rc.local\u003c/code\u003e file.\u003c/p\u003e\n"],["\u003cp\u003eIf the server's reboot process stops responding, especially with many attached LUNs, increasing the watchdog timeout value in the \u003ccode\u003e/etc/systemd/system.conf.d/\u003c/code\u003e or modifying the \u003ccode\u003egrub.cfg\u003c/code\u003e file can resolve it.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eRejecting connection\u003c/code\u003e error during Oracle Grid infrastructure 12c installation can be fixed by blocking access to the metadata service on both cloud VMs and Bare Metal Solution hosts using firewall commands.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot Oracle RAC issues\n==============================\n\nThis page provides troubleshooting tips for issues related to Oracle RAC on\nBare Metal Solution.\n\nCheck if your question or problem has already been addressed on the\n[Known issues and limitations](/bare-metal/docs/known-issues) page.\n\n### SSH verification fails with OpenSSH error\n\nSSH verification might fail with the following OpenSSH error: \n\n OpenSSH_6.7: ERROR [INS-06003] Failed to setup passwordless SSH connectivity During Grid Infrastructure Install\n\nTo resolve this issue, do the following:\n\n1. In the `/etc/ssh/sshd_config` file, add the following line:\n\n KexAlgorithms curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1\n\n2. Restart the `sshd` service to apply the changes.\n\n /etc/init.d/sshd restart\n\nSCP file copy taking too long\n-----------------------------\n\nThe SCP file copy with rekey operation might take too long to complete due to\na Bare Metal Solution SSH daemon configuration issue.\n\nTo resolve this issue, do the following:\n\n1. On your Bare Metal Solution server, open the `sshd_config` file in edit mode.\n\n vi /etc/ssh/sshd_config\n\n2. In the `sshd_config` file, add following line. If the line already exists in\n the file, modify it as follows:\n\n ClientAliveInterval 420\n\n3. Restart the `sshd` service to apply the changes.\n\n /etc/init.d/sshd restart\n\nCRS `root.sh` or OCSSD fails with `No Network HB` error\n-------------------------------------------------------\n\nCRS `root.sh` script fails with the following error if the node pings\nthe IP address 169.254.169.254: \n\n has a disk HB, but no network HB\n\nThe IP address 169.254.169.254 is the Google Cloud metadata service\nwhich registers the instance in Google Cloud. If you block this IP\naddress, the Google Cloud VM can't boot up. This in turn can interrupt the\nHAIP communication route causing the Bare Metal Solution RAC servers to\nexperience HAIP communication issues.\n\nTo resolve this issue, you need to block the IP address or disable HAIP. The\nfollowing example shows how to block IP address with `route` commands. The\nchanges made by `route` statement are not persistent. Therefore, you need to\nmodify the system startup scripts.\n\nTo resolve this issue, do the following:\n\n1. On all the nodes, run the following command before rerunning the `root.sh`\n script.\n\n /sbin/route add -host 169.254.169.254 reject\n\n2. Make the `rc` script executable.\n\n chmod +x /etc/rc.d/rc.local\n\n3. In the `/etc/rc.d/rc.local` file, add the following lines:\n\n /sbin/route add -host 169.254.169.254 reject\n\n Enable rc-local service\n systemctl status rc-local.service\n systemctl enable rc-local.service\n systemctl start rc-local.service\n\nReboot process not responding\n-----------------------------\n\nIf your server is running Red Hat Linux, OVM, or SUSE Linux, and there are many\nLUNs attached to it, the reboot process might stop responding.\n\nTo resolve this issue, increase the default watchdog timeout value:\n\n1. Under `/etc/systemd`, create a folder named `system.conf.d`.\n\n2. In the folder, create a `*.conf` file. For example,\n `/etc/systemd/system.conf.d/kernel-reboot-workaround.conf`.\n\n3. In the `*.conf` file, add the following code:\n\n [Manager]\n\n RuntimeWatchdogSec=5min\n\n ShutdownWatchdogSec=5min\n\nAn alternative workaround is as follows:\n\n1. Open the `grub.cfg` file in edit mode.\n\n vi /etc/default/grub\n\n2. Remove the `quiet` parameter from the settings.\n\n3. Add the following after the parameter `GRUB_CMDLINE_LINUX`:\n\n acpi_no_watchdog DefaultTimeoutStartSec=900s DefaultTimeoutStopSec=900s\n\n4. Rebuild the `grub.cfg` file.\n\n grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg\n\nOracle Grid infrastructure 12c fails with `Rejecting connection` error\n----------------------------------------------------------------------\n\nOracle Grid infrastructure 12c installation might fail with the following error: \n\n Rejecting connection from node 2 as MultiNode RAC is not supported or certified in this Configuration.\n\nThis error occurs because the IP address 169.254.169.254 is forwarded to the\nlocal metadata service of a Compute Engine VM, making it look like the Bare Metal Solution\nhost is a Compute Engine VM. Such a configuration might also leak the\nCompute Engine VM's private\nservice account keys.\n\nTo resolve this issue, consider the security implications of your NAT\nconfiguration and limit external network access as much as possible. Do the\nfollowing:\n\n- Block the access to the metadata service on your cloud VM:\n\n firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -d 169.254.169.254 -j REJECT --reject-with icmp-host-unreachable\n\n firewall-cmd --permanent --direct --add-rule ipv4 filter FORWARD 0 -d 169.254.169.254 -j REJECT --reject-with icmp-host-unreachable\n\n- Block access to the metadata service on the Bare Metal Solution host:\n\n firewall-cmd --direct --add-rule ipv4 filter OUTPUT 0 -d 169.254.169.254 -j REJECT --reject-with icmp-host-unreachable\n\n firewall-cmd --permanent --direct --add-rule ipv4 filter OUTPUT 0 -d 169.254.169.254 -j REJECT --reject-with icmp-host-unr"]]
