The attempt to restart-instance while the instance did not run - failed

[glassfishrobot]

Glassfish 3.1.1 b07. This issue exists on all platforms.

The attempt to restart-instance while the instance did not run - failed:

============================================================================

---

create-local-instance --cluster c4 --node localhost-domain4 in41 Rendezvoused with DAS on localhost:7000. Port Assignments for server instance in41: JMX_SYSTEM_CONNECTOR_PORT=28686 JMS_PROVIDER_PORT=27676 HTTP_LISTENER_PORT=28080 ASADMIN_LISTENER_PORT=24848 JAVA_DEBUGGER_PORT=29009 IIOP_SSL_LISTENER_PORT=23820 IIOP_LISTENER_PORT=23700 OSGI_SHELL_TELNET_PORT=26666 HTTP_SSL_LISTENER_PORT=28181 IIOP_SSL_MUTUALAUTH_PORT=23920 Command create-local-instance executed successfully.

---

restart-instance --debug=true in41 remote failure: The instance is not running. A start was attempted but it was unsuccessful. Please try to start the instance with start-local-instance. Message from start-instance: Could not start instance in41 on node localhost-domain4 (localhost).

Command failed on node localhost-domain4 (localhost): Command start-local-instance failed.

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 C:\hudson\workspace\dmcli\glassfish3:

asadmin start-local-instance --node localhost-domain4 --sync normal --debug in41 Command restart-instance failed.

================================================================

create-instance --node=node44 in43 Command _create-instance-filesystem executed successfully.

Port Assignments for server instance in43: JMX_SYSTEM_CONNECTOR_PORT=28688 JMS_PROVIDER_PORT=27678 HTTP_LISTENER_PORT=28082 ASADMIN_LISTENER_PORT=24850 JAVA_DEBUGGER_PORT=29011 IIOP_SSL_LISTENER_PORT=23822 IIOP_LISTENER_PORT=23702 OSGI_SHELL_TELNET_PORT=26668 HTTP_SSL_LISTENER_PORT=28183 IIOP_SSL_MUTUALAUTH_PORT=23922

The instance, in43, was created on host localhost Command create-instance executed successfully.

---

restart-instance in43 remote failure: The instance is not running. A start was attempted but it was unsuccessful. Please try to start the instance with start-local-instance. Message from start-instance: Could not start instance in43 on node node44 (localhost).

Command failed on node node44 (localhost): Command start-local-instance failed.

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 C:\hudson\workspace\dmcli\glassfish3:

asadmin start-local-instance --node node44 --sync normal in43 Command restart-instance failed.

Affected Versions

[3.1.1_dev]

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/glassfish/issues/16833
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @yaminikb
• Original Issue Closed By:@glassfishrobot

[glassfishrobot]

@glassfishrobot Commented bnevins said: There is a crystal-clear message in the "failure". It wants you to hand over the master password!

Works fine for me.

Reassign to Tom instead of closing as invalid. Tom - do you see this bug?

===================

d:\gf\v3>asadmin create-cluster c4

d:\gf\v3>asadmin create-local-instance --cluster c4 in41 Rendezvoused with DAS on localhost:4848.

d:\gf\v3>asadmin create-local-instance --cluster c4 in42 Rendezvoused with DAS on localhost:4848. Using DAS host localhost and port 4848 from existing das.properties for node localhost-domain1. To use a different DAS, create a new node using create-node-ssh or create-node-config. Create the instance with the new node and correct host and port: asadmin --host das_host --port das_port create-local-instance --node node_name instance_name.

d:\gf\v3>asadmin restart-instance --debug=true in41 The instance was not running. A normal start was successful. Message from start-instance: Attempting to start in41.... Please look at the server log for more details..... The instance, in41, was started on host localhost

[glassfishrobot]

@glassfishrobot Commented scatari said: Downgrading as the message is clear and no impact on product functionality.

[glassfishrobot]

@glassfishrobot Commented tmueller said: I agree with Byron that this is not a bug. When a master password is required to start an instance, and the master password has not been saved, then restart-instance cannot be used to start the instance. This is because if the instance is remote, then the master password would have to be passed over the network which is not allowed for security reasons.

In this case, a local command must be used to start the instance.

[glassfishrobot]

@glassfishrobot Commented easarina said: 1) The domain was created with: --savemasterpassword=true.

asadmin --passwordfile password.txt --user admin --host localhost --port 7000 create-domain --adminport=7000 --instanceport=6000 --savemasterpassword=true --usemasterpassword=true --savelogin=false --checkports=true --nopassword=false domain4

2) The restart-instance used --password.

asadmin --passwordfile password.txt --user admin --host localhost --port 7000 restart-instance --debug=true in41

3) Everything was executed on one machine

4) When the instance was running restart-instance worked.

So the master password should not be sent over the network in this case.

[glassfishrobot]

@glassfishrobot Commented tmueller said: Saving the master password on the DAS (domain) does not cause the master password to be saved for nodes. To save the master password for a node, you have to have the commnand "asadmin change-master-password nodename" where nodename is the name of the node, such as localhost-domain1 for the node that is created by default.

The master password mechanism is designed so that the master password is never sent over the network by GlassFish. So if there is a master password, and it is not saved on the node (even if local to the DAS), then restart-instance can only restart the instance if it is already running. If the instance is stopped, then restart-instance cannot start an instance that is on a node that doesn't have the master password saved.

[glassfishrobot]

@glassfishrobot Commented Was assigned to tmueller

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-16833

[glassfishrobot]

@glassfishrobot Commented Reported by easarina

[glassfishrobot]

@glassfishrobot Commented Marked as works as designed on Monday, June 13th 2011, 11:51:58 pm