Can you execute "set -confirmations off" in the same command session before issuing the shutdown command? That should fix that. Alternatively, adding "-ignore-quorum-warnings true" to the halt command might do it
I received the following error message 'not authorized for that command' when halting the second node using a custom account.
I found an article (917335) that states: If you run the 'system node halt' command on the local node by using a user name with a role that has 'DEFAULT' and the access level is 'none', the command fails with the following error message: Error: not authorized for that command
Workaround: To prevent the 'system node halt' command from failing, perform one of the following steps: - Run the command by using a user name with a role that has 'DEFAULT' and the access level is 'all'. - Run the command from a node other than the one you are attempting to halt.
When you create a custome role, "DEFAULT" is also created for that role with an access level of "none".
I modifued "DEFAULT for that role to an access level of "all" and was able to halt both nodes without error.