# ha-cluster script return error for default network interface

**URL:** <https://forums.suse.com/t/ha-cluster-script-return-error-for-default-network-interface/33132>\
**Category:** SLES High Availability Extension\
**Created:** [November 2, 2018, 10:17am UTC](https://forums.suse.com/t/ha-cluster-script-return-error-for-default-network-interface/33132 "2018-11-02T10:17:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![collinsyunkk](https://avatars.discourse-cdn.com/v4/letter/c/4491bb/32.png) [@collinsyunkk](https://forums.suse.com/u/collinsyunkk)\
**Post date:** [November 2, 2018, 10:17am UTC](https://forums.suse.com/t/ha-cluster-script-return-error-for-default-network-interface/33132/1 "2018-11-02T10:17:21Z")

</div>

Hello SME,

I’m testing SLES12 SP3 HA Extension. When running ha-cluster-init in node 1, it returns error message as follows. From the man page, it mentions eth0 is the default network interface. Don’t understand why it cannot detect the network card. The workaround is to use -i option to specify eth0 and looks worked fine. When running ha-cluster-join in node 2, it returns the same error message. But this time, that workaround doesn’t work and it returns another error message as follows. I verified that node 1 and node 2 are able to login with each others via ssh without password. Do you have any idea to solve it?

# In node 1

ha-cluster-init  
“ERROR: cluster.init: Failed to determine default network interface”

hc-cluster-init -i eth0  
…  
…  
Done (log saved to /var/log/ha-cluster-bootstrap.log)

# In node 2

ha-cluster-join  
ERROR: cluster.join: Failed to determine default network interface

ha-cluster-join -i eth0  
…  
…  
ERROR: 1: cluster.join: Can’t invoke ha-cluster-init ssh\_remote on 192.168.10.11

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [November 6, 2018, 1:18pm UTC](https://forums.suse.com/t/ha-cluster-script-return-error-for-default-network-interface/33132/2 "2018-11-06T13:18:55Z")

</div>

Hi collinsyunkk,

had you checked what’s in the logs (i. e. /var/log/ha-cluster-bootstrap.log) when running cluster-init without “-i”? Also, does “ip a” report anything unusual?

Regards,  
J

---

<div class="post-metadata">

**Author:** ![collinsyunkk](https://avatars.discourse-cdn.com/v4/letter/c/4491bb/32.png) [@collinsyunkk](https://forums.suse.com/u/collinsyunkk)\
**Post date:** [November 14, 2018, 10:21am UTC](https://forums.suse.com/t/ha-cluster-script-return-error-for-default-network-interface/33132/3 "2018-11-14T10:21:02Z")

</div>

[QUOTE=jmozdzen;55116]Hi collinsyunkk,

had you checked what’s in the logs (i. e. /var/log/ha-cluster-bootstrap.log) when running cluster-init without “-i”? Also, does “ip a” report anything unusual?

Regards,  
J[/QUOTE]

Hello jmozdzen,

Thanks for your comment. After read the log, I got a hint to turn on debug mode when running the crm command which called by ha-cluster-join. The issue is fixed by adding default gateway in both node 1 and 2 (even if both nodes are located at the same subnet).

Regards,  
Collins

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [November 14, 2018, 1:27pm UTC](https://forums.suse.com/t/ha-cluster-script-return-error-for-default-network-interface/33132/4 "2018-11-14T13:27:59Z")

</div>

Hi Collins,

thank you for sharing your findings - I wouldn’t have put my guess on a missing default route, indeed. Glad you found that out and got it running!

Regards,  
J