smpartition start - Fails With Unable To Get Rpc Version On Some Nodes In The Fabric (Doc ID 2084598.1)

Last updated on SEPTEMBER 19, 2024

Applies to:

Symptoms

smpartition start (i.e. /usr/local/sbin/smpartition start) can fail if peer checks by partitiond (i.e. /usr/local/util/partitiond) fails.

Here are some example scenarios.

1)
# smpartition start
Unable to get rpc version on some nodes in the fabric
Please check /var/log/messages
#

- /var/log/messages -
Nov 25 11:31:46 ibsw partitiond: doPeerCheck: Unable to get rpc version for peer W.X.Y.Z
Nov 25 11:31:46 ibsw partitiond: doPeerCheck: Unable to get rpc version for peer W.X.Y.Z
Nov 25 11:36:16 ibsw partitiond: doPeerCheck: Unable to get rpc version for peer W.X.Y.Z
Nov 25 11:36:16 ibsw partitiond: doPeerCheck: Unable to get rpc version for peer W.X.Y.Z

2)
# smpartition start
Unable to signal some of the smnodes
Please check /var/log/messages
#

- /var/log/messages -
Dec 10 19:28:36 ibsw partitiond: doPeerCheck:Signaling other host failed: W.X.Y.Z
Dec 10 19:28:38 ibsw partitiond: doPeerCheck:Signaling other host failed: W.X.Y.Z
Dec 10 19:37:48 ibsw partitiond: doPeerCheck:Signaling other host failed: W.X.Y.Z
Dec 10 19:37:49 ibsw partitiond: doPeerCheck:Signaling other host failed: W.X.Y.Z

3)
# smpartition start
smnodes list on some nodes is inconsistant(empty/doesn't exist/different) with that of the primary
Please check /var/log/messages
Aborting.
#

- /var/log/messages -
Dec 10 19:32:24 ibsw partitiond: doPeerCheck :smnode file on W.X.Y.Z is different from primary
Dec 10 19:38:58 ibsw partitiond: doPeerCheck :smnode file on W.X.Y.Z is different from primary

Changes

IB environments can use IB partitions and smpartition start starts a session to edit IB partitions.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.