You should be able to start a CONFIG instance on local node.
This is like creating an instance with the out-of-box localhost-domain1
CONFIG node, and you shouldn't have any problem starting such instance.
I just launched the 3.1.2 admin console, created a CONFIG node, and
specify 'localhost' as the host, and then create a standalone
instance specifying this config node, I can start that instance without
any problem.
Actually Admin Console just calls the start-instance command to start
this instance. Are you able to start your instance by running
"asadmin start-instance thupa" ?
Anissa.
On 4/5/12 12:36 PM, Laird Nelson wrote:
> Playing around with standalone instances.
>
> I created a new CONFIG instance on the local node (named thupa). Then
> I tried to start it.
>
> The error message in the admin console says:
>
> Could not start instance thupa on node localhost-jx (localhost).
> Command failed on node localhost-jx (localhost): CLI801 Instance is
> already synchronized Command start-local-instance failed. Picked up
> _JAVA_OPTIONS: -Dfile.encoding=UTF-8 The Master Password is required
> to start the domain. No console, no prompting possible. You should
> either create the domain with --savemasterpassword=true or provide a
> password file with the --passwordfile option. To complete this
> operation run the following command locally on host localhost from the
> GlassFish install location /usr/local/glassfish-3.1.2b23: bin/asadmin
> start-local-instance --node localhost-jx --sync normal thupa
>
> I understand basically what this is telling me. But does that mean
> that it is impossible to start a CONFIG instance on the local node
> from the admin console?
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson
>