It turned out rpcbind was not setup correctly. This is a note that the Sun
Engineer sent me:
Symptoms
Although RPC is enabled on the ACSLS server, RPC clients cannot
communicate to it.
rpcinfo, when called from the client server, fails with an "Authentication
error".
# rpcinfo -p acsls_hostname
rpcinfo: can't contact portmapper: RPC: Authentication error; why
= Failed (unspecified error)
Changes
New clustered servers with Solaris OS, Solaris Cluster, ACSLS and ACSLS
HA installed successfully.
Cause
rpcbind service was configured to have SMF property config/local_only set
to TRUE. (By, default, it should be set to FALSE.) This SMF property is
used to allow or disallow access to rpcbind by remote clients.
Thus, a value of TRUE will disallow remote access.
Solution
1. Verify the RPC bind service's local_only property setting:
# svccfg -s bind listprop | grep local
config/local_only boolean true
2. If set to TRUE, change the setting to FALSE; then, list the property
again to verify change:
# svccfg -s bind setprop config/local_only=false
# svccfg -s bind listprop | grep local
config/local_only boolean false
3. Refresh the service to activate the new value:
# svcadm refresh bind
-----Original Message-----
From: veritas-bu-bounces < at > mailman.eng.auburn.edu
[mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of John
Meyers
Sent: Monday, October 03, 2011 3:48 PM
To: Rusty Major
Cc: VERITAS-BU < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ACSLS 8.0.2 and NBU 7.1(.0.2)
Just a data point for you. We're still on ACSLS 7.3 under Solaris 10 and
have had zero issues going from 6.5.4 -> 7.0 -> 7.0.1 -> 7.1 -> 7.1.0.1.
The robot definitions were defined soley through the gui after the initial
7.0 upgrade and don't have anything specific to the robot in the vm.conf.
John
On 10/03/2011 02:03 PM, Rusty Major wrote:
Hi All,
Fresh install of NBU 7.1 with ACSLS 8.0.2, both on Solaris 10. I am
unable to get NBU to communicate with ACSLS without forcing the port
to communicate over in vm.conf (ACS_CSI_HOSTPORT). This works fine until
the ACSLS application is restarted and the port changes.
I noticed with NBU version 7.1.0.0, MM and ACS daemons would not even
start up, but when I patched to 7.1.0.2, all the appropriate daemons
started, but there was still no communication with ACSLS without the
above mentioned vm.conf entry. ACSLS is configured with default settings.
I have an ACSLS 8.0.2 server working with NBU version 6.5.x without
any issues (same default ACSLS settings and no entries in VM.CONF).
Has anyone run across this and have any pointers?
Thanks,
-Rusty
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
